IBAN Transfer Failed: 7 Reasons Your International Payment Was Rejected

An IBAN transfer failure is one of the most frustrating experiences in international banking — your money leaves your account, processing takes a day or more, and then the transfer comes back with a terse rejection code and sometimes a fee deducted. Understanding why IBAN payments get rejected — and how to prevent each failure mode — saves time, money, and the stress of chasing delayed payments.

Here are the seven most common reasons an IBAN transfer is rejected, with specific diagnostic steps and fixes for each.

Reason 1: Invalid Check Digits (MOD-97 Failure)

Every IBAN contains two check digits at positions 3–4, calculated using the MOD-97 algorithm. When a payment processor receives an IBAN, this calculation is the first thing it runs. If the check digits do not match the rest of the number, the IBAN is structurally invalid — it was either typed incorrectly or fabricated.

How it happens: A single transposed digit anywhere in the IBAN — swappingDE89 to DE98, or changing one digit in the account number — almost always produces a MOD-97 mismatch.

Fix: Paste the IBAN into ibanchecker.cash before initiating any transfer. The validator runs MOD-97 instantly and highlights which part of the IBAN is invalid. Get a fresh copy of the IBAN directly from the recipient — do not retype it; copy-paste from the original source.

Reason 2: Wrong Country Length

Every country that uses IBANs has a fixed, mandatory length. German IBANs (DE) are always 22 characters. French IBANs (FR) are always 27 characters. UK IBANs (GB) are always 22 characters. An IBAN with the wrong character count for its country code is immediately rejected.

How it happens: A recipient provides an IBAN verbally or in a poorly formatted email. One character is missed or doubled during transcription. Or a legacy system truncates the field.

Fix: Count the characters (excluding spaces). Cross-reference the count against the country IBAN format table. If the count is wrong, request the IBAN again from the recipient in writing.

Reason 3: BIC / SWIFT Code Mismatch

Many international SWIFT transfers require both an IBAN and a BIC (Bank Identifier Code). When the BIC you provide does not correspond to the bank embedded in the IBAN — for example, you provide Barclays' BIC but the IBAN belongs to an HSBC account — the receiving bank's system detects the inconsistency and rejects the transfer.

How it happens: Recipients sometimes provide a BIC from memory while the IBAN is from their bank statement — and they have accounts at different institutions. Or a company's finance team uses an old BIC that changed after a bank merger.

Fix: Use the ibanchecker.cash SWIFT directory to look up the correct BIC for any bank. Confirm with the recipient that the BIC matches the account's institution, not a different account they hold elsewhere.

Reason 4: SEPA Transfer Limit Exceeded

SEPA Credit Transfers within the Eurozone have no regulatory limit per transaction, but individual banks impose their own daily or per-transaction ceilings on outgoing SEPA payments — typically ranging from €10,000 to €100,000 for online banking. Exceeding your bank's limit causes the transfer to be declined before it even leaves your account.

How it happens: Large supplier payments, property deposits, or bulk payroll runs can easily exceed default online banking limits set years ago.

Fix: Contact your bank to request a temporary or permanent limit increase before initiating the transfer. Alternatively, split large transfers into multiple transactions on consecutive days — though confirm this is acceptable with the recipient first.

Reason 5: Sanctions Screening Block

Banks are legally required to screen every international transfer against government sanctions lists — OFAC (US), EU financial sanctions, UN Security Council lists, and others. If the recipient's name, bank, or country matches a sanctions entry, the transfer is frozen, rejected, and may trigger a compliance investigation.

How it happens: The recipient's name closely matches a sanctioned entity (name-matching algorithms use fuzzy logic). The recipient's bank is in a sanctioned country or has itself been sanctioned. The payment description includes flagged keywords.

Fix: If you believe the block is a false positive, contact your bank's compliance team directly with documentation proving the recipient is a legitimate business entity. This process can take several business days. For ongoing payments to high-risk jurisdictions, work with your bank's international payments desk to pre-clear the relationship.

Reason 6: Recipient Name Does Not Match the Account

In SEPA and many SWIFT transfers, banks increasingly perform name-matching verification — comparing the beneficiary name you provide against the name registered to the IBAN at the receiving bank. A significant mismatch causes the transfer to be returned.

How it happens: You transfer to "John Smith Trading Ltd" but the account is registered as "J. Smith Ltd." Or an individual uses their trading name rather than their legal name. Accents, abbreviations, and punctuation differences can also trigger mismatches in stricter systems.

Fix: Ask the recipient for the exact account name as it appears at their bank — not their trading name, not a shortened version. Use that exact string in the beneficiary name field, including any legal suffixes (Ltd, GmbH, SRL, etc.).

Reason 7: Closed, Dormant, or Frozen Account

An IBAN that was valid yesterday may point to an account that has since been closed, frozen by the bank due to inactivity, or suspended by a court order. A structurally perfect IBAN — correct length, valid check digits, matching BIC — will still be rejected if the underlying account no longer accepts credits.

How it happens: A supplier changes their banking relationship and forgets to update their invoice template. A freelancer closes their EU account after relocating. A business account is frozen pending an investigation.

Fix: For any new or irregular payment relationship, request a recent bank statement or voided check from the recipient to confirm the account is active. If a transfer is returned with a "closed account" reason code, contact the recipient immediately to obtain updated banking details.

How to Prevent IBAN Transfer Failures Before They Happen

The majority of IBAN rejections in reasons 1, 2, and 3 above are detectable before the transfer is initiated — without needing to contact your bank. Running every new IBAN through a validator takes under five seconds and eliminates the most common failure modes.

ibanchecker.cash validates the IBAN structure, checks the MOD-97 check digits, confirms the country code is a recognized IBAN country, verifies the length against the country's specification, and returns the associated bank name and BIC code — all instantly. If the IBAN is invalid, you know before the transfer, not three days after.

For finance teams processing multiple supplier payments, the bulk IBAN checker validates up to 100 IBANs simultaneously from a CSV or Excel upload — an efficient step to add to any payment run checklist.

Last updated: June 2026