What the digital euro pilot asks of payment companies
Europe's digital euro preparations now include payment providers, open technical standards and merchant recruitment. The work ahead reaches well beyond the wallet.
On 15 September 2026, the Eurosystem opened a call for online and mobile merchants to join the digital euro pilot. It followed agreements with three European standards organisations and the selection of 36 payment service providers. The project now had participants, interfaces and payment journeys to test.
These preparations did not amount to a currency launch. The operational pilot is planned for the second half of 2027 and is expected to run for 12 months, using a beta digital euro without legal tender status. A decision on issuance remains dependent on the adoption of relevant European legislation. The immediate commercial question is how payment companies prepare to test a new service before its final market exists.
A pilot with a defined perimeter
The ECB selected the 36 providers after receiving more than 50 applications. The group includes banks and nonbank payment businesses of different sizes and business models. Some will distribute the beta digital euro to participating consumers, some will enable merchants to accept it, and some will perform both roles. This division matters because a payment succeeds only when both sides of the transaction can use the service.
The planned exercise involves the ECB, 19 national central banks, participating staff and selected merchants. Scenarios include online and offline payments between people, payments at physical points of sale, and online and mobile commerce. This controlled testing population can reveal defects and operational constraints. It cannot establish demand across the entire euro area.
The checkout carries the integration cost
The merchant call asks participants to test customer payment journeys and the fit with existing checkout processes. Participation is voluntary and unremunerated. Selected merchants must sign an agreement with the ECB and establish or adapt a relationship with an acquiring provider in the pilot. Selection considers operational readiness, market reach and suitability for testing.
Scroll to view all columns
| Comparison | Consumer distribution | Merchant acceptance |
|---|---|---|
| Main responsibility | Provide participating users with accounts and payment services. | Enable participating merchants to accept beta digital euro payments. |
| Product work | Integrate services into a provider app or use the Eurosystem app. | Connect physical, online or mobile acceptance to merchant processes. |
| Operational support | Onboard users and support the participating account and payment services. | Provide onboarding, integration guidance and merchant assistance. |
Roles described in the ECB's selection announcement and pilot FAQ. A participating provider may perform both roles.
The work is familiar to payment software companies. A merchant has to present the payment option, receive an intelligible result and reconcile that result with the order. When a customer leaves the checkout or a transaction fails, staff need to understand what happened. These steps determine whether an additional payment method can be introduced without creating disproportionate service costs.
The ECB's pilot FAQ asks for merchant feedback on implementation effort, checkout integration, defects, support and transaction outcomes. It also identifies completion times, cancellations and repeated acceptance among the useful observations. That focus gives investors a practical way to assess progress: look for measured operating results from the intended payment journey, including unsuccessful attempts.
Open standards change the engineering question
The ECB agreed with European Card Payment Cooperation, nexo standards and the Berlin Group to reuse existing open technical standards for online digital euro payments. CPACE, developed by European Card Payment Cooperation, supports contactless interaction between payment devices and terminals. Nexo standards connect merchant systems with payment providers and acquirers. Berlin Group standards support functions including payments using aliases, balance checks and reconciliation.
The ECB expects reuse to reduce adoption costs and improve interoperability, benefits that the pilot still needs to test. A startup should examine which existing components can be reused, what needs certification and where additional integration is necessary. An established standard can reduce some technical uncertainty while leaving substantial work in testing, operations and customer support.
The work continues after payment approval
The pilot FAQ includes onboarding, settlement, liquidity management, incident handling and refunds among its operational learning areas. Each creates a software requirement beyond displaying a successful payment. Finance teams need usable records. Service teams need a way to investigate a customer's complaint. Operators need to distinguish a delayed response from a failed transaction before attempting recovery.
Offline payments add a separate set of conditions. The FAQ describes transfers using near field communication and secure elements, with balances funded before offline use. Money received offline can then be spent again offline without reconnecting. These proposed capabilities are material to the user experience, but the pilot remains a test of how they work together. A demonstration of one successful transfer cannot establish reliability across devices, support situations and operating conditions.
An investment case before issuance
The pilot creates opportunities to learn about acceptance software, integration services and payment operations. The timing and scale of future commercial revenue remain uncertain. Participation is unremunerated and requires resources, so a startup needs to explain how that work fits its funding plan. Selection establishes a provider's role in the trial without assuring future market share.
The more durable investment question is whether the company is solving a payment problem that customers recognise: expensive integration, unreliable acceptance, difficult reconciliation or slow incident resolution. The digital euro pilot offers a new setting in which to test those capabilities. Evidence that a product reduces merchant effort or improves service reliability will remain more informative than a revenue forecast built around an issuance date that has yet to be decided.
Investment implications
- Standards agreements, provider selection and merchant recruitment prepare the pilot; issuance still depends on legislation.
- Consumer distribution and merchant acceptance create different integration, support and product requirements.
- Pilot participation can generate operating evidence, but it does not establish future transaction volume or guaranteed revenue.
Sources
- ECB selects 36 payment service providers to join digital euro pilot (opens in a new tab)
European Central Bank
- Call for online and mobile merchants to participate in digital euro pilot now open (opens in a new tab)
European Central Bank
- ECB signs agreements with European standard setters to facilitate digital euro payments (opens in a new tab)
European Central Bank
- Call for payment service providers to participate in digital euro pilot now open (opens in a new tab)
European Central Bank
- FAQs on the digital euro pilot (opens in a new tab)
European Central Bank
Published
