121019 | Mangopay docs

Error message	Payout refused because the bank account address is formatted as an unstructured string in AddressLine1 (created via an API v2 endpoint). Re-register as a Recipient and try again.
Description	The `BankAccountId` used was registered on a legacy API v2 endpoint, so the address is a single string containing the full address including city, postal code, and country. The external account must be re-registered with a structured address format.
Categories	Payout Bank account

Note – Restriction takes effect from October 15, 2026

Your platform is only impacted by this change if you registered a bank account on the API v2 (not v2.01) legacy bank account endpoints and are using it to send payouts.

Platforms identified as being impacted received an email in July 2026 with further details. Impacted platforms can find the list of BankAccountId values affected in the Mangopay Dashboard (Company profile > Documents tab).

Support for unstructured addresses ends on October 15, 2026, due to changes in industry regulations. The European Payments Council (EPC) and SWIFT are prohibiting unstructured addresses in payment messages across all SEPA schemes (SCT, SDD, and SCT Inst) and SWIFT CBPR+ cross-border flows.

If your platform did not receive an email and there is no list of bank accounts in the Dashboard, then it is likely that your platform won’t be impacted by this change. This is because all your external accounts have structured addresses, having been created via a v2.01 Bank Account endpoint or the Recipient endpoint.

Causes

This error occurs when a payout’s BankAccountId references an object created via an API v2 endpoint (rather than v2.01) for bank account registration:

POST /v2/{ClientId}/users/{UserId}/bankaccounts/iban
POST /v2/{ClientId}/users/{UserId}/bankaccounts/gb
POST /v2/{ClientId}/users/{UserId}/bankaccounts/us
POST /v2/{ClientId}/users/{UserId}/bankaccounts/ca
POST /v2/{ClientId}/users/{UserId}/bankaccounts/other

The v2 Bank Account endpoints used a single string for the address. The v2.01 Bank Account endpoints and the Recipient endpoint use structured address data. The difference is shown below:

1 {
2   //...
3   "Address": "6 rue de la Cité, Appartement 3, Paris, île-de-France, 75003, FR"
4   //...
5 }

What to do

From October 15, 2026, a Bank Account with unstructured address data can no longer be used for payouts. The external accounts with unstructured addresses need to be re-registered before they can be used again.

The affected BankAccountId values can be retrieved via the GET View a Recipient endpoint, in which case the AddressLine1 property contains the full address, including city, postal code, and country. These bank accounts are also visible in the Dashboard on the corresponding User page.

Each external account needs to be re-registered using POST Create a Recipient before it can be used for a payout.

If the external account is not re-registered, any payout attempts using it from October 15, 2026 automatically become FAILED with the ResultCode 121019.

Re-registering the external account requires the user to perform SCA to authenticate the action, unless your platform has their consent to act via proxy.