The IBAN Survival Guide
What’s in the bowl, who can slurp from it, and what to do when it spills.
Decode an IBAN field by field with the IBAN Decoder & Validator. It runs in your browser. Nothing is sent.
1. The short answer
Your IBAN is not a secret, but it is not harmless either.
Nobody can log in to your bank or push money out of your account with an IBAN alone. What they can do is try to pull money out by direct debit, pay for their own subscriptions with your account, or call you sounding exactly like your bank.
An IBAN is printed on invoices, sent to landlords and typed into every subscription form. It was designed to be shared. That is why a leak is a kitchen spill and not a kitchen fire: annoying, worth cleaning up properly, rarely a reason to close the account.
This guide covers the SEPA area. It is general information, not legal or financial advice. Your bank’s terms decide the details.
2. Anatomy of an IBAN
An IBAN (International Bank Account Number, ISO 13616) has three ingredients and a maximum of 34 characters.
| Part | Length | Example (DE89 3704 0044 0532 0130 00) | What it is |
|---|---|---|---|
| Country code | 2 letters | DE | ISO 3166 country |
| Check digits | 2 digits | 89 | Result of the mod-97 calculation |
| BBAN | Fixed per country | 370400440532013000 | The national account number: bank code, sometimes branch code, account number, sometimes a national check digit |
Each country fixes its own length and recipe. Germany uses 22 characters, Luxembourg 20, France 27, Norway only 15, Malta 31.
The checksum in three steps
- Move the first four characters to the end.
- Replace each letter with two digits: A = 10, B = 11, up to Z = 35.
- Divide the resulting number by 97. The remainder must be 1.
The checksum catches any single mistyped digit and any two swapped neighbouring digits, but not every possible error.
What a valid checksum does not prove
- That the account exists.
- That the account is still open.
- That it belongs to the person or company who gave it to you.
A fraudster’s IBAN has a perfect checksum too. Well-formed noodles, wrong kitchen.
3. What someone can do with your IBAN alone
| They cannot | They can |
|---|---|
| Log in to your online banking | Send you money |
| Make a transfer out of your account | Submit a direct debit against your account using a forged or invented mandate |
| Pay by card or withdraw cash | Enter your IBAN as the payment method at a merchant that accepts direct debit |
| See your balance or transactions | See which country and bank you use (it is encoded in the IBAN) |
| Change your account details | Use it to sound credible in a phishing call or email |
Everything in the right-hand column gets easier when the IBAN leaks together with your name, address, date of birth or a copy of your ID.
4. The risk menu, from most to least likely
4.1 Phishing and vishing with your IBAN as bait
How it works: someone calls or writes pretending to be your bank, and “proves” it by reading out your IBAN. The goal is your login, a confirmation code, or a “safe account” transfer that you authorise yourself.
Who pays: often you. A transfer you approved yourself is much harder to recover than a debit you never authorised.
How you notice: urgency, a request for codes, a request to move money, a link to “confirm your account”.
4.2 Fraudulent direct debit
How it works: under the SEPA Core scheme, the creditor keeps the mandate. Your bank does not check it before the first debit. A fraudster with access to a creditor account can submit a collection against your IBAN with a mandate that never existed.
Who pays: in the end, not you, if you dispute in time (section 8). In the meantime the money is gone and other payments may bounce.
How you notice: an unknown creditor name or creditor identifier on your statement, usually small amounts first.
4.3 Someone shops with your IBAN
How it works: the fraudster signs up to a legitimate service (telecom, streaming, parking, donations, gambling) and enters your IBAN. The merchant is real and the mandate looks real; the signer is not you.
Who pays: you get refunded if you dispute. The merchant carries the loss.
How you notice: a debit from a well-known company you have no contract with.
4.4 Invoice and IBAN-substitution fraud (businesses)
How it works: an email, often from a compromised mailbox, announces that a supplier has “changed bank”. The next payment goes to the fraudster. This attack does not need your IBAN; it replaces someone else’s.
Who pays: the paying company, almost always.
How you notice: new bank details arriving by email, a different country code than usual, pressure to pay quickly, a Verification of Payee warning (section 9). More local variants in EU Scam Patterns.
4.5 Identity fraud
How it works: an IBAN plus an ID copy, a proof of address or a signature sample is enough at some providers to open contracts or credit in your name.
Who pays: it depends. Cleaning up takes months.
How you notice: letters about contracts you never signed, debt collection notices, credit refusals.
5. How to protect your IBAN
You cannot keep an IBAN secret. You can make it a poor ingredient for fraud.
For individuals
- Turn on notifications for every debit, or at least for new direct debits. Detection speed is your main defence.
- Read your statement monthly. Your refund rights have deadlines.
- Ask your bank for direct debit controls. EU law gives you the right to limit direct debits to a maximum amount or frequency, to block all direct debits, to block named creditors (blacklist) or to allow only named creditors (whitelist). Banks must offer this whenever the payer or the payee is a consumer (Article 5(3)(d) of Regulation (EU) 260/2012). How you activate it depends on the bank: some offer it in the app, some only on request.
- Use a separate account for incoming payments and public use (freelance invoices, marketplace sales, club memberships), and keep savings elsewhere.
- Do not send IBAN, ID copy and signature in the same message unless a regulated party really needs all three.
- Savings accounts that do not accept direct debits are less exposed. Check your account type.
- Never confirm or “verify” an IBAN, code or login to someone who contacted you. Hang up and call the number on your card.
For businesses
- Call back before any supplier bank change, on a number you already had, never one from the email that announces the change.
- Four-eyes approval for new beneficiaries and changed bank details.
- Take Verification of Payee warnings seriously. “No match” on a supplier payment means stop, not click through.
- Clean vendor master data. Validate IBAN format on entry, log who changed bank details and when.
- If you collect direct debits: verify that the person signing the mandate controls the account (a small verification transfer, an account-ownership check, or a signed mandate with strong authentication).
- Treat IBANs as personal data when they belong to natural persons: mask them in logs and screenshots, restrict access, include them in your data breach assessment (GDPR Articles 33 and 34).
- The published IBAN on your invoices is fine. The risk for a business sits in outgoing payments, not in its own IBAN being known.
6. Your IBAN leaked: what to do
In the first 24 hours
- Read the breach notification carefully. Note exactly what leaked: IBAN only, or IBAN plus name, address, date of birth, ID.
- Turn on push or SMS alerts for all debits.
- Check the last 13 months of statements for direct debits you do not recognise.
- Reach the notifying company only through its official website, never through a link in the notification.
In the first week
- Ask your bank which direct debit mandates or creditors are active on the account, and remove what you do not recognise.
- Activate a whitelist, blacklist or amount limit (section 5).
- Dispute any unknown debit immediately (section 8).
- Warn the people who share the account.
- If an ID document leaked too, follow your country’s procedure for compromised identity documents.
For the next 13 months
- Check each statement. Fraudsters often wait months before using leaked data.
- Treat every call, SMS or email that mentions your IBAN or the breach as suspicious.
- Keep the breach notification. It is useful evidence in a dispute.
Do you need a new account?
Usually not. A new IBAN means updating your salary, rent, insurance and every subscription. Consider it only if fraudulent debits keep coming back despite blocking, or if your bank recommends it.
7. If money has already left
- Unknown direct debit: dispute it with your bank, in the app or by phone. State clearly that you never gave a mandate.
- Transfer you made to a fraudster: call your bank’s fraud line at once and ask for a recall. Speed matters most with instant payments.
- In both cases: report it to the police, keep all messages, and change your banking credentials if you typed them anywhere suspicious.
Already hit by something else too? Start with I’ve Been Hit.
8. Your rights and deadlines
| Situation | Scheme | Your right | Deadline |
|---|---|---|---|
| You gave a mandate but disagree with a debit | SEPA Core | Refund on request, no reason needed | 8 weeks from the debit date |
| You never gave a mandate (unauthorised debit) | SEPA Core | Refund after you notify the bank | Without undue delay, at the latest 13 months from the debit date |
| Authorised debit between businesses | SEPA B2B | No refund right | None |
| Unauthorised debit between businesses | SEPA B2B | Claim under PSD2 and your bank contract | 13 months by default, but a business may agree a different period with its bank |
Notes:
- The no-questions refund within 8 weeks is a right in EU law, not only a scheme rule: for SEPA direct debits the payer has “an unconditional right to a refund” (PSD2, Articles 76 and 77). The SEPA Core Rulebook applies it on a “no-questions-asked basis”. The bank has 10 business days to refund or explain a refusal.
- For an unauthorised debit, the bank must refund by the end of the next business day after you notify it, unless it has reasonable grounds to suspect fraud and reports them in writing to the national authority (PSD2, Article 73). The 13-month limit and the duty to notify “without undue delay” come from PSD2, Article 71.
- In the B2B scheme the payer’s bank checks the mandate data before the first debit, which is why there is no refund for authorised debits. A business can also agree with its bank that some of these PSD2 rules do not apply, or that other time limits do (PSD2, Article 61).
- “Without undue delay” means when you notice. Waiting months after noticing can cost you the claim.
9. Verification of Payee: the new bouncer
Since 9 October 2025, payment providers in the euro area must check that the name you typed matches the name on the IBAN before a SEPA credit transfer or an instant transfer is sent (Regulation (EU) 2024/886, which added Article 5c to Regulation (EU) 260/2012).
The European Payments Council’s scheme gives one of four answers:
| Result | Meaning | What to do |
|---|---|---|
| Match | Name and IBAN belong together | Proceed |
| Close match | Small difference; the bank shows you the registered name | Compare, correct, proceed if it makes sense |
| No match | The name does not fit this IBAN | Stop and verify through another channel |
| Check not possible | The other bank did not answer or the account type is not covered | Treat as unverified |
Three things to know:
- It covers transfers, not direct debits. It helps against invoice fraud and typos. It does nothing against a forged mandate.
- A warning does not stop you, but it shifts the risk to you. You can still send the payment. If your bank ran the check properly, it is not liable for paying the wrong person; your bank must tell you what going ahead means for your rights. If your bank failed to run the check and the payment went wrong because of it, the bank must refund you.
- Outside the euro area the obligation starts on 9 July 2027.
Businesses sending bulk payment files can opt out of the check. Doing so means accepting the risk the check would have reduced.
10. Country notes
Luxembourg
- First contact: your bank’s fraud or card-stop line.
- Unresolved dispute with a bank: first complain in writing to the bank’s complaints manager. With no satisfactory answer within one month, the CSSF offers a free, voluntary out-of-court procedure; file within one year of your complaint to the bank.
- Report fraud at a police station: the Police Grand-Ducale’s online complaint form covers thefts only. Who to contact, step by step: Reporting fraud in Luxembourg.
Germany
- BaFin: you can object to a SEPA Core direct debit you authorised up to eight weeks after the debit; for one you did not authorise, claim within 13 months.
- Report fraud to your local police station or through the online police station of your federal state (in German).
France
- Banque de France: if your bank keeps a list of creditors authorised to debit your account (“white list”), keep it up to date. Ask your bank whether it offers white and black lists for direct debits.
- Help and reporting: cybermalveillance.gouv.fr (in French).
Austria
- Oesterreichische Nationalbank: an authorised SEPA Core direct debit can be reversed within 56 days of the debit; if the mandate is missing or invalid, within 13 months. You can set a limit on direct debits or name the payees allowed to debit you.
- Unresolved dispute with a bank: the FMA does not decide individual cases. It points to ombuds, arbitration and mediation bodies, such as the Joint Conciliation Board of the Austrian Banking Industry (in German).
Belgium
- Unresolved dispute with a bank: complain to the bank first, then in writing to Ombudsfin, the financial services ombudsman. Handling takes about 90 days.
- Report fraud to the local police of your choice. The FPS Economy’s consumer reporting point does not take crime reports.
Ireland
- Unresolved dispute: complain to your provider first, then to the Financial Services and Pensions Ombudsman (FSPO). It is free, the time limit is 6 years, and its decisions are legally binding (appeal only to the High Court).
- Report fraud at your local Garda station: the online Garda form covers theft of property only.
- Central Bank of Ireland on Verification of Payee: after a “no match” you can still proceed, amend or cancel, but proceeding could mean paying someone you did not intend to pay.
Italy
- Banca d’Italia: for a direct debit you did not authorise, you have 13 months to dispute it. You can set maximum limits, block all direct debits, or give a blacklist or whitelist of payees.
- Unresolved dispute: complain in writing to the bank first (15 days to answer for payment services), then to the Arbitro Bancario Finanziario within 12 months. It costs €20; decisions are not legally binding, but non-compliance is made public.
- Report fraudulent payments to your bank at once and ask for a refund. A police report is not required to be reimbursed, but it helps fight fraud.
Netherlands
- Unresolved dispute: use your bank’s complaints procedure, then Kifid, within one year of complaining to the bank or three months of its rejection letter. Kifid’s decision is generally binding.
- Some crimes, including internet fraud, can be reported online with DigiD (forms in Dutch only); otherwise report at a police station.
- De Nederlandsche Bank: a business may not refuse your euro IBAN because it is from another EU country. Complain to the business first, then report it to DNB.
Poland
- Unresolved dispute: complain to the bank first; it must answer within 30 days (60 in complex cases). Then the Financial Ombudsman (Rzecznik Finansowy) can help; its amicable procedure is one banks must take part in, but it cannot issue binding decisions.
- Online scams and incidents can be reported to CERT Polska at incydent.cert.pl (English version available).
Spain
- Banco de España: if you did not authorise a direct debit, you have 13 months to claim a refund.
- Unresolved dispute: complain in writing to the bank’s customer service first. Without an answer within 15 working days for payment services (one month otherwise), you can go to the Banco de España.
- Cybersecurity help line: call 017 (INCIBE), free and confidential.
Switzerland
Switzerland is in the SEPA area but not in the EU: the rights in section 8 come from EU law (PSD2, the SEPA Regulation), which does not apply there as such. Check your bank’s terms.
- Unresolved dispute: complain in writing to the bank’s management or complaints office first, then to the Swiss Banking Ombudsman. It is free for clients and can recommend solutions but not impose them; contacting it does not stop legal deadlines.
- Paid a fake invoice with changed bank details? The Federal Office for Cybersecurity (BACS) says to contact your bank immediately, as it may be able to stop the payment, and to report a loss to the police (Suisse ePolice, in German, French and Italian).
11. FAQ
Is it safe to put my IBAN on an invoice or in an email?
Yes. That is its purpose. Avoid sending it bundled with an ID copy and a signature.
Can someone empty my account with my IBAN?
Not by transfer. They can attempt direct debits, which you can dispute and have refunded within the deadlines above.
Can a company refuse my IBAN because it is from another EU country?
No. A company that accepts transfers or collects by direct debit may not dictate in which EU Member State your account must be (Article 9 of Regulation (EU) 260/2012), provided your account can be reached through SEPA. This is often called “IBAN discrimination”.
The checksum is valid. Is the IBAN genuine?
It is well-formed. Whether it belongs to the right person is a different question, answered by Verification of Payee or a call-back.
Do I need the BIC as well?
Not for SEPA payments in euro. Outside SEPA, banks often still ask for it.
Should I change my account after a breach?
Rarely. Alerts, a creditor whitelist and regular statement checks do more for less effort.
Is an IBAN personal data?
When it can be linked to a person, yes: the GDPR covers any information relating to an identified or identifiable natural person (Article 4(1)).
12. Sources
- Regulation (EU) No 260/2012 (SEPA Regulation, consolidated text including the 2024/886 changes): Article 5(3)(d), Article 5c, Article 9
- Regulation (EU) 2024/886 (Instant Payments Regulation, Verification of Payee)
- Directive (EU) 2015/2366 (PSD2): Articles 61, 71, 73, 76, 77
- Regulation (EU) 2016/679 (GDPR): Articles 4, 33, 34
- European Payments Council: SEPA Direct Debit Core Rulebook (2025 v1.2, section 4.3.4), SEPA Direct Debit B2B Rulebook (2025 v1.2, sections 4.1 to 4.3), Verification of Payee Scheme Rulebook (2026 v1.1, section 3.2.1)
- ISO 13616 and the SWIFT IBAN Registry (structure, lengths, check digits)
- CSSF: customer complaints; Police Grand-Ducale: scams
- BaFin: credit transfers and direct debits; BKA: reporting a crime
- Banque de France: Observatory for the Security of Payment Means
- Austria: OeNB: recurring payments; FMA: complaints and points of contact
- Belgium: Ombudsfin: procedure; FPS Economy: consumer reporting point
- Ireland: FSPO; An Garda Síochána: fraud; Central Bank of Ireland: sending a payment
- Italy: Banca d’Italia: direct debit; Banca d’Italia: Arbitro Bancario Finanziario; Banca d’Italia: payment fraud
- Netherlands: Kifid: procedure; Politie: reporting a crime; DNB: SEPA and IBAN discrimination
- Poland: KNF: disputes with a financial institution; Financial Ombudsman; CERT Polska
- Spain: Banco de España: direct debits; Banco de España: how to file a complaint; INCIBE: 017 help line
- Switzerland: Swiss Banking Ombudsman: FAQ; BACS: business email compromise
Checked against these sources on 18 November 2026. This guide is general information for educational use. It is not legal or financial advice. Deadlines and procedures depend on your bank and country.