The Digital Euro Isn’t a Compliance Project. It’s a Market-Shaping Moment.
In collaboration with Lucia Italiano (LI Advisory Studio)
Two conversations, a few weeks apart, ended up in the same place.
One of us was at a payments industry working session where the talk kept circling back to the same anxious question: how are we supposed to be pilot-ready when half the rulebook isn’t finalised yet? The other was mid-way through a strategy-to-execution engagement where a client’s roadmap had five major programmes running in parallel, none of them sequenced against the other, and no one in the room whose job it was to notice.
Different rooms, different clients, same underlying problem. That’s usually the signal that something is worth writing about together.
The calendar is no longer abstract
For a long time, “the digital euro” was a phrase payments executives could file under later. That’s no longer true. The ECB is finalising technical standards this summer. Providers who apply to be part of the infrastructure have been notified in July 2026. A live pilot is scheduled for the second half of 2027. Design parameters are firming up too, a holding limit in the region of €3,000 per person has been floated, offline payment functionality is a stated requirement, and the settlement infrastructure candidates under evaluation include distributed-ledger options that most payment providers have never had to architect around.
Layer that on top of what’s already ongoing, such as the Instant Payments Regulation reshaping bank-to-bank economics, PSD3 and the PSR standardising open banking APIs through 2027, EPI’s Wero wallet already operating in Benelux, Germany and France, and you get a genuinely unusual moment: several structural shifts landing in the same 18-month window, each with its own deadline, and very few organisations with someone whose full-time job is to look at all of them together.
“I keep having the same conversation with CFOs and board members. They’re not short on awareness, most of them can recite the ECB timeline better than I can. What they’re short on is a way to translate that timeline into a governance decision they can actually act on this quarter, not a policy briefing to file away.”
Daniela
“From the delivery side, the pattern I see is almost the opposite failure mode. Teams that treat the digital euro as ‘yet another workstream’ and bolt it onto an already-overloaded roadmap, without asking whether it should be re-sequenced against the IPO timeline, the fundraising story, or whatever else is competing for the same engineering hours. Readiness isn’t a document. It’s a sequencing decision.”
Lucia
What this looks like in the room
To make this concrete, picture a composite example: a fast-growing European payments platform expanding into adjacent financial products, with a significant equity event on the horizon. Not a specific company but a fair illustration of the conversations we keep having with platforms carrying this kind of growth profile.
Its leadership walked into the session expecting a compliance briefing. What they got instead was a working session structured around four questions, not four slides:
- Where does our current licensing and governance posture actually sit against the emerging rulebook?
- What does our architecture need to look like to interoperate with the settlement infrastructure being considered?
- How does this change our competitive position as the broader market moves on the same timeline?
And the question that usually lands hardest:
- What does this bump down our roadmap, and have we actually decided that on purpose?
Two hours in, the conversation had moved from “how do we stay compliant” to “how do we make sure we’re one of the names in the room when the standards are finalised.” That shift from defensive posture to competitive positioning is the entire point of doing this work as a working session rather than a fat report handed across a table.
Why “wait for the final rulebook” is the wrong instinct
The natural executive instinct is to defer: wait until the legislation is finalised, wait until the rulebook stabilises, wait until a competitor moves first. We understand the instinct, no one wants to build against a (fast!) moving target. But three things make waiting the more expensive option here, not the safer one:
First, the milestones that matter most in the next twelve months (i.e. provider selection, infrastructure notifications, standards finalization) are procedural and near-term, not legislative and distant. Missing the window to investigate them isn’t a 2029 risk. It’s a 2026 risk.
Second, the frameworks converging right now aren’t independent of each other. A firm that treats IPR, PSD3, and digital euro readiness as four separate compliance tickets will build four overlapping – and expensive – pieces of infrastructure. A firm that reads them as one coherent architecture question builds once.
Third, and the one board members underweight most: being visibly, credibly prepared is itself a competitive signal to regulators deciding who gets a seat at the standards table, to investors assessing operational discipline ahead of a raise or a listing, and to a market where several well-capitalised players are moving on the same timeline.
What we’ve learned readiness actually requires
Across the engagements that led to this piece, the organisations handling this well share a pattern – not a department, a pattern:
- Regulatory fluency that reaches the board, not just the compliance function because decisions about licensing posture, custody, and governance need to be made at board level, informed by someone who can translate rulebook language into commercial consequence.
- Delivery discipline that treats this as a sequencing problem, not an additional line item: resourcing, milestones, and an honest answer to “what does this bump down the roadmap” rather than pretending it’s additive.
- Technical judgment applied early, not after a vendor has already been chosen, because architecture decisions made under deadline pressure are hard to unwind later.
Very few organisations carry all three natively, in the same room, pointed at the same 18-month window. That gap, more than any single regulatory clause, is what we think will separate the fintechs that shape this market from the ones responding to it.
What comes next
This is the first piece in a short series we’re writing together on digital euro readiness, not as an abstract policy topic, but as a practical governance and delivery question that payments leadership teams are facing right now, this year, on a real calendar. We’ll be going deeper on the sequencing question, the board conversation, and what a genuinely useful readiness assessment looks like versus a compliance checklist wearing an advisory hat.
If your leadership team has looked at this same calendar and isn’t yet sure who inside the building owns connecting the dots, that’s usually the first sign it’s worth a conversation. We’d like to hear from you.