Is this Montenegrin IBAN example real?

No. It is a synthetic value generated to pass MOD 97 and the 22-character ME length check. It does not correspond to any real Montenegro bank account, so it is safe for test fixtures and demos but must never be used for an actual transfer.

Why use a synthetic Montenegrin IBAN instead of a real one?

Real Montenegrin IBANs are private account identifiers; publishing one would expose a customer's account. A MOD 97-valid synthetic example gives you the same format and checksum behavior for testing without touching any real account.

Can I load this ME example into the validator?

Yes. The "Validate this example" link below loads this sample straight into the IBAN validator so you can see the green check and the full breakdown, exactly as a real Montenegrin IBAN would render.

What do I pair with a Montenegrin IBAN for a wire?

For most cross-border payments into Montenegro you need the IBAN plus the receiving bank's SWIFT/BIC code. This Montenegrin IBAN example covers the account side; look up the bank's BIC separately to complete the wire instructions.

IBAN example · ME

Montenegrin IBAN example

This page gives you a sample Montenegrin IBAN that passes all ISO 13616 checks — correct character set, exactly 22 characters, and MOD 97 check digits that yield a remainder of 1. This Montenegrin IBAN is a synthetic test value for forms and integrations, not a real account. Use it for payment-integration tests, form demos, or to learn how a ME IBAN is structured. It does not map to a real bank account, so never send money to it. Below you will find the full IBAN, a field-by-field breakdown, notes on testing, and the SWIFT/BIC code you would pair with it for a complete cross-border payload.

Sample IBAN

ME89 0120 1234 5678 9012 01

ME89012012345678901201

Validate this sample →Montenegrin IBAN overview

Field-by-field breakdown

The breakdown below splits the sample Montenegrin IBAN (ME89012012345678901201) into its country code, check digits, and BBAN fields, applying the 3!n13!n2!n pattern so each field is labeled with its length and allowed characters. This is the same field-by-field view the IBAN validator produces for any ME IBAN you paste, so you can compare a real Montenegrin IBAN against this reference structure.

Country code

ISO 3166 — Montenegro

Check digits

MOD 97-10 checksum

BBAN field 1

3 digits · digits (0–9)

012

BBAN field 2

13 digits · digits (0–9)

0123456789012

BBAN field 3

2 digits · digits (0–9)

How to use this Montenegrin IBAN example

A common use case is testing a payment form that accepts Montenegrin IBANs: paste the sample into your form to confirm it accepts 22-character ME input and rejects malformed values. You can also load this example straight into the IBAN validator to see the green check, or open the Montenegrin IBAN format page for the full structure spec. For end-to-end testing of a cross-border flow, pair this IBAN with the receiving bank's SWIFT/BIC code.

Reading the Montenegrin IBAN structure

Reading the sample Montenegrin IBAN left to right: the first two characters (ME) are the ISO 3166 country code for Montenegro; the next two are the MOD 97 check digits, chosen so the whole number passes the checksum; and the remaining 18 characters are the BBAN, which encodes the bank and account under Montenegro's national format. Because the BBAN layout is fixed for Montenegro, you can predict which characters are the bank code and which are the account number just from the 3!n13!n2!n pattern — and that is exactly what the field-by-field breakdown below shows.

Testing with this Montenegrin IBAN

For QA and integration work, this Montenegrin IBAN example is most useful in three places. In a payment form, paste it to confirm the field accepts 22-character ME input and rejects values that are too short, too long, or have a bad country prefix. In a MOD 97 unit test, assert that the example returns a remainder of 1 and that flipping any single digit makes it fail. In an end-to-end test, pair the IBAN with a Montenegro SWIFT/BIC code so the full wire payload looks realistic. Because the example is synthetic, it will never collide with a real Montenegro account, which makes it safe to commit to test fixtures.

Montenegrin IBAN example and SWIFT codes

If you are testing a full international payment into Montenegro, you will usually need a SWIFT/BIC code alongside this IBAN. Look up the receiving Montenegro bank's BIC with a SWIFT code lookup tool to build a realistic ME wire payload around this Montenegrin IBAN.

Montenegrin IBAN example FAQ

Is this Montenegrin IBAN example real?: No. It is a synthetic value generated to pass MOD 97 and the 22-character ME length check. It does not correspond to any real Montenegro bank account, so it is safe for test fixtures and demos but must never be used for an actual transfer.
Why use a synthetic Montenegrin IBAN instead of a real one?: Real Montenegrin IBANs are private account identifiers; publishing one would expose a customer's account. A MOD 97-valid synthetic example gives you the same format and checksum behavior for testing without touching any real account.
Can I load this ME example into the validator?: Yes. The "Validate this example" link below loads this sample straight into the IBAN validator so you can see the green check and the full breakdown, exactly as a real Montenegrin IBAN would render.
What do I pair with a Montenegrin IBAN for a wire?: For most cross-border payments into Montenegro you need the IBAN plus the receiving bank's SWIFT/BIC code. This Montenegrin IBAN example covers the account side; look up the bank's BIC separately to complete the wire instructions.

⚠️ This is a synthetic test IBAN. It passes format and MOD 97 checks but does not map to a real bank account. Never send money to it.

Montenegrin IBAN overview →ME IBAN format spec Validate this example