On 14 July 2026, the ECB selected 36 payment service providers to pilot the digital euro. It picked them from more than 50 applicants. The pilot starts H2 2027. Most of the industry still can’t say precisely what that means for their roadmap. If you sit in a bank, a PSP, or a merchant finance function, that’s not a knowledge gap you can afford.
Here’s the honest state of play. The digital euro is further along than the “still just a concept” crowd assumes. It’s further from launch than the marketing suggests. And it’s more precisely regulated than most public debate about it credits. This is the version I’d give a client who needs to plan around it, not just form an opinion.
What the digital euro actually is
Strip away the “digital cash” shorthand and the underlying claim is simple. The digital euro would be central bank money, held in a digital wallet. Today’s euro balances sit in commercial bank accounts instead. That’s the whole distinction, and it’s the one that matters.
Central bank money vs. commercial bank money
A euro coin in your pocket is a direct claim on the Eurosystem. No bank failure can take it from you. Your current account balance works differently. Deposit guarantee schemes protect it up to €100,000, but legally it remains your bank’s liability, not the central bank’s. The digital euro would change that: it puts a central-bank-liability instrument directly in consumers’ hands, at retail scale, for the first time. Central bank reserves already exist, but only banks and a handful of institutions hold them, wholesale-only. Retail access would be genuinely new.
Two design choices explain almost everything else
Legal tender status drives the whole architecture. Once lawmakers adopt the Regulation, merchants must accept the digital euro at par. That’s the same protection cash already carries under Article 128(1) TFEU. No private-sector wallet has this lever, Wero included. Acceptance won’t be a commercial negotiation. It becomes a legal obligation for credit institutions that already offer retail payment accounts.
Lawmakers built it to avoid competing with savings. The digital euro will never earn or charge interest. Holdings will carry a per-person cap too. The ECB has floated a range around €3,000–4,000. One academic paper cited in the ECB’s own working paper argues €1,500–2,500 would maximize welfare instead. The Governing Council still owns that decision, and must finalize it before first issuance. For comparison, the Bank of England’s parallel digital pound work has floated a much higher ceiling, around £20,000. That gap is a useful reminder: central banks are weighing this trade-off very differently.
How it actually works
Three mechanics matter more than the rest, because payment professionals actually have to build against them.
The waterfall and reverse-waterfall mechanism
This is the least publicized, most important design feature. Say you initiate a payment larger than your digital euro balance. Your PSP automatically pulls the shortfall from a linked bank account (reverse waterfall). Say an incoming payment would push you over your holding limit instead. Your PSP automatically sweeps the excess to your linked bank account rather than declining it (waterfall). Both require user authorization. Both must settle within seconds.
Here’s the detail architecture teams need. A linked digital euro account at a different PSP always triggers waterfall functionality. Reverse waterfall only works when the two PSPs sign a bilateral arrangement covering funding conditions and data protection responsibilities. That’s a new interoperability dependency between PSPs, and it doesn’t exist today. Someone at your institution needs to own that relationship.
Mandatory distribution, not commercial adoption
Credit institutions that already offer retail payment accounts must distribute the digital euro. They must provide basic services free of charge too. This isn’t opt-in the way Wero adoption was for EPI’s shareholder banks. Member States must also designate public entities (such as post offices, local authorities) to reach people without a bank account, or who don’t want one. A specific AML carve-out covers asylum seekers and people with no fixed address who can’t produce standard ID. Basic services also guarantee a physical, non-app payment instrument on request. This won’t be an app-only product.
Offline privacy, by architecture rather than promise
For offline payments specifically, the device stores and processes transaction data locally. Neither the PSP nor the Eurosystem can see it. That’s comparable to what an ATM cash withdrawal records today. The protection applies to the offline channel only. Online digital euro payments still flow through standard AML/CFT checks, the same as any euro moving through a bank now. Neither Wero nor card schemes offer an equivalent offline-privacy mode.
The distinction almost everyone gets wrong
“Programmable money” versus “conditional payments” is the single most misunderstood point in every public conversation about the digital euro, including among people who follow the space closely. It deserves its own section.
Programmable money: banned outright
Article 2(18) of the draft Regulation defines “programmable money” precisely. It means units of money carrying an intrinsic logic that restricts their fungibility. Picture a euro that can only buy certain goods, or one that expires, and stays restricted no matter whose hands it reaches. Article 24(2) bans this outright, full stop.
Conditional payments: explicitly permitted
Article 24(1) covers something different: automated payment instructions that trigger when both parties pre-agree on conditions. Think of a standing order or an escrow release. The restriction lives in the instruction, not in the money itself. Once a conditional payment executes, ordinary, fully fungible digital euro moves, indistinguishable from any other euro before or after.
Why the line matters in practice
PSPs can still restrict a payment instrument itself. Picture an account or card configured to authorize spending only at certain merchant category codes. That’s not new, and lawmakers haven’t banned it. Meal vouchers and corporate benefit cards already work this way on ordinary commercial bank rails today. Article 24(2) actually prohibits something narrower, and arguably more consequential: money that stays shackled no matter who receives it. That would break the fungibility that makes a currency a currency. When you advise a client on digital euro use cases, know this line precisely. “Is this programmable money?” and “is this a restricted payment instrument?” are two different regulatory questions, with two different answers.
One more point worth tracking. Every ECB press release I’ve checked uses only “conditional payments.” The word “programmable” circulates widely in trade press, but it traces back to at least one private vendor’s own marketing language, not the ECB’s terminology. Keep the regulatory text separate from how the ecosystem around it talks about itself.
Merchant and PSP economics: regulated, not free
Consumer-facing messaging tends to collapse this to “free.” That’s only true for consumers using basic services. On the commerce side, merchant service charges and inter-PSP fees still apply. A proportionality test caps them at the PSP’s cost-plus-margin, or the fee for comparable digital payment means, whichever is lower. EU-wide uniform caps will follow too. The Commission will set those with ECB technical input, using a prescribed methodology: a volume-weighted average of fees for comparable digital means of payment over the preceding 12 months.
The actual number isn’t public yet. Nobody can model the real margin impact with precision until the Commission publishes its first implementing act. That includes the PSPs already building for the 2027 pilot.
Where it actually sits versus Wero and cards
This is the strategic question, and it deserves a direct answer rather than a hedge.
Digital euro, Wero, and card schemes aren’t three versions of the same thing. They’re three different trust and settlement models, all competing for the same checkout screen. One carries central bank liability with a legal mandate behind it. One runs on commercial bank money, built through voluntary bank consortium adoption. One is a third, already-regulated interchange model. Wero itself has run live for P2P transfers and e-commerce in France, Germany and Belgium since January 2026. In-store POS coverage is still landing through late 2026, and the Netherlands and Luxembourg remain in deployment. That’s real traction, though narrower than its 2024 launch narrative implied.
My read on where this goes
This is a genuinely open question, not a settled one. I don’t think digital euro displaces Wero in the near term. I think it becomes a settlement layer underneath existing wallets instead, the way SEPA Instant already sits invisibly behind a dozen consumer-facing apps today. Lawmakers built the waterfall mechanism for accounts to talk to each other, not for a walled garden and it explicitly requires PSP-to-PSP interoperability arrangements. That outcome only holds if commercial banks treat the mandatory interlinking obligation as infrastructure worth owning, not a compliance line item to minimize. Many of those same banks are also EPI shareholders behind Wero. Right now, most of them are choosing the compliance-minimizing path.
The actual bottlenecks
Four things stand between today and a real launch, and none of them are resolved yet.
- The Regulation itself isn’t adopted. It’s still moving through ordinary legislative procedure; Parliament and Council both have to agree. The scheme rulebook sits at draft v0.91, explicitly marked as not usable for implementation.
- The holding limit is unset. Every deposit-flight model a bank builds today works from a range, not a number. The Governing Council must decide the actual figure before first issuance, not after.
- The fee caps aren’t published. No PSP can finalize the business case for digital euro acceptance infrastructure until the Commission’s implementing act sets real numbers.
- The pilot skips the hardest use case. The four confirmed pilot use cases cover P2P online, P2P offline, and two P2B/merchant scenarios. None of them test the unbanked-onboarding channel, the public-entity distribution model, or the simplified AML pathway. Those are real legal commitments in the draft text, but currently unproven mechanisms.
What this means if you’re planning around it
If you’re a bank
The distribution obligation is coming, whether or not you’ve priced it as strategic. Treat the waterfall interlinking relationship as an asset rather than a checkbox. Do that, and you end up owning the connective tissue between digital euro and whatever wallet your customers actually open every day.
If you’re a PSP or acquirer
The fee cap methodology benchmarks against comparable digital payment means. Digital euro acceptance costs will very likely undercut card economics once the Commission publishes the number. Model that now, even with a range instead of a figure. Don’t wait for the implementing act to force your hand.
If you’re a merchant
Legal tender status means acceptance won’t stay optional once digital euro goes live. But “once it’s live” still means an H2 2027 pilot followed by an undated issuance decision. You have time to plan. Just not a reason to wait until the last minute.
None of this is settled, and nobody writing about it, including us, should treat it as settled. But it’s precise enough now to plan against, more than most current commentary gives you credit for.
Working on your institution’s digital euro or Wero interlinking strategy? → Book a scoping call with ITOPYX
ITOPYX