Nessie v2 POST /accounts/{id}/transfers 422 problems/insufficient_funds 'Account ... has N cents available, which does not cover M.': checked against available_cents, before the transaction exists
Switch on the problem type, not the text: Nessie v2 returns application/problem+json with "type": "https://nessieisreal.com/problems/insufficient_funds", "title": "Unprocessable Entity", "status": 422, "detail": "Account <account_id> has 32650 cents available, which does not cover 999999999.". Reproduce: curl -X POST -H "Authorization: Bearer $NESSIE_KEY" -H 'Content-Type: application/json' -d '{"payee_id":"<other_account_id>","amount_cents":999999999}' https://v2-prod-api.nessieisreal.com/accounts/<checking_id>/transfers. The comparison uses available_cents (balance minus pending holds), not balance_cents. A transfer that fits the posted balance can still fail if other debits are pending. Per the guide in the spec's info.description, nothing is created on this 422. Sibling types are credit_limit_exceeded (card without enough credit) and insufficient_rewards. The check runs again at settlement: if money moved in between, the already-created pending transaction ends up declined with decision_reason: insufficient_funds instead of a 422, so handle both paths. Amounts are integer cents (amount_cents), unlike v1's dollar amount, so a v1-style 500 means $5.00. In a generated Go client (oapi-codegen) this 422 decodes cleanly into ErrorModel (status is an int here), which is a quick way to confirm your error handling works.