
Monaco IBAN Rejected? What to Do
Why EU merchants, SaaS tools and platforms reject MC IBANs, what the SEPA rules cover, and how Monaco businesses can avoid payment disruption.
Most Monaco business owners have seen it at least once. You set up a direct debit for an EU software subscription, register as a seller on a marketplace, or add a supplier's payment details, and the form says your IBAN is "invalid" or "not supported". The account works fine. The problem is the two letters at the start: MC.
Here is what most people miss. The EU rule against "IBAN discrimination" probably doesn't protect you. The fix is usually operational, not legal, and a good part of it sits inside your own website and billing systems.
Why MC IBANs get rejected
Monaco is part of the SEPA scheme. Monegasque banks can send and receive euro credit transfers and direct debits using the same formats as banks in Paris or Milan. From a technical point of view, a Monaco account is a normal SEPA account.
Rejections usually come from one of four places:
- Outdated validators. Many checkout forms and onboarding flows check IBANs against a hard-coded list of countries. If "MC" isn't on the list, the IBAN fails before anyone looks at it.
- "EU only" product settings. Some SaaS companies, payroll tools and marketplaces enable SEPA Direct Debit only for EU or EEA countries. That is a business choice, not a technical limit.
- Missing address data. When a SEPA payment involves a country outside the EEA, the rulebooks require more information about the payer, including an address. Providers that don't collect it often block those countries altogether.
- Risk scoring. In June 2025 the European Commission added Monaco to the EU list of high-risk third countries, in line with the FATF grey listing. EU-regulated firms must apply enhanced due diligence to relationships involving Monaco, and some simply opt out. We covered this in our article on the FATF grey-list exit.
What the SEPA Regulation actually protects
The EU SEPA Regulation (No 260/2012) bans IBAN discrimination in Article 9. A payer or payee may not dictate which Member State a payment account must be located in. In practice, if a German company accepts SEPA Direct Debit, it must accept an Italian or Spanish IBAN too.
The key word is located in the Union. The protection is written for payment accounts in the EU, and it extends to the EEA. Monaco is not an EU member state and is not in the EEA. Taking part in the SEPA scheme is a separate arrangement from being covered by the EU Regulation. So the usual reading is that a merchant who refuses an MC IBAN is not breaching Article 9, even though a French IBAN would be protected.
We are not lawyers, and national regulators can interpret the rules in their own way. If a rejection is costing you real money, check with your bank or a payments lawyer before assuming you have, or don't have, a legal remedy. But plan as if you have no legal right to insist.
If you are paying: reduce your exposure
For a Monaco company, the practical risk is a subscription, a platform payout or a supplier relationship you can't set up, or one that stops working at renewal. A few habits help:
- Test before you commit. Before signing a contract with an EU SaaS tool, marketplace or logistics partner, ask a direct question: "Do you accept SEPA Direct Debit from an MC IBAN, and do you pay out to one?" Get the answer in writing.
- Keep a card fallback. Many providers that reject MC IBANs will accept a company card issued by a Monegasque bank. For subscriptions, a card is often the easier route.
- Map your critical payments. List the providers that would disrupt operations if a direct debit failed, such as hosting, payment processing, advertising accounts and accounting software, and note how each one is paid.
- Consider a secondary account carefully. Some Monaco businesses hold an EU account for specific flows. That adds cost, compliance work and possibly tax questions, so discuss it with your bank and accountant first. Don't treat it as a quick workaround.
If you are getting paid: don't repeat the mistake
The same problem shows up in reverse. Monaco businesses that collect payments online, whether for rent, memberships, services or e-commerce orders, often use form plugins or billing tools that were never tested with Monegasque accounts. Some reject MC IBANs from their own customers.
A Monaco IBAN is 27 characters, the same length as a French one, and it starts with MC followed by two check digits. Check your own flows:
- Payment and mandate forms on your website: do they accept MC, FR, IT, DE and Swiss (CH) IBANs?
- Billing and CRM tools: are Monaco addresses and IBANs stored in structured fields, or forced into a French format?
- Error messages: if an IBAN is refused, does the customer see a clear alternative such as card or bank transfer, or just a red "invalid" label?
Our web development team often finds problems like this during form audits. The same validation code can also break Monaco phone numbers and postcodes. If you run an online shop, our e-commerce services include checkout testing with Monegasque payment details.
What to watch in the coming months
Two things could reduce the friction, but neither will remove it automatically.
First, if the FATF removes Monaco from its grey list, the EU is expected to update its own high-risk list afterwards, usually with a delay of several months. That should ease the risk-based rejections, though not the ones caused by outdated validators or EU-only product settings.
Second, from 22 November 2026 the SEPA rulebooks move to structured address data. Providers that upgrade properly will be better able to handle non-EEA SEPA countries. Those that don't may reject more payments for a while. Our guide to the SEPA structured address change explains what to clean up.
In the meantime, the most useful step is a short internal review of which providers you depend on, how each one gets paid, and whether your own website accepts the payment details your Monaco customers actually use. If you want to plan this as part of a wider digital strategy review, that works well too.
Talk to us
If your checkout, billing forms or customer portal need testing with Monegasque payment and contact data, or you want a second opinion on your payment setup before Q4, get in touch. We will help you find the weak points before your customers do.