Bosnia & Herzegovina IBAN
20 characters: the country code, two check digits, then the BBAN cut as below.
Anatomy of the official example
BA391290079401028494
- Country code
- Check digits
- Bank code
- Branch code
- Account number
- National check or other
The example comes from the ISO 13616 registry; it belongs to nobody. Positions count from the first character of the IBAN.
| ISO code | BA |
|---|---|
| Length | 20 characters |
| Check digits | positions 3 to 4, ISO 7064 mod 97-10 |
| Bank code | positions 5 to 7 · 3!n |
| Branch code | positions 8 to 10 · 3!n |
| Account number | positions 11 to 18 · 8!n |
| Official example | BA39 1290 0794 0102 8494 |
| SEPA area | outside the SEPA area |
| Verification of Payee | no duty to date |
| Bank-code register | no bank-code data we may reuse: structure and check digits only |
SWIFT notation: n = digits, a = upper-case letters, c = alphanumeric characters; the exclamation mark fixes the exact length.
What the API checks on a Bosnia & Herzegovina IBAN
- The length, the charset of every field and the mod-97 check digits.
- IBANforge holds no bank-code data it may reuse for this country: beyond the structure, the API cannot say whether the bank code exists, and answers that the code was not consulted.
- The country is outside SEPA: a SEPA transfer will not reach this account.
What the API answers for this code
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": "BA",
"name": "Bosnia and Herzegovina"
},
"bic": null,
"bank_code_check": {
"value": "129",
"status": "unavailable",
"reason": "no_reference_data_for_country",
"match": null,
"register": null,
"authoritative": false,
"as_of": "2026-10"
},
"sepa": {
"member": false,
"vop_required": false
},
"issuer": null,
"risk_indicators": {
"country_risk": "elevated",
"sepa_reachable": false,
"vop_coverage": false,
"test_bic": false
}
}Source: ISO 13616 registry for the length, layout and example; API answer captured on 2026-10-21.