The short answer
IBAN discrimination concerns restrictions linked to an account being in another Member State in the relevant SEPA context. A rejection due to unsupported activity, sanctions, missing information or other grounds is not automatically the same issue. Preserve the stated reason before selecting a complaint route. [European Commission]
Source-linked facts below are distinct from our suggested workflows. Examples are hypothetical; this is not individual legal, tax or investment advice.
- 01Refusal
- 02Payment context
- 03Evidence
- 04Escalation
Record the refusal precisely
Save the message, form error or payment rejection rather than paraphrasing it as the bank refusing crypto. Record the parties, account locations, payment type and the exact field rejected. Do not put the full account number in a public complaint screenshot; retain it securely for the appropriate authority or provider.
A domestic-only country dropdown can point to a different issue from a request for source-of-funds documents. Record these separately. The European Commission describes the relevant SEPA account-location problem and refers complaints to the national competent authority in the country where the discrimination occurred. [European Commission]
Check the payment context
Establish whether the transaction is a euro credit transfer or direct debit within the relevant framework. SEPA is a payment-scheme area and should not be casually treated as identical to EU membership. Also establish whether the account and parties are reachable for the payment type. [EPC]
A wallet address is not an IBAN. A conversion service that has not yet submitted a euro transfer has not necessarily reached the payment leg where the IBAN question arises. Map the sequence to avoid raising a complaint about account location when the unresolved issue is at the crypto deposit or trade stage.
Separate location from activity restrictions
Ask for clarification of the reason through the appropriate channel. Does the recipient insist on a domestic IBAN, or does the institution reject a category of counterparties or activities? Do not assert that an account-location rule authorises every transaction or defeats other lawful obligations.
A useful fact table records the explicit reason, the evidence for that reason and what is not known. The same transaction may have more than one problem. Correcting the location restriction may not resolve missing information, beneficiary mismatch or an unsupported source of funds.
Build an evidence-led escalation
Use the relevant provider or recipient complaint process and the national route indicated by the Commission where appropriate. Include the payment context, a concise chronology and redacted evidence. Explain the remedy requested, such as acceptance of a reachable account without an unjustified country restriction. [European Commission]
Keep a copy of the submitted complaint and acknowledgement. Do not assume the same ombudsman or consumer protection route is available to every company. Eligibility, deadlines and remedies depend on the applicable jurisdiction and the parties involved; seek advice where legal rights are disputed.
Keep operations running without obscuring the facts
While the complaint is being considered, ask the counterparties what lawful alternative payment methods they support. Changing a route for continuity should not require hiding the legal originator or using an unrelated person’s account. Preserve the relationship between the original obligation and any replacement payment.
If a payment is resent, confirm the original status first to avoid paying twice. Record the new reference, fees and any reversal. An operations log can support both reconciliation and a later complaint, while preventing the legal argument from becoming a second source of payment errors.
Turn the incident into a reusable check
Update the receiving-instructions checklist with the failure observed. A country dropdown failure, unsupported payment scheme and beneficiary-name mismatch should be categorised differently so that the next case reaches the right owner.
The site’s route diagrams are intended to help make these distinctions visible. They do not resolve legal scope or determine that discrimination occurred. A confident conclusion requires evidence of the actual refusal and the applicable rule, not merely a foreign IBAN on an unsuccessful transfer.
Working checklist
Ticks record your work, not an approval or compliance score. Progress stays in this browser where storage is available.
Method, assumptions and limits
Regulatory facts are linked to primary sources. Suggested workflows are our editorial synthesis; examples and fee scenarios are hypothetical. The mechanical illustration is a conceptual navigation aid, not a prescribed legal funds flow.
This is a dated research edition, not an automatically updated register or live price feed. Check the applicable entity, service, jurisdiction and source version before using the material.
Read the methodologyQAnswers
Questions before you set out.
01Does a foreign IBAN prove discrimination?
No. You also need the payment context and evidence of the refusal or restriction.
02Does SEPA require every crypto payment to be accepted?
No. SEPA account-location rules should not be read as overriding all other legal or contractual controls.
03Where is a complaint filed?
The Commission points to the relevant national competent authority; the correct route depends on where the issue occurred.
04Should funds be resent immediately?
Establish the original payment’s status before issuing a replacement to avoid duplicate payment.
Sources & scope
Research snapshot: 12 November 2026. The dated rule, its scope and the legal entity matter. Open the primary source before acting.
- European Commission: IBAN discrimination and national complaintsOfficial guidance
- EPC: SEPA Credit Transfer schemeScheme operator documentation
- EBA: Guidelines challenging unwarranted de-riskingRegulator guidance
- EUR-Lex: Regulation (EU) 2023/1113 — information accompanying transfersEU legislation