.png)
The ECB Is Asking Merchants to Test the Digital Euro. Here's What Actually Changes
The European Central Bank has moved the digital euro from policy discussion towards merchant operations.
On 15 September 2026, the ECB opened applications for e-commerce and mobile-commerce merchants to participate in a controlled, 12-month digital euro pilot expected to run in the second half of 2027. Applications close at 17:00 CET on 27 October 2026, with an information session scheduled for 6 October 2026.
The announcement matters because it turns a central bank digital currency (CBDC) into a checkout decision.
For merchants, the question is no longer simply whether the digital euro will exist. It is whether their payment stack can accept, route, reconcile and manage another payment rail without adding operational friction.
The real competition is not cash versus CBDC. It is about who controls the decision layer at checkout.
The pilot is not a digital euro launch
The ECB’s pilot will use a “beta digital euro” in a controlled environment. It is designed to test technical readiness, operational processes and user experience rather than introduce a fully launched currency.
The pilot is expected to run for 12 months from the second half of 2027. The ECB will test person-to-person and person-to-business payments across online, mobile and proximity environments.
The current merchant call is specifically aimed at e-commerce and mobile-commerce businesses that:
Are legally established in the European Union
Can serve customers across at least two pilot locations
Operate a suitable e-commerce website or mobile application
Can integrate a dedicated or adapted checkout flow
Are willing to enter into an agreement with the ECB
Can establish or adapt a relationship with an acquiring pilot PSP
Selected merchants will work with one of the pilot acquiring PSPs to integrate and test beta digital euro payments. They will also provide feedback on onboarding, checkout performance, payment completion, refunds, reconciliation and operational complexity.
Participation is voluntary and merchants will not be charged fees by pilot PSPs for pilot payment services. However, the ECB states that merchants will bear their own participation costs and will not receive financial remuneration.
That distinction is important. The pilot is free at the payment-service level, but it is not necessarily free in engineering time, testing, compliance or operational support.
1. The digital euro is designed to coexist with cards and wallets
The first misconception to avoid is that the digital euro is intended to replace cards.
It is better understood as a public digital-money rail that sits alongside cards, bank transfers, wallets and cash. The ECB describes the digital euro as a digital equivalent of cash: a liability of the Eurosystem, available for online and offline use, non-remunerated and subject to holding limits.
Under the proposed framework, individual holding limits would be set by the European Commission and reviewed at least every two years. Businesses would generally not be able to hold digital euro as a long-term balance, although incoming payments could be accumulated for a limited operational period, commonly described as up to 24 hours.
That structure gives the digital euro a different economic role from a bank account, card scheme or commercial stablecoin. It is intended to support payments, not become a yield-bearing treasury asset.
The market context also argues against a “card killer” narrative. According to the ECB’s SPACE 2024 study, cash still represented 52% of euro-area point-of-sale transactions in 2024, although that was down from 59% in 2022.
At the same time, cards accounted for 57% of all non-cash transaction volumes in the second half of 2025, according to the ECB’s payments statistics.
These figures describe different parts of the market, but together they show the reality merchants face: payment behaviour is already plural. The digital euro will add to that mix rather than simplify it.
2. The merchant challenge is acceptance complexity
Adding another payment method sounds straightforward. In practice, it creates another operating model.
A merchant accepting the digital euro will need to consider:
Acquiring and contractual relationships
Checkout integration and authentication
Payment status and exception handling
Refund and cancellation flows
Settlement timing and destination accounts
Reconciliation with existing card and bank payment data
Customer support and transaction disputes
Risk, compliance and reporting requirements
The ECB’s pilot documentation makes this visible. Merchants must establish or adapt a relationship with an acquiring pilot PSP, integrate the beta digital euro into an e-commerce or mobile-commerce environment and support ongoing operational reporting.
The pilot also requires a dedicated or suitably adapted checkout accessible only to pilot participants. That is a small but revealing detail: even a controlled test requires segmentation, eligibility controls and a separate customer journey.
For a large enterprise, the challenge is rarely adding one more button. It is ensuring that payment data, settlement records, refunds and accounting entries remain consistent across every channel.
This is where payment orchestration becomes the control layer.
An orchestration platform can connect multiple acquirers, payment methods and settlement routes while presenting a unified checkout and reporting model to the merchant. Over time, AI payment routing can help determine which rail should be used based on availability, cost, risk, customer preference, location and previous payment performance.
The digital euro therefore strengthens the case for AI payments. The value is not just accepting more methods. It is deciding intelligently between them.
3. Offline payments preview the next layer of complexity
Offline functionality is one of the digital euro’s most distinctive features.
The ECB’s pilot FAQs explain that offline person-to-person payments will be tested through NFC proximity. Two devices can exchange value without an internet connection, with secure elements helping protect balances and prevent double spending.
The current e-commerce and mobile-commerce merchant call focuses on online person-to-business payments. Offline P2B merchant acceptance is not the central use case in this specific application process.
Nevertheless, offline functionality is a useful preview of what CBDC payments could require more broadly. A merchant will eventually need to understand what happens when:
A customer’s device is offline
A payment is authorised but not immediately visible in the merchant system
A balance exceeds a holding limit
Funds need to be swept to a commercial bank account
A transaction reconnects after a delay
The customer receives a payment confirmation but the merchant has not yet completed reconciliation
These are not theoretical questions. They are acceptance, risk and accounting questions.
The pilot’s holding-limit and waterfall mechanisms also reinforce the point. Digital euro transactions may need to draw from or return funds to a linked commercial bank account when limits or balances require it. Merchants will not simply receive an unrestricted digital balance and manage it like ordinary deposits.
4. The 36 PSPs are the first distribution layer
The ECB has selected 36 payment service providers for the pilot. They include banks and non-bank PSPs, with participants taking on distributing, acquiring or both roles.
For merchants, acquiring PSPs are the important relationship. They will provide the acceptance solution, onboarding support, technical guidance and operational assistance required to test the beta digital euro.
That arrangement also offers a preview of how a future digital euro ecosystem may work. Merchants are unlikely to connect directly to the ECB in a full rollout. Instead, they will interact with the digital euro through PSPs, just as they currently rely on acquirers, gateways and payment processors for card acceptance.
The pilot’s direct merchant agreement with the ECB is specific to the test environment. It should not be treated as the final commercial or legal model.
The more durable lesson is that CBDC acceptance will require coordination between central-bank infrastructure, commercial PSPs, technical service providers and merchant platforms.
That is another reason the payments foundation model matters. Businesses will need a connected data and decision architecture that can understand the full transaction lifecycle, from checkout through authorisation, settlement, reconciliation and reporting.
What merchants should do before the October deadline
Eligible merchants considering the pilot should treat the application as an operational readiness exercise, not just a regulatory form.
Before applying, they should:
Map every existing payment method and acquiring relationship.
Identify whether the checkout can support a dedicated pilot flow.
Confirm how payment status, refunds and cancellations reach the ledger.
Assess the engineering effort required for a new PSP integration.
Define ownership across payments, finance, risk, technology and customer support.
Model how incoming digital euro payments would be reconciled and swept.
Prepare questions for the ECB information session on 6 October.
Even merchants that do not participate should monitor the pilot. Its findings will indicate how much integration work, operational support and reconciliation complexity may be involved in a future CBDC rollout.
The wider payments industry should also read the pilot alongside other infrastructure developments. Quantum Payments’ analysis of stablecoins and the WTO’s 3% finding, tokenised deposits and the Bankchain moment, and the move towards 24/7 settlement points to the same conclusion: payment rails are multiplying.
The strategic advantage will not come from choosing one rail early. It will come from managing several rails intelligently.
The checkout decision layer is the real battleground
The digital euro will not make cards, wallets, cash, stablecoins or bank transfers disappear.
Instead, it will make checkout decisions more consequential.
A merchant’s payment infrastructure will need to determine which method is available, compliant, cost-effective and most likely to complete. It will also need to explain the result to finance teams, customer service staff and auditors.
That is the role of payment orchestration and AI payment routing.
The winning platform will not simply add a digital euro button. It will decide when that rail should win, when another method is more appropriate and how the entire transaction is reconciled afterwards.
The ECB is asking merchants to test the digital euro. The more important question for the industry is whether merchants are ready to test their own control layer.
Sources and further reading
SEO and publishing details
Meta title: Digital Euro Pilot: What Merchants Need to Know Before the October Deadline
Meta description: The ECB’s digital euro pilot turns CBDC payments into a merchant checkout decision. Learn what changes for acquiring, integration, offline payments and payment orchestration.
Slug:digital-euro-pilot-merchants-what-changes
Primary keyword: digital euro
Secondary keywords: CBDC payments, AI payments, payment orchestration, AI payment routing, payments foundation model