View all services
Talk to QA Advisor
Free tool · Test data

IBAN checker and validator

Every check an IBAN has to pass, shown separately so you can see which one failed and why. Includes BIC validation, the test and passive markers inside a BIC, and documented sample IBANs for test data.

Runs entirely in your browser. Nothing you enter is sent to a server.

Spaces, hyphens and lower case are accepted.

Sample IBANs

Valid IBAN for United Kingdom

Well formed and the checksum holds. Only the receiving bank can confirm the account exists.

Country
GB
Check digits
82
Length
22
Account part
WEST12345698765432
GB82 WEST 1234 5698 7654 32
  • PassCharacters. Only letters and digits, once spaces are removed.
  • PassStructure. Two-letter country code, then two check digits, then the account part.
  • PassCountry. GB is United Kingdom.
  • PassLength. 22 characters, correct for United Kingdom.
  • PassCheck digit range. Check digits are within the valid range of 02 to 98.
  • PassChecksum (mod 97). Passes the ISO 7064 mod 97-10 check.

BIC and SWIFT code checker

Checks structure and country, and reads the test and passive markers in the location code.

8 or 11 characters. An 8-character BIC refers to the primary office.

Valid BIC format

Bank
DEUT
Country
DE
Location
FF
Branch
500
  • PassLength. 11 characters: includes a branch code.
  • PassFormat. Four-letter bank code, two-letter country, two-character location, optional three-character branch.
  • PassCountry. DE is a valid ISO country code.
How to use

How to use the IBAN and BIC validator

  1. 1Paste an IBAN. Spaces, hyphens and lower case are accepted, as they should be by any payment form.
  2. 2Read each check: characters, structure, country, length, check digit range and the mod 97 checksum. A failure names the check that failed.
  3. 3Validate the BIC separately if your flow collects one. Its location code reveals whether it is a test BIC.
  4. 4Use the sample IBANs for test data. They are documented examples that pass every check.

What the checks cover

An IBAN is a two-letter country code, two check digits and a country-specific account part of fixed length. Validation confirms the country is known, the total length is right for that country, and the check digits are consistent with the rest of the number under the ISO 7064 mod 97-10 algorithm. That checksum catches all single-character errors and almost all transpositions, which is most of what goes wrong when a person types an IBAN.

Check digits of 00, 01 and 99 can never be produced by the algorithm, so they are rejected before the checksum runs. It is a small rule, and a surprising number of validators omit it.

Valid is not the same as real

A valid IBAN is well formed. Whether the account exists, is open and belongs to the named payee is something only the receiving bank can confirm. That gap is what payee verification services exist to close: Confirmation of Payee in the UK, and Verification of Payee, which payment providers in the euro area have had to offer on euro credit transfers since October 2025.

If your product sends payments to an IBAN, test both halves: format validation in the form, and the behaviour when the bank or the verification service reports a mismatch, a closed account or a name that does not match.

What a payment form should do with an IBAN

Accept the IBAN the way people copy it: with spaces, in lower case, sometimes with a trailing space from the clipboard. Normalise before validating and before storing. Display it back in groups of four, which is how people check it against a paper document. Validate in the browser for immediate feedback, and again on the server, because client-side validation is a convenience rather than a control.

Never truncate an IBAN for display without showing the country code and the last four characters, which are the parts a person uses to recognise their own account.

Reading a BIC

A BIC, or SWIFT code, is eight or eleven characters: a four-letter bank code, a two-letter country code, a two-character location code and an optional three-character branch code. An eight-character BIC refers to the primary office, equivalent to a branch code of XXX.

The second character of the location code carries meaning. A 0 marks a test BIC that cannot be used for live payments, and a 1 marks a passive participant on the SWIFT network. When a payment test fails for reasons that look like a bank refusal, the BIC is worth checking. For euro payments between EU countries an IBAN alone has been enough since 2016, so a form that insists on a BIC for one is asking for more than it needs.

QAble service

Banking and payments testing

QAble tests cross-border payment flows end to end, including payee verification, rejected payments and the reconciliation that follows.

Explore the service
FAQ

Frequently asked questions

How is an IBAN validated?

Move the first four characters to the end, replace every letter with two digits where A is 10 and Z is 35, and divide the resulting number by 97. A valid IBAN leaves a remainder of 1. Before that, the country code must be recognised and the length must match the length fixed for that country.

What is an example of a valid IBAN?

GB82 WEST 1234 5698 7654 32 is the most widely used example: a UK IBAN that passes every check. DE89 3704 0044 0532 0130 00 is the common German example. Both are in the sample list above. Use them as test data for format validation, never as a destination for real payments.

What is the difference between a BIC and a SWIFT code?

In practice there is none. BIC is the name the ISO 9362 standard gives the code, and SWIFT code is the everyday name, after the network that registers it. Both mean the same 8 or 11 characters, and this tool checks the format of either.

Does a valid IBAN mean the account exists?

No. Validation confirms the IBAN is well formed and internally consistent. Only the receiving bank can confirm that the account exists and belongs to the named payee.

Can I use the sample IBANs in tests?

Yes. They are documented examples that appear throughout public descriptions of the standard, and they pass every check. Use them as test data for format validation. Do not send live payments to them.

Why will this tool not fix my check digits?

Calculating correct check digits for an arbitrary account number produces a plausible identifier that could belong to a real account. A validator should tell you whether an IBAN is valid, not manufacture valid ones.

What does the X in an 8-character BIC mean?

An eight-character BIC has no branch code and refers to the institution’s primary office. It is equivalent to the same code with XXX appended as the branch.

Is the IBAN I type sent anywhere?

No. Validation runs entirely in your browser and nothing is sent to a server.

Need the edge cases found for you?

QAble testers work through the inputs, payment paths and data that break products in production, before your users find them.

Talk to QA Advisor