Adds address validation errors for CMRAs and registered agents to Accounts v1 and Accounts v2
Adds two values to the [requirements.errors[].code](https://docs.stripe.com/api/accounts/object.md?api-version=2026-09-30.endive#account_object-requirements-errors-code) and [future_requirements.errors[].code](https://docs.stripe.com/api/accounts/object.md?api-version=2026-09-30.endive#account_object-future_requirements-errors-code) enum properties on v1 objects, and to the [requirements.entries[].errors[].code](https://docs.stripe.com/api/v2/core/accounts/object.md?api-version=2026-09-30.endive#v2_account_object-requirements-entries-errors-code) and [future_requirements.entries[].errors[].code](https://docs.stripe.com/api/v2/core/accounts/object.md?api-version=2026-09-30.endive#v2_account_object-future_requirements-entries-errors-code) enum properties on v2 Accounts: Integrations that read requirement error codes from Accounts v1 or Accounts v2 can now receive invalid_address_cmra_address and invalid_address_registered_agent_address. If your code uses strict enum matching or doesn’t handle unknown error codes, it can fail when it encounters these values.
docs.stripe.comquote checked- behaviour change
- Your codeby hand
Nemotron fixes
| [Adds address validation errors for CMRAs and registered agents to Accounts v1 and Accounts v2](https://docs.stripe.com/changelog/endive/2026-09-30/address-validation-cmra-registered-agents-accounts-v2.md) | Issuing, Treasury | Breaking | api |
Integrations that read requirement error codes from Accounts v1 or Accounts v2 can now receive `invalid_address_cmra_address` and `invalid_address_registered_agent_address`. If your code uses strict enum matching or doesn’t handle unknown error codes, it can fail when it encounters these values.
What Teire looks for in your code
nothing to search for: checked by hand
Does it reach your code?