Belgium IBAN

Anatomy of the official example

BE68539007547034

• Country code
• Check digits
• Bank 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.

The bank code of this official example is not allocated in Banque nationale de Belgique, bank identification codes (Protocol Secretariat): the API says so as it is, which is the expected behaviour on a demonstration IBAN.

What the API checks on a Belgium IBAN

• The length, the charset of every field and the mod-97 check digits.
• The bank code against Banque nationale de Belgique, bank identification codes (Protocol Secretariat), refreshed monthly: institution, matching BIC, status.
• The country's SEPA reachability and the open schemes (SCT, SDD, SCT Inst).
• The Verification of Payee duty that does, or does not, bind the country's providers.

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": "BE",
    "name": "Belgium"
  },
  "bic": null,
  "bank_code_check": {
    "value": "539",
    "status": "not_in_register",
    "reason": "not_allocated",
    "match": null,
    "register": "Banque nationale de Belgique, bank identification codes (Protocol Secretariat)",
    "authoritative": true,
    "as_of": "2026-09"
  },
  "sepa": {
    "member": true,
    "schemes": [
      "SCT",
      "SDD",
      "SCT_INST"
    ],
    "vop_required": true,
    "vop_participant": null,
    "basis": "country_default"
  },
  "issuer": null,
  "risk_indicators": {
    "country_risk": "standard",
    "sepa_reachable": true,
    "vop_coverage": true,
    "test_bic": false
  }
}