Normalization
Remove permitted spacing, standardize casing and return only a masked IBAN.
Normalize an IBAN and verify its country structure, length, and checksum locally.
Responses include a check timestamp and explicit boundaries, so your application can distinguish a negative result from an unavailable source or missing identity.
POST /v1/iban/check
{ "iban": "DE89 3704 0044 0532 0130 00" }
{
"valid": true,
"normalized_masked": "DE89**************3000",
"checks": { "checksum_valid": true },
"account_status": "not_checked"
}Validate IBAN format, country structure, expected length and MOD-97 checksum locally without claiming that a bank account exists.
Remove permitted spacing, standardize casing and return only a masked IBAN.
Check the country code and expected country-specific IBAN length.
Run the deterministic checksum defined by the IBAN standard.
A valid format and checksum do not prove that the account exists, is open, belongs to a named person or can receive a payment.
Call /v1/iban/check from this workflow and retain the returned evidence with the business event.
Call /v1/iban/check from this workflow and retain the returned evidence with the business event.
Call /v1/iban/check from this workflow and retain the returned evidence with the business event.
Need the request schema or complete response fields? Continue to the API reference.
No. It means the identifier has a valid country structure, length and checksum. Account status is not checked.
The normal response and ordinary application logs use a masked value. Sensitive raw inputs should not be written to general logs.
The initial structure and checksum checks are deterministic and run locally without an upstream validation fee.