Your IBAN Is Foreign. Is That a Reason to Reject It?
EU and EEA rules address account-location barriers for covered euro payments. Currency, reachability and legal scope matter more than a foreign-looking prefix.

The account number fits. The currency fits. The payment form still says no. Sometimes the obstacle is an IBAN whose first two letters identify a different country from the business taking the payment. A rejection like that can feel like a minor technical inconvenience. In the right legal circumstances, it is a specific kind of discrimination that European payment rules were designed to prevent.
The approved title asks a question rather than promising a universal answer. A foreign-looking IBAN is not automatically entitled to acceptance for every transaction worldwide. The payment type, currency, account location and reachability matter. So does the distinction between membership of the broader Single Euro Payments Area and the territorial scope of the law being invoked. Getting those limits right makes the protection more useful, not less.
What Article 9 actually says
The relevant rule is Article 9 of Regulation (EU) No 260/2012. For a credit transfer to an account within the Union, a payer must not specify the Member State in which the payee's account is located, provided the account is reachable under the regulation. The corresponding provision applies to a payee accepting a credit transfer or using direct debit: it must not specify the Member State where the payer's account is located, subject to reachability.
This is an enacted payment rule, not a new proposal. It tackles the assumption that a payment account must be domestic simply because the customer or business is domestic. Read alongside Article 1, it concerns euro-denominated credit transfers and direct debits within its stated scope. It does not establish an obligation to accept every card, every currency, or every payment method offered by any business.
A hypothetical example makes the distinction concrete. A business that already accepts an in-scope euro direct debit cannot justify demanding a particular Member State account merely by preferring a local prefix. But a business that does not offer direct debit at all presents a different question. Article 9 is about account-location restrictions within the covered payment arrangements, not a universal mandate to offer a payment method.
“SEPA” and “covered by this law” are not synonyms
SEPA is a scheme area for euro payments that reaches beyond the EU. The European Commission's SEPA overview describes that wider geography. Article 9, however, expressly refers to accounts located within the Union. EEA Joint Committee Decision 86/2013 incorporated the regulation into Annex XII of the EEA Agreement, with adaptations; EFTA records the decision as in force. That extends the legal framework through the EEA Agreement rather than merely through SEPA scheme membership. The covered euro payment and reachability requirements still matter.
That distinction is particularly important for a reader using an account in a non-EU country participating in SEPA. Scheme participation can tell you something about how the payment may travel. It does not, by itself, establish that every protection in EU legislation applies identically to that account. For an EEA case, the incorporated framework and relevant national enforcement arrangements need checking; do not infer the legal position solely from an IBAN country code.
This article explains the EU rule and its recorded EEA incorporation without making an unverified country-by-country conclusion for every wider SEPA account. The honest answer to “is my foreign IBAN covered?” therefore starts with location and the applicable legal framework, rather than ending with the fact that a provider advertises SEPA transfers.
Reachability is more than a correct-looking number
An IBAN identifies an account; it is not a blanket certificate that the account supports every payment arrangement. The regulation's reachability requirement matters. A valid account number can still be involved in a payment whose characteristics fall outside the situation being discussed. Currency, payment type and relevant provider locations should be established before treating a rejection as a confirmed Article 9 violation.
The same caution applies to the reason given for rejection. An explicit message demanding a domestic account is different from an explanation that the account details are incomplete, that a mandate has not been authorised or that a payment cannot be processed for another documented reason. Other eligibility or compliance questions are not automatically resolved by Article 9. A country-prefix rule is the central issue here, not proof that every refusal is unlawful.
These distinctions are OLECH analysis of how to read the rule, not a personalised legal determination. They help separate a potentially discriminatory account-location restriction from a problem that needs a different remedy. Without that separation, a genuine complaint can become buried in arguments about a payment method the business never offered.
A payment form can recreate a border
The most revealing version of the problem is sometimes mundane: a website field has been built around domestic account formats. The business may describe the limitation as technical. From the customer's perspective, the result is still a barrier based on account location. Technology choices do not change the wording of the legal rule, although the full facts still matter to an enforcement decision.
Imagine a hypothetical worker whose employer can make euro salary transfers but whose payroll form accepts only local prefixes. Compare that with a seller asking a customer to pay in a different currency through a method outside the regulation's scope. Both experiences can be frustrating; they are not necessarily the same legal issue. The first is the kind of account-location obstacle worth examining under the rule. The second requires a separate analysis.
This is why the story is bigger than one frustrating checkout. Standardised payment infrastructure is supposed to make compatible accounts usable across borders. A domestic-only form can restore the friction that common standards removed underneath. The relevant question is whether the form's restriction is compatible with the actual payment arrangement, not whether its designer intended to discriminate.
What the Commission says about complaints
The Commission's IBAN discrimination guidance describes the problem as being unable to make or receive a SEPA credit transfer, or pay by SEPA direct debit, from an account located in another Member State. It directs complaints to the national competent authority where the discrimination occurred. The page provides the current route for identifying those authorities.
A useful factual record includes the payment method being offered, the currency, the account location, the exact error message and any written response from the business. This is practical editorial guidance about documenting an incident, not a guarantee of a particular complaint outcome. Do not publish full bank details simply to demonstrate the problem; a country prefix and redacted evidence may establish the issue without exposing the account.
Asking the business for its precise reason can also clarify the scope. “We only accept local IBANs” and “this transaction uses a payment arrangement your account does not support” are different statements. The authority can assess the actual facts more effectively when the restriction is clear. A complaint is not the same as a ruling, and the article does not promise damages or immediate acceptance.
The border that matters is the legal one
A payment account can be foreign to a form yet entirely ordinary within a shared euro-payment system. Article 9 aims to prevent certain account-location demands from defeating that compatibility. Its strength lies in a specific rule for a specific payment context, not a sweeping instruction that every foreign account must work everywhere.
The practical conclusion is to identify the payment before judging the refusal. Establish its currency and method, the account's location and reachability, and the relevant EU or EEA legal basis. Then compare the stated rejection reason with the rule. A country prefix should not become an unexplained barrier where the law protects cross-border use, but SEPA geography alone is not the whole legal answer.
Sources - Regulation (EU) No 260/2012, consolidated text: Articles 1 and 9 - European Commission: IBAN discrimination and complaint authorities - European Commission: Single Euro Payments Area - EFTA: Regulation 260/2012 EEA incorporation status
- #IBAN
- #EU
- #SEPA

