Montenegro IBAN

Anatomy of the official example

ME25505000012345678951

• 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.

What the API checks on a Montenegro IBAN

• The length, the charset of every field and the mod-97 check digits.
• The bank code against our composite map assembled from BIC directories: a BIC and a bank name when they are listed, without the weight of a national register.
• The country's SEPA reachability and the open schemes (SCT).
• 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": "ME",
    "name": "Montenegro"
  },
  "bic": null,
  "bank_code_check": {
    "value": "505",
    "status": "not_in_register",
    "reason": "absent_from_reference_data",
    "match": null,
    "register": "IBANforge composite bank-code map (assembled from BIC directories, not a national bank-code register)",
    "authoritative": false,
    "as_of": "2026-09"
  },
  "sepa": {
    "member": true,
    "schemes": [
      "SCT"
    ],
    "vop_required": false,
    "vop_participant": null,
    "basis": "country_default"
  },
  "issuer": null,
  "risk_indicators": {
    "country_risk": "standard",
    "sepa_reachable": true,
    "vop_coverage": false,
    "test_bic": false
  }
}