For PSPs
Digital euro timeline for banks — 2026, 2027, 2028
Launch is targeted around 2029, which sounds like plenty of time. It isn't. A year-by-year plan for credit institutions.
On this page
"Launch is targeted around 2029" is the sentence that has let every bank in the euro area defer this for another quarter. Three years is a long time. There is no emergency.
That reading is wrong, and it is wrong for a specific reason: the work with the longest lead time is not the build. It is the decision. And the window in which you can make that decision calmly is considerably shorter than three years.
Here is the year-by-year version.
The fixed points
July 2026
Rulebook v0.91 published
A draft. Explicitly not for implementation reliance.14 July 2026
36 PSPs selected for the pilot
From 57 applications, across 19 countries including Croatia.Q3 2026
Development starts
Pilot build work begins.H2 2027
Live pilot, ~12 months
Beta digital euro. Users are ECB and national central bank staff — not the public.~2029
Targeted launch
Dependent on the regulation completing the EU legislative process.
And the two facts that make those dates matter to you:
- Credit institutions will be obliged to offer basic digital euro services on request once the digital euro launches.
- Basic services are free for individuals.
Mandatory, unpaid, on a date you do not control.
2026 — decide, do not build
This is the year to make decisions, and the year not to write code.
Why not build? Rulebook v0.91 is explicitly a draft. Sections are unfinished — including the functioning and enforcement of the holding limit, which is the most consequential parameter in the whole design. Offline specifications are expected in future versions. Code written against v0.91 is code you will write twice, and you will pay for both.
What to do instead:
Confirm the obligation applies to you. Credit institution or not. Payment institutions and EMIs may distribute the digital euro without being compelled to — which means a genuine business case with a genuine option to decline. Credit institutions do not have that option. This single answer changes everything downstream.
Decide your role. Distributing PSP (serving individual users) or acquiring PSP (serving business users), or both. They are different builds. Scoping both when you need one is a classic and expensive error.
Make the build-vs-buy call. Not the build — the call. PSPs may outsource development and operations to a TSP, while retaining regulatory responsibility, which never transfers. Procurement, due diligence and contracting run in quarters. Start now and you are choosing in a calm market.
Read the specs. The pilot's technical documentation is public, including back-end API specifications in YAML. You do not need to be one of the 36 to read the contract you will implement.
The trap of looking busy
A proof-of-concept against a draft feels like progress and produces nothing durable. It burns the budget you will need in 2028 and generates code with a known expiry date. Resist it.
2027 — learn from the pilot
The live pilot starts in H2 2027 and runs roughly 12 months, with a beta digital euro and ECB and national central bank staff as users. Not the public. Not your customers.
If you are one of the 36: your build meets reality. You are not implementing a finished specification — you are helping find out where it is wrong. That is valuable and it is a different job from what your delivery plan says. Budget for discovery, not delivery.
If you are not: this is the cheapest learning available, and you get it for free.
- Watch what the pilot surfaces. Where a specification meets an implementation, the gaps become public.
- Track the RDG progress reports. They show what is being worked on before it lands in a published draft.
- Finalise your build-vs-buy decision if 2026 got away from you. This is the last comfortable moment.
The specific things to watch for, because they are where estimates die:
- The holding limit mechanics, currently unspecified.
- Offline — the wallet SDK, distribution service, and DESP offline issuance integration.
- The liquidity edge cases, especially the post-settlement waterfall step that exists because a single pre-settlement check cannot catch two incoming payments racing each other.
2028 — build, against something stable
By now the rulebook should have moved beyond draft and the pilot should have exposed what the specification got wrong. This is when serious implementation is defensible rather than premature.
If you are building: this is the year. Access management, aliases, switching (including emergency switching using the technical proof), funding and defunding at 24/7/365 availability including the cross-PSP case, the waterfall mechanics, combined transactions, your front end.
Then certification, testing and onboarding — a phase with its own duration. Every scheme in payments works this way, and every team that treats certification as a rubber stamp learns otherwise at the worst possible moment. Put it on the plan with real weeks against it.
If you are buying: this is when your provider does the above and you do the work that is irreducibly yours — supervision, audit, evidence. Remember that regulatory responsibility never transferred. Being able to say "our vendor handles it" is not an answer to a regulator.
The capacity crunch is here
This is the year every credit institution in the euro area needs an integration simultaneously, drawing on the same small pool of people who have done this work before. Whether you build or buy, you are competing for that capacity. Institutions that decided in 2026 contracted in a normal market. Institutions deciding in 2028 are in a scramble.
2029 — launch, if the legislation lands
The obligation arrives with the launch, not after a grace period you can plan around.
And the honest caveat, which cuts both ways: ~2029 is a target, dependent on legislation. The regulation is still in the EU legislative process, and the decision on whether to issue the digital euro will only be considered once that process completes.
So yes — it could slip. Planning on that is a bet that a supranational legislature will be slower than announced, in exchange for being unprepared if it is not. That is a poor trade for a regulated institution.
The one-page version
| Year | Do | Don't |
|---|---|---|
| 2026 | Confirm the obligation, pick your role, make the build-vs-buy call, read the public specs | Write code against a draft |
| 2027 | Learn from the pilot and the RDG reports; finalise the decision if you haven't | Mistake the pilot for a public launch |
| 2028 | Build against a stabilised rulebook; plan certification as a real phase | Discover certification exists in month eleven |
| 2029 | Be live when the obligation lands | Assume a grace period |
The point
The deadline is not the problem. The queue is.
Three years is genuinely enough time to do this well — once. It is not enough time to do it twice, which is what building against a draft buys you. And it is not enough time to start procurement in 2028, when every institution that deferred is calling the same providers in the same quarter.
The institutions that handle the digital euro well will not be the ones that started earliest. They will be the ones that decided earliest and built once.
Nothing on that list requires the rulebook to be final. All of it requires you to start.
Sources
Related reading
Digital euro — should your bank build or buy?
The digital euro is mandatory for credit institutions and free for individuals. That makes build vs buy a cost problem, not a product decision.
36 PSPs selected for the digital euro pilot — what it means
On 14 July 2026 the ECB selected 36 PSPs from 57 applications across 19 countries for the digital euro pilot. What it signals — and what it doesn't.