Guide

IBAN Print Format vs Digital Format

Learn the difference between spaced IBAN print format and compact digital IBAN format, why tools normalize separators, and what format checks cannot prove.

Who this guide is useful for

People copying IBANs from invoices, PDFs, emails, bank letters, country pages, and payment forms.

Compact IBAN and spaced IBAN

The digital IBAN format is the compact value with no spaces. The print format shows the same characters in groups, usually blocks of four, so people can read and compare the value more easily.

  • Print format example: DE89 3704 0044 0532 0130 00.
  • Digital format example: DE89370400440532013000.
  • Country pages can show both formats so a user can compare a readable invoice value with the compact form.

Why tools normalize separators

A user may paste an IBAN with spaces or hyphens. BankCodeKit normalizes common separators before checking the country code, length, allowed characters, and checksum.

What BankCodeKit can check

BankCodeKit can check whether the normalized IBAN matches supported country, length, character, and checksum rules. It can also show a print format so the value is easier to review.

What BankCodeKit cannot check

A normalized and checksum-passing value is still only a format result. BankCodeKit cannot confirm that an account exists, belongs to the intended payee, or is ready for payment.

Practical copy-and-review example

If an invoice shows a spaced IBAN, compare it carefully before using the compact value in a payment form.

  • Invoice text: DE89 3704 0044 0532 0130 00.
  • Payment form entry: DE89370400440532013000.
  • Local check: country DE, length 22, allowed characters, and checksum.
  • Payment reminder: verify the payee and payment instruction through a trusted channel before sending money.

Important limitations

BankCodeKit validates format and reference data only. It does not confirm account existence, account ownership, bank connectivity, sanctions status, fraud risk, payment readiness, or payment success.

  • Spacing does not prove an IBAN is real or safe to pay.
  • Normalization does not confirm account existence or ownership.
  • A passed checksum does not confirm bank connectivity, payment readiness, or payment success.
  • BankCodeKit does not upload the IBAN or contact banks while checking format.

FAQ

Are spaces part of the IBAN?

Spaces are used for readability in print format. Digital validation uses the compact value after spaces are removed.

Can I paste an IBAN with hyphens?

BankCodeKit normalizes common separators before validation, but the final value should still be reviewed carefully.

Which format should I enter in a payment form?

Many forms expect the compact digital value. Follow the instructions from your bank or payment provider.

Does print formatting confirm the account is real?

No. Print formatting only changes readability and does not verify a real account.

Sources and update note

BankCodeKit uses local IBAN reference data and browser-local format rules for country, length, character, and checksum checks. The official Swift IBAN information is used as a reference source, but BankCodeKit does not query Swift or any bank while you use the tool. Reference data is reviewed periodically and does not imply live accuracy.

BankCodeKit validates format and reference data only. It does not confirm account existence, account ownership, bank connectivity, sanctions status, fraud risk, payment readiness, or payment success.

Last reviewed: 2026-05-15 Sources: Swift IBAN Registry Reference data is reviewed periodically. BankCodeKit does not perform live bank, account, sanctions, or payment-network verification.