## TL;DR

Clients that assume an exhaustive enum set or fail on unknown fields will break; parse leniently and handle unknown errors gracefully. The API returns 503 when Green Dot's systems are unavailable, so implement retry logic on cash-deposit paths and never treat 503 as a final decline.

## Fix

1. Clients that assume an exhaustive enum set or fail on unknown fields will break; parse leniently and handle unknown errors gracefully.
   Expected: You get the expected result; the problem is gone.

## When to use

- You are setting up or using this Treasury Prime feature.
- The symptom matches: handle Green Dot 503s and unknown API enum values gracefully.

## When NOT to use

- Unrelated Treasury Prime issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported against Treasury Prime. Source: https://docs.treasuryprime.com/reference/compatibility.

## Variant phrasings

### handle Green Dot 503s and unknown API enum values gracefully

## Why it happens

Green Dot cash deposit calls occasionally return 503, and API enums can grow new values that break strict client parsing.

## Edge cases

- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.

## Source

https://docs.treasuryprime.com/reference/compatibility