Integrate IBAN checks into your software
Try a validation, inspect the response, then connect your application through the API or an existing integration.
Explore the API workflow23 characters: the country code, two check digits, then the BBAN cut as below.
AE070331234567890123456
The example comes from the ISO 13616 registry; it belongs to nobody. Positions count from the first character of the IBAN.
| ISO code | AE |
|---|---|
| Length | 23 characters |
| Check digits | positions 3 to 4, ISO 7064 mod 97-10 |
| Bank code | positions 5 to 7 · 3!n |
| Account number | positions 8 to 23 · 16!n |
| Official example | AE07 0331 2345 6789 0123 456 |
| SEPA area | outside the SEPA area |
| Verification of Payee | no duty to date |
| Bank-code register | IBANforge composite map, assembled from BIC directories (not a national register) |
SWIFT notation: n = digits, a = upper-case letters, c = alphanumeric characters; the exclamation mark fixes the exact length.
The block below is the route's own answer, produced by the same code that serves api.ibanforge.com, on the register as of the date shown. Nothing is edited.
{
"valid": true,
"country": {
"code": "AE",
"name": "United Arab Emirates"
},
"bic": {
"code": "BOMLAEADXXX",
"bic8": "BOMLAEAD",
"bank_name": "MASHREQBANK PSC",
"city": "DUBAI",
"source": "IBANforge curated bank-code map",
"as_of": "2026-09",
"basis": "curated_map",
"authoritative": false,
"lei": "5493000SA3K24EQKA103"
},
"bank_code_check": {
"value": "033",
"status": "verified",
"match": "register",
"register": "IBANforge composite bank-code map (assembled from BIC directories, not a national bank-code register)",
"authoritative": false,
"as_of": "2026-09"
},
"sepa": {
"member": false,
"schemes": [],
"vop_required": false,
"vop_participant": false,
"basis": "country_default"
},
"issuer": {
"type": "bank",
"name": "MASHREQBANK PSC",
"classification": "default"
},
"risk_indicators": {
"country_risk": "standard",
"sepa_reachable": false,
"vop_coverage": false,
"test_bic": false
}
}Choose a first step for your software or your supplier file.
Try a validation, inspect the response, then connect your application through the API or an existing integration.
Explore the API workflowUpload a CSV or Excel file and preview the findings for free. Purchase the annotated workbook if you need the full report. No account or subscription required.
Explore the file auditAvailable bank information varies by country and source. These checks do not confirm the account holder or guarantee that a payment will succeed.
Source: ISO 13616 registry for the length, layout and example; API answer captured on 2026-09-23.