Learn about addresses in Mambu Payments (formerly Numeral)
Address structure
Addresses are used in any party, like originating or receiving party, or agent, like banks. The attributes allowed in payment orders and incoming payments are the following.
Payment order attributes
| Attribute | Description |
|---|---|
| building_number string | Building / street number of the originating/receiving party. |
| street_name string | Street name of the originating / receiving party. |
| postal_code string | Postal / zip code of the originating / receiving party. |
| region_state string | Region or state of the originating / receiving party. |
| city string | City / town name of the originating / receiving party. |
| country string | ISO 3166 alpha-2 country code of the originating / receiving party. For instance: GB, FR, or US. |
| line_1 string | Line 1 (unstructured) of the originating / receiving party. |
| line_2 string | Line 2 (unstructured) of the originating / receiving party. |
Incoming payment attributes
| Attribute | Description |
|---|---|
| building_number string | Building / street number of the originating/receiving party. |
| street_name string | Street name of the originating / receiving party. |
| postal_code string | Postal / zip code of the originating / receiving party. |
| region_state string | Region or state of the originating / receiving party. |
| city string | City / town name of the originating / receiving party. |
| country string | ISO 3166 alpha-2 country code of the originating / receiving party. For instance: GB, FR, or US. |
| line_1 string | Line 1 (unstructured) of the originating / receiving party. |
| line_2 string | Line 2 (unstructured) of the originating / receiving party. |
| department string | Department of the originating / receiving party. Only supported for incoming payments. |
| sub_department string | Sub-department of the originating / receiving party. Only supported for incoming payments. |
| building_name string | Building name of the originating / receiving party address. Only supported for incoming payments. |
| floor string | Floor number of the originating / receiving party address. Only supported for incoming payments. |
| postal_box string | Post office box of the originating / receiving party. Only supported for incoming payments. |
| room string | Room number of the originating / receiving party address. Only supported for incoming payments. |
| city_location_name string | Town location name of the originating / receiving party. Only supported for incoming payments. |
| district_name string | District name of the originating / receiving party. Only supported for incoming payments. |
Structured vs. hybrid vs. unstructured address
The key differences between unstructured, hybrid and structured addresses are the following.
Unstructured address
Starting from November 15, 2026, unstructured addresses will be decommissioned from any SEPA flows. SEPA participants must use either structured or hybrid addresses.
An unstructured address contains a country (usually in the form of an ISO-3166 country code) and up to two address lines.
In Mambu Payments, it means using the country, and line_1 / line_2 properties. Address lines can contain anything relevant that identifies an address, hence the name unstructured.
Hybrid address
Hybrid addresses have been introduced in the SEPA rulebooks 2025 since October 5, 2025.
A hybrid address contains a country (usually in the form of an ISO-3166 country code), a city and up to two address lines.
In Mambu Payments, it means using the country, city and at least line_1 properties. It can optionally have any other address properties.
Structured address
A structured address must include a country and city as well as split street name and building number.
In Mambu Payments, it means filling the country and city properties as well as optionally filling other properties like building_number, street_name, region_state, and postal_code, except the line_1 and line_2 unstructured properties.