The same familiar envelope
If you already use the Wealthreader API, MyBankMatch responds with the same structure and the same integration habits.
Developers
MyBankMatch is an endpoint of the Wealthreader API: HTTPS, form parameters and a JSON response. Send the IBAN and the name, and receive the verification result.
To activate the service, we link one account of your company once from the Wealthreader Customers panel: it is the account that performs the Verification of Payee queries. Your customers and suppliers do not have to do anything.
A POST request with your API key, the account’s IBAN and the name of the person or company claiming to be its holder.
curl https://api.wealthreader.com/my-bank-match/ \
-d api_key=$API_KEY \
-d iban=ES9121000418450200051332 \
--data-urlencode name="Talleres Ruiz SL"
The response arrives in the same call, with the same envelope as the rest of the API: success, payload and statistics.
{
"success": true,
"payload": {
"result": "MATCH"
},
"statistics": {
"SESSION": "…",
"execution_time": 1.84,
"warnings": []
}
}
If the name is similar but not identical, the response includes suggested_name with the name held by the bank.
The values are illustrative.
{
"success": true,
"payload": {
"result": "PARTIAL_MATCH",
"suggested_name": "Talleres Ruiz Martínez SL"
}
}
Parameters, results and errors for POST /my-bank-match/. The full detail is in the integration guide.
| Parameter | Validation |
|---|---|
api_key | Your API key, with the MyBankMatch product active and quota available. |
iban | IBAN from a SEPA country. Spaces and letter case are ignored; the length for its country and the check digits are validated. |
name | Name of the person or company claiming to be the holder, up to 140 characters. |
result | Meaning | Uses quota | Additional fields |
|---|---|---|---|
MATCH |
The name matches the account holder. | Yes | — |
PARTIAL_MATCH |
The name is similar to the holder’s; suggested_name carries the name held by the bank. | Yes | suggested_name |
NO_MATCH |
The name does not correspond to the account holder. | Yes | — |
NOT_CONFIGURED |
Your key does not yet have a linked account; setup_url leads to the linking process. | No | setup_url |
REAUTH_REQUIRED |
The linked bank requires you to authenticate again; setup_url leads to the reconnection. | No | setup_url, reason_code |
NOT_POSSIBLE |
The bank could not verify the account at this time; reason gives the cause. | No | reason |
| Error code | Meaning |
|---|---|
2 | Invalid call: method, API key, inactive product or call limit. |
4000 | Invalid IBAN. |
4001 | Invalid account holder name. |
1 | Internal error. |
Errors are not charged and do not use up quota.
If you already use the Wealthreader API, MyBankMatch responds with the same structure and the same integration habits.
The IBAN and the name are validated before the bank is queried: malformed data returns an error instantly.
MATCH, PARTIAL_MATCH and NO_MATCH use up quota. Queries that do not reach a conclusion do not.
The step-by-step guide and the API reference describe the full contract, with examples.
Open the MyBankMatch guide (opens in a new tab) Open the API reference (opens in a new tab) Request access
We will show you MyBankMatch with your business’s payments and onboarding flows.