Short answer
The digital euro's developer opportunities sit with licensed payment service providers and the technical service providers that build for them: wallet and app integration, acceptance at checkouts and terminals, back-end connection, fraud, offline payments and reconciliation. Independent developers cannot connect directly. Today's realistic steps are learning the published standards, working through a PSP or applying to ECB innovation activities.
Why developers are asking now
Three things changed in 2026. The ECB published pilot specifications for payment service providers (PSPs) in April, selected 36 PSPs for a pilot planned from the second half of 2027, and signed agreements with three European standard setters. On 3 June 2026, ECB Executive Board member Piero Cipollone told the European Parliament that early clarity on standards lets private operators start building now (ECB speech).
None of this means the digital euro exists. It has not been issued, the regulation is still in trilogue negotiation, and the ECB will decide on issuance only after the law is adopted. Our timeline sets out the conditional dates, and our overview explains what the digital euro is.
For payment developers, the practical question is no longer whether the digital euro is technically possible but where the integration work will fall and when. Digital euro for developers, in other words, is mostly a question of roles. This page is about people and organisations: who builds what, what skills that takes and which route fits you. What the technical documents actually contain, including the API structure and error model, is covered on our page on the digital euro API. DIGITAL EUR is independent and has no affiliation with the ECB or the Eurosystem.
Who can build what?
The digital euro is distributed through supervised intermediaries, so your role decides your access. The table summarises roles named in ECB documents.
| Role | Examples from ECB documents | Access to Eurosystem interfaces | Status on 5 November 2026 |
|---|---|---|---|
| Distributing PSP (serves consumers) | Banks, payment and e-money institutions | Yes, through contracts and a network service provider | 36 PSPs selected for the pilot |
| Acquiring PSP (serves businesses) | Acquirers, payment institutions | Yes, as above | Part of the same 36 |
| Technical service provider (TSP) | Payment processors, IT service providers, software vendors, system integrators, consultancies | Through the PSP it works for | ECB held two TSP workshops in March 2026 |
| Eurosystem component provider | Alias lookup, risk and fraud, app and SDK, offline solution, secure payment information | Builds components for the Eurosystem | Framework agreements since October 2025; no payment at this stage |
| Network service provider | Two groupings selected on 30 October 2026 | Provides connectivity | First contract effective 28 September 2026 for pilot connectivity |
| Standard setter | European Card Payment Cooperation (CPACE), nexo standards, Berlin Group | Defines reused standards | Agreements announced 24 April 2026 |
| Merchant development team | E-commerce and m-commerce merchants | Through an acquiring PSP | Main pilot merchant call closed 27 October 2026 |
| Innovation platform participant | Registered organisations in the EU | Simulated PSP in a test environment | 2026 call closes 9 November 2026, 17:00 CET |
| Independent developer or unlicensed start-up | Freelancers, tool vendors | None directly | Can work through the routes above |
Sources: ECB pilot FAQ, TSP workshop summary, component providers, network service providers, standards agreements and the innovation call.
The ECB's TSP workshops show where the market sees work. Participants included Nexi, Worldline, SAP Fioneer, Finanz Informatik, Giesecke+Devrient, Redsys, Payone, Senacor and Sopra Steria, among others. They described roles in integrating with PSP systems, connecting to the digital euro service platform, and providing wallet and front-end solutions and merchant acceptance infrastructure.
What is confirmed, proposed and unknown for developers?
| Topic | Status | What it means for your planning |
|---|---|---|
| Pilot specifications (front end 14 April 2026, back end 23 April 2026) | Published, indicative | Enough to study architecture and data models |
| Draft scheme rulebook v0.91 (2 July 2026) | Draft | Requirements may still change |
| Reused standards: CPACE, nexo, Berlin Group | Agreed with the ECB | Skills in these standards are a reasonable bet |
| Eurosystem app and SDK for PSP apps | Procured; development to be decided later | PSP app teams will integrate a library, not build everything |
| Stability of DESP interfaces after the pilot | Intended, per the ECB pilot FAQ | Pilot work is not expected to be thrown away |
| Public sandbox or simulator | Not available; requested by TSPs | No self-service testing yet; technical sandbox research happens only inside ECB programmes |
| Integrations roadmap for merchants and PSPs | Pilot from H2 2027; no production date | Any digital euro integrations roadmap must be conditional on legislation |
| Final regulation, holding limits, fees | Under negotiation | Business cases remain uncertain |
| Issuance | Not decided | Production work has no fixed go-live |
Where are the developer opportunities, layer by layer?
The opportunities follow the architecture. Each layer below is one where ECB documents describe work that someone other than the Eurosystem has to do.
App and wallet front end
Consumers would use the digital euro through their PSP's banking app or through the Eurosystem's own app. The ECB's contract notice says the SDK is embedded in a PSP's mobile banking app as a software library and provides a client to the platform's standard APIs (ECB contract notice). Work here is integration: embedding the SDK, meeting the minimum user experience requirements in rulebook Annex B1, onboarding, alias registration and accessibility.
Acceptance: terminals, checkouts and in-app payments
In shops, payments would use NFC contactless under the CPACE standard or QR codes. Online, the customer would be passed to their app by QR code, link or alias. In the pilot, acquiring PSPs may be asked to offer SoftPOS (a software terminal on an ordinary device) and e-commerce or m-commerce solutions, and merchants must offer the beta digital euro through a dedicated or adapted checkout. Developers at acquirers, gateways and point-of-sale vendors would build these.
Back-end connection
PSP engineers would connect core systems to the Digital Euro Service Platform (DESP): user and account number management, alias lookup, settlement of payments and refunds, and the "waterfall" and "reverse waterfall" that move money between a digital euro holding and a linked bank account. The ECB's pilot FAQ notes that PSPs must develop pilot payment services independently, using documentation on connectivity, front-end requirements, common services and back-end infrastructure.
Risk, fraud and disputes
The Eurosystem procured a risk and fraud management component, and the draft rulebook has back-end chapters on risk and fraud and on dispute management. PSPs still own customer due diligence, monitoring and complaint handling, which creates work for compliance engineering teams.
Offline payments
Offline digital euro payments would settle device to device. The offline component was awarded to Giesecke+Devrient as first-ranked provider. TSPs at the ECB's workshop asked for further guidance on terminal integration and operational parameters, which suggests this layer is still being specified.
Data, reporting and reconciliation
Merchants hold no online digital euro balance under the ECB's design, so incoming funds are moved to their bank account. Every refund draws from that account. ERP, accounting and reconciliation developers will need to handle new identifiers and settlement patterns. Our guide for businesses shows a worked example of what a merchant's bank statement might look like.
Value-added services
The ECB's innovation platform explores electronic receipts, split payments, conditional payments, app features, AI and public uses. These are research themes, not commitments, and the ECB rules out programmable money. Our innovation platform page covers the 2026 call, eligibility and the 9 November 2026 deadline.
Which skills and standards should a developer learn?
| Area | What to study | Why it matters | Public starting point |
|---|---|---|---|
| ISO 20022 | Data dictionary, payment status and reason codes | The pilot API uses ISO 20022 data types and status codes where available | Pilot back-end specification, data dictionary chapter |
| REST API design | JSON, problem+JSON errors, asynchronous responses, idempotency with a Request-Id | This is how the DESP and PSPs exchange requests | Pilot back-end specification, sections 1–2 |
| Contactless | CPACE and NFC | Basis for tap-to-pay with the digital euro | ECB press release of 24 April 2026 |
| Merchant-to-acquirer messaging | nexo standards | Connects point-of-sale and acceptance systems to acquirers | Same press release |
| Alias payments | Berlin Group work, including the Mobile P2P Interoperability Framework | Alias lookup reuses it | Pilot back-end specification |
| Mobile integration | Embedding third-party SDKs, secure storage, accessibility | PSP apps will host the Eurosystem SDK | ECB contract notice |
| Operational resilience | The Digital Operational Resilience Act (DORA) for financial entities | PSPs must manage ICT risk and third-party providers | Regulation (EU) 2022/2554 |
| Data protection | GDPR, data minimisation | Privacy is a design principle of the digital euro | Our overview and the ECB FAQ |
You do not need blockchain skills for this work. The published pilot interfaces are conventional REST APIs, and nothing in the ECB documents we reviewed requires smart contracts.
How does digital euro work compare with integrations you already know?
Many developers will meet the digital euro after working on card acceptance, SEPA instant transfers or open banking APIs under the second Payment Services Directive (PSD2). The comparison below highlights what transfers and what is new. It is our structured reading, based on the ECB documents cited on this page.
| Question | Card acceptance today | Open banking (PSD2) today | Digital euro (as documented for the pilot) |
|---|---|---|---|
| Who connects to the central system? | Acquirers and issuers, through card schemes | Licensed third-party providers, through each bank's API | Licensed PSPs, through one Eurosystem platform |
| How many interfaces? | One per scheme and processor | One per bank, despite common standards | One central DESP interface set for every PSP |
| Standards | Scheme specifications | Berlin Group and national API standards | ISO 20022 data model, REST and JSON, CPACE, nexo and Berlin Group |
| Who builds the consumer front end? | Issuers and wallet providers | Third-party apps and banks | PSP apps with an embedded Eurosystem SDK, or the Eurosystem app |
| Holding of funds | Card account at the issuer | Payment account at the bank | Central bank money held in a digital euro account provided by a PSP, which can be linked to a bank account |
| What is new for developers? | — | — | Alias lookup across all PSPs, funding and defunding flows, offline device-to-device payments |
Two points follow. First, much existing knowledge transfers: idempotent payment requests, ISO 20022 codes and contactless acceptance are familiar ground. Second, the single central interface changes the shape of the work. Instead of integrating many counterparties, a PSP integrates once with the DESP, and differentiation moves to the app, the merchant experience and value-added services.
Worked example: a 90-day learning plan for a payments engineer
This plan uses only public documents. It is our suggestion, not an ECB programme.
- Days 1–10: the scheme. Read the ECB digital euro FAQ and the summary of the draft rulebook's structure. Write a one-page glossary: DESP, DEAN, alias, waterfall, distributing and acquiring PSP.
- Days 11–30: the back end. Read sections 1 and 2 of the pilot back-end specification. Load the YAML file into an API viewer and list the endpoints for one service, for example settlement. Note every status and reason code you meet.
- Days 31–45: error handling. Write test cases for HTTP success with business rejection, functional time-outs and safe retries with the same Request-Id. Compare them with how your current card or SEPA instant integration behaves.
- Days 46–60: the front end. Read the pilot front-end specification that matches your role (distributing PSP, acquiring PSP or acceptance instruments) and rulebook Annex B1 on minimum user experience.
- Days 61–75: standards. Study the scope of CPACE, nexo and the Berlin Group's work, and identify which already touch your systems.
- Days 76–90: a gap note. Write a short internal note: which of your systems would change, which would not, what you would need from a PSP or vendor, and what remains unknown. Date it, and set a review for the next rulebook release.
The deliverable is a dated piece of technical research, a gap analysis, not code for production. Anything built now should be treated as a prototype.
Which route fits you?
- You work at a licensed PSP. Your organisation can engage with the ECB directly. If it is one of the 36 pilot PSPs, the pilot documentation is your source of truth.
- You work at a processor, software vendor or integrator. Offer services to PSPs as a TSP. The ECB pilot FAQ explicitly allows PSPs to rely on TSPs.
- You build for merchants. Your counterpart is the merchant's acquirer or payment gateway. Prepare checkout, refund and reporting logic, and see our merchant readiness checklist.
- You run a registered start-up or research team in the EU. Consider the ECB innovation platform, if a call is open and your organisation meets the criteria.
- You are an individual developer. Learn the standards and contribute through an employer, a TSP or open standards work. No route gives individuals direct access.
What are the limits and risks?
- Specifications are indicative. The ECB states that the back-end document may be modified, and the rulebook is a draft.
- No official sandbox. Vendor "sandboxes" that simulate the DESP exist, but they are the vendors' own builds, not ECB services. Check what they are based on.
- Unpaid preparation. Innovation platform participation is unpaid, and component framework agreements involve no payment at this stage.
- No B2B first release. The ECB's innovation outcome report says the first version will not include business-to-business use cases.
- No programmable money. Designs that restrict where or when money can be spent conflict with ECB principles.
- Legislative risk. Holding limits, fees and the acceptance obligation could change in the final regulation, which affects every business case. Our legislation tracker follows the trilogue.
Where does DIGITAL EUR fit?
DIGITAL EUR is not a PSP, has no access to the DESP and does not process digital euro payments. Our reconciliation software works with today's euro bank data and runs as an in-browser demo. Possible future products related to the digital euro are listed, with their gates, on our research roadmap. None of them is available.
Frequently asked questions
Can I get access to a digital euro test environment as a developer?
Not as an individual. Pilot PSPs work with the ECB's pilot set-up, and innovation platform participants use a dedicated test environment as simulated PSPs. There is no public sandbox.
Is there a digital euro SDK for developers?
The ECB has procured an SDK for PSPs to embed in their own apps, with Almaviva and Fabrick as first-ranked providers. It is not a public developer kit, and its development will be decided later.
Do I need blockchain or smart contract skills?
No. The published pilot interfaces are REST and JSON APIs using ISO 20022 data types. Conditional payments in ECB experiments are handled by PSP logic, not by programmable money.
Which companies are working on the digital euro?
The ECB has named 36 pilot PSPs, component providers such as Feedzai, Giesecke+Devrient, Senacor and Almaviva with Fabrick, network service providers, and TSP workshop participants. Our pilot page covers the pilot participants.
When could digital euro development work become production work?
Only after the regulation is adopted and the ECB decides to issue. The ECB aims to be ready for a potential first issuance in 2029 if the law is adopted in 2026.
Where can I follow technical updates?
The ECB's rulebook page and "Technical documents and research" page publish new versions. Our news page records dated developments.
Sources
- ECB, Piero Cipollone, introductory statement at the ECON committee, 3 June 2026 (accessed 5 November 2026)
- ECB, FAQs on the digital euro pilot (accessed 5 November 2026)
- ECB, Digital euro pilot (accessed 5 November 2026)
- ECB, Summary of workshops with technical service providers, 19 March 2026 (PDF) (accessed 5 November 2026)
- ECB, Digital euro pilot – Back-end implementation specifications, 23 April 2026 (PDF) (accessed 5 November 2026)
- ECB, Digital euro scheme rulebook (draft v0.91, 2 July 2026) (accessed 5 November 2026)
- ECB, Technical documents and research (accessed 5 November 2026)
- ECB, Digital euro service providers selected, 2 October 2025 (accessed 5 November 2026)
- ECB, Contract notice: Digital euro – App and SDK (PRO-009488) (accessed 5 November 2026)
- ECB, Network service providers selected for the digital euro, 30 October 2026 (accessed 5 November 2026)
- ECB, ECB signs agreements with European standard setters, 24 April 2026 (accessed 5 November 2026)
- ECB, Call for expressions of interest in a new wave of innovation platform activities, 28 September 2026 (accessed 5 November 2026)
- ECB, Innovation platform outcome report, September 2025 (PDF) (accessed 5 November 2026)
- EUR-Lex, Regulation (EU) 2022/2554 on digital operational resilience for the financial sector (accessed 5 November 2026)