> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.mangopay.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.mangopay.com/_mcp/server.

# 121019

<table>
  <tbody>
    <tr>
      <th class="header">
        Error message
      </th>

      <td class="table-content">
        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.
      </td>
    </tr>

    <tr>
      <th class="header">
        Description
      </th>

      <td class="table-content">
        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.
      </td>
    </tr>

    <tr>
      <th class="header">
        Categories
      </th>

      <td class="table-content">
        Payout

        \


        Bank account
      </td>
    </tr>
  </tbody>
</table>

> **Note**
>
> **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](https://hub.mangopay.com/) (***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](https://www.swift.com/standards/iso-20022/iso-20022-faqs/iso-20022-removal-unstructured-address) 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:

**`v2 Bank Account`**

```json v2 Bank Account
{
  //...
  "Address": "6 rue de la Cité, Appartement 3, Paris, île-de-France, 75003, FR"
  //...
}
```

**`v2.01 Bank Account`**

```json v2.01 Bank Account
{
  //...e
  "Address": {
    "AddressLine1": "6 rue de la Cité",
    "AddressLine2": "Appartement 3",
    "City": "Paris",
    "Region": "île-de-France",
    "PostalCode": "75003",
    "Country": "FR"
  }
  //...
}
```

**`Recipient (v2.01)`**

```json Recipient (v2.01)
{
  //...
  "Address": {
    "AdedressLine1": "6 rue de la Cité",
    "AddressLine2": "Appartement 3",
    "City": "Paris",
    "Country": "FR",
    "PostalCode": "75003",
    "Region": "île-de-France"
  }
  //...
}
```

### 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.

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](https://hub.mangopay.com/) (***Company profile*** > ***Documents*** tab).

The affected `BankAccountId` values can be retrieved via the [GET View a Recipient](/api-reference/recipients/view-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](/api-reference/recipients/create-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](/guides/sca/recipients) to authenticate the action, unless your platform has their [consent to act via proxy](/guides/sca/proxy-management).