EU Digital ID Wallet and Monaco

Four Months From Now, 450 Million People Get a New Way to Prove Who They Are

On 24 December 2026, every European Union member state must be able to issue at least one certified digital identity wallet to its citizens and residents. Not a pilot. Not a recommendation. A legal obligation under Regulation (EU) 2024/1183 — the framework usually called eIDAS 2.

Monaco is not an EU member state, and this regulation does not apply in the Principality. But a very large share of the people who buy from Monaco businesses, book Monaco hotels, view Monaco property and subscribe to Monaco services are EU residents. From the end of this year, a growing number of them will carry a government-issued identity wallet on their phone and will expect it to be useful.

This is a forward-looking piece. The wallet will not be everywhere on day one, and adoption will be uneven. But the design decisions that determine whether your website can accept a wallet credential in 2028 are the ones being made in your next redesign, not in some future compliance project.

What the Wallet Actually Is

Think of it as a government-backed container on a phone that holds verified attributes and releases them one at a time.

The wallet can hold a national identity document, a driving licence, professional qualifications, company representation rights, and — this is the part with the most immediate commercial consequence — a simple attestation of age.

The mechanism that matters is selective disclosure. A customer proving they are over eighteen does not hand you a scan of their passport. The wallet returns a single verified assertion: yes, over eighteen. You receive the answer without receiving the document, the birth date, the name or the identifier behind it.

For any business that currently handles identity documents by email, upload form or photocopy, that is a meaningful change in both risk and friction.

Who Has to Accept It, and When

Two dates, and they are commonly confused.

24 December 2026 is the provision deadline. Member states must make a compliant wallet available. Public authorities must accept it where identification is required.

December 2027 is the acceptance deadline for parts of the private sector. The obligation falls on relying parties that are already required to apply strong customer authentication — banks, credit institutions, e-money institutions, payment service providers — along with regulated sectors such as transport, energy, health, telecoms and education, and Very Large Online Platforms under the Digital Services Act. Micro and small enterprises are exempt from the acceptance requirement.

Neither obligation reaches a business established in Monaco by force of the regulation itself. If your company has an EU subsidiary, branch or regulated activity inside the Union, the analysis is different and genuinely fact-specific — that is a question for counsel with your structure in front of them, not for an article.

Why It Still Lands on Monaco Businesses

The obligation is not the mechanism. Customer expectation is.

Once a European customer can open an account at their bank by tapping a wallet, a Monaco business that asks the same customer to scan a passport and email it looks a decade behind. The comparison is not against your Monaco competitors. It is against every other checkout and onboarding flow that person uses.

Age verification is where this arrives first and hardest. Pressure to gate age-restricted goods and content is rising across Europe, and the wallet is being positioned as the harmonised way to do it without collecting identity documents. Monaco merchants selling wine, spirits or anything else age-restricted into EU markets already sit in an awkward middle ground, and a tick-box confirming date of birth has never been a serious control. A wallet-based check is a better answer, and it collects less data — which sits well with the data-minimisation duties in Monaco's own Law No. 1.565 of 3 December 2024, supervised by the APDP.

There is also a B2B case that gets overlooked. The wallet can carry proof that a person is authorised to act for a company. For anyone selling professional services or B2B products across borders, that removes a slow, manual verification step.

Monaco Has Its Own Identity Track

The Principality is not standing still. MConnect gives residents and businesses a national digital identity for government services, and the wider Extended Monaco programme has treated sovereign digital identity as core infrastructure rather than a side project.

MConnect and the EU wallet are separate schemes and are not interoperable today. Whether some future recognition arrangement emerges between the two is genuinely unknown, and we would not speculate. The practical planning assumption is that a Monaco business serving both local and EU customers will, over time, need to handle more than one identity scheme — which is an argument for building identity verification as a swappable component rather than hard-wiring one provider into your checkout.

What to Actually Do Between Now and December 2027

Nothing here requires a compliance budget. It requires a few decisions to be taken deliberately rather than by default.

Find out where you handle identity today. Onboarding, age gates, account recovery, high-value order verification, KYC for regulated activity. Most businesses have more of these than they think, and several are usually improvised.

Stop storing what you do not need. If you keep passport scans because someone once asked for them, that is a liability under Law No. 1.565, not an asset. A properly scoped data protection review will normally find several of these.

Treat identity as an integration point. When you next commission e-commerce work or a platform rebuild, ask how a new verification method would be added later. If the honest answer is "we would rebuild checkout", that is the finding.

Ask your payment provider directly. Providers regulated in the EU are inside the December 2027 obligation and are already planning for it. Payment arrangements can work differently for Monaco merchants than for French ones, so ask specifically about your own contract rather than assuming the general roadmap applies to you.

Design the flow before the technology. A verification step that is technically correct and confusing on a phone will cost you more orders than it protects. This is UX work as much as engineering.

None of this is urgent this month. All of it is cheaper to decide now than to retrofit in 2028.

If you want a clear view of where identity sits in your customer journey — and what it would take to accept a wallet credential when your customers start asking — get in touch. We will tell you honestly whether it is a real project or a line item you can safely leave until next year.