All articles
Digital EuroCBDCPaymentsBanking Technology

Digital euro in 2026: the pilot, the network contracts, the unresolved rules and what banks must prepare

In the last week of October 2026 the digital euro moved from policy to procurement. The ECB signed ten-year network contracts with Nexi and Deutsche Telekom and with Telefónica and Indra, 36 payment service providers are preparing for a 12-month pilot from the second half of 2027, and EU negotiators met again on 5 November with merchant fees, offline limits and holding limits still open. What has been decided, what has not, and a practical readiness playbook for bank technology leaders.

By Yassineh Pourebrahim · · 9 min read

For several years the digital euro was a policy debate that most bank technology teams could follow from a distance. The last week of October 2026 changed that. On 30 October the European Central Bank (ECB) announced that it had signed service agreements with two groups of network service providers that will connect banks, payment providers and national central banks to the digital euro platform. On the same day Nexi, Deutsche Telekom, Telefónica and Indra's Minsait confirmed ten-year contracts. Thirty-six payment service providers (PSPs) are already preparing for a 12-month pilot that starts in the second half of 2027. And the EU co-legislators scheduled their sixth political trilogue on the regulation for 5 November, the day this article was published, with the most sensitive questions still open. When a central bank starts buying network capacity for a decade, the project has entered its engineering phase, and banks need a plan that works whatever the final legal text says.

What happened in October 2026

The ECB bought the network for the next ten years

According to the ECB, the selected network service providers (NSPs) will provide the connectivity that links participating PSPs and national central banks to the digital euro service platform and lets its components communicate. The two winning groups are Nexi Payments with Deutsche Telekom Business Solutions, and Telefónica de España and Telefónica Global Solutions with Indra. The first contract entered into force on 28 September 2026 and initially covers the pilot; the second starts in May 2027. Both providers are to be ready from 2029 for a potential issuance, and every PSP offering the digital euro will be able to connect through either network.

A few details matter for architects. Payment Expert reports that the combined maximum value of the two agreements is about €355 million and that all services must be provided and managed from within the European Economic Area. The ECB's published award notice values the Telefónica lot at €177.66 million, records four tenders received and sets nationality and control requirements for contractors and subcontractors. Telefónica describes its part as an MPLS backbone with SD-WAN connectivity and cybersecurity services, and Nexi says its solution combines connectivity with a mediation platform for end-to-end exchange of digital euro transactions. In other words, the digital euro will run on a private, dual-sourced, European-controlled network, not on the public internet or a public blockchain.

The pilot has participants, a scope and a date

On 14 July the ECB selected 36 PSPs, from more than 50 applicants, for a pilot that is due to start in the second half of 2027 and run for 12 months. Participants include banks and non-bank providers; Payment Expert notes that Nexi is one of them. The pilot will use a beta digital euro that is "functionally and technically close" to the one foreseen in the draft legislation but has no legal tender status. Distributing PSPs will give staff of the ECB and 19 national central banks beta accounts, while acquiring PSPs will let selected merchants accept payments. The scenarios include person-to-person payments online and offline, and person-to-business payments at the physical point of sale, including software point of sale, and in e-commerce. The ECB's merchant call has closed, and the selected merchants are to be announced by early 2027.

The ECB's own planning assumption is explicit: it aims to be ready for a first issuance during 2029, assuming the regulation is adopted in 2026, and it will only decide whether to issue once the regulation exists. On 3 November Denis Beau, First Deputy Governor of the Banque de France, said that the ECB could officially commit to issuing a digital euro in 2027, paving the way for potential issuance in 2029.

The law is close in some areas and far apart in others

The European Parliament's position was set by its ECON committee on 23 June 2026 (43 votes to 14) and confirmed in plenary on 9 July by 416 votes to 169; the Council adopted its mandate on 17 December 2025. Parliament wants the digital euro to complement cash online and offline, free basic services, a cap on individual holdings, privacy-enhancing technologies and data minimisation, and a roll-out period of at least 24 months after issuance is authorised to give banks, providers and users time to prepare.

The open questions are the ones that drive bank business cases. According to the Parliament's legislative tracker, the main divergences are the compensation model (the Council's national exemptions versus Parliament's "no worse off" principle for merchants), operational aspects of the distribution model, and holding limits, which had not yet been discussed at political level. Agence Europe reports that the 20 October trilogue covered offline payment limits, anti-money laundering rules for small transactions and the move to a long-term operating model, with technical work on data protection and on use outside the euro area to follow. Börsen-Zeitung, which saw the Irish Council presidency's note on that meeting, reports that the sides still disagree on how merchant fee caps should work, who sets offline limits and whether they can differ by country, and that holding limits between €500 and €3,000 are being discussed. The declared aim is still to close the negotiations in 2026, which the paper calls ambitious.

Why this matters beyond the euro area

The digital euro is one part of a wider redesign of European payments. In the same speech, Beau framed the goal as extending the two-tier monetary system, in which central bank money and commercial bank money play distinct but complementary roles, into digital and tokenised payments. He described the erosion of domestic card schemes in Europe and the emergence of US dollar stablecoins as challenges to efficiency, safety and strategic autonomy. On the wholesale side, the Eurosystem's Pontes service launched in September 2026 and makes tokenised central bank money available for wholesale settlement, and the longer-term Appia project is expected to produce a blueprint in 2028. Beau also pointed to synergies between the digital euro and private pan-European services such as Wero; Payment Expert, by contrast, reports that fourteen banks wrote to the European Parliament about overlap between the two. Cross-border reach is growing too: on 30 October Canada and the EU announced that they will negotiate connecting Canada's Real-Time Rail with the Eurosystem's TIPS instant payment system.

For banks outside the euro area, including those that serve European clients or correspondent flows, this is the template to watch: public money on regulated rails, distributed by private intermediaries, with hard limits on holdings and strict privacy rules.

What the digital euro means for a bank's technology stack

From the materials published so far, I read five technical implications for a distributing bank.

  1. A new wallet next to the current account. Customers will hold a separate balance that is a claim on the central bank, not on the bank. Onboarding, KYC, account linking, statements, disputes and customer support all need to cover a product whose ledger the bank does not own.
  2. Limits as a live constraint. Whatever the final number, a holding cap means every incoming payment can push a wallet above its limit. My expectation is that banks will need real-time logic that moves funds between the wallet and the linked account automatically, with clear customer consent and an audit trail; this is a core banking integration, not a front-end feature.
  3. Offline as a separate security domain. Offline person-to-person payments are in the pilot scope, and limits on offline holdings are among the most contested points. Device-level secure elements, key management, fraud controls and reconciliation of offline transactions become part of the bank's risk perimeter.
  4. Connectivity and resilience. Each PSP will connect through one of two NSPs over a private network. Network onboarding, redundancy design, certificate and key lifecycle, monitoring and incident response with a new critical third party belong in the plan from the start.
  5. Economics under uncertainty. Fees for merchants and compensation for PSPs are still being negotiated. Build the cost model with ranges, and make sure the platform can change pricing rules without a release cycle.

A readiness playbook for bank technology leaders

Here is how I would organise the work while the legislators finish theirs.

  1. Appoint an owner and a programme, not a working group. The pilot runs from the second half of 2027 and Parliament's position foresees at least 24 months of roll-out after authorisation. That sounds long, but it is roughly one major core banking release cycle.
  2. Map the distributing and acquiring roles to your strategy. The ECB already distinguishes distributing PSPs, which serve payers, from acquiring PSPs, which serve merchants. Decide early which role, or both, fits your customer base.
  3. Design the wallet-to-account integration first. Funding, defunding and limit handling touch the core ledger, liquidity management and customer consent. This is the same discipline I described in Core banking modernization in 2026: keep the system of record deterministic and put new services around it through well-defined interfaces.
  4. Treat privacy as an architecture requirement. Parliament's mandate calls for data minimisation and privacy-enhancing technologies, and data access by PSPs and central banks is under technical negotiation. Classify which digital euro data you may store, for how long and for what purpose, before you build analytics on it.
  5. Prepare the network and security foundation. Plan NSP connectivity, hardware security modules and key ceremonies now. The signature and key layer is also where crypto-agility matters most, as I argued in Post-quantum cryptography in 2026.
  6. Build one payments orchestration layer. Cards, SEPA instant via TIPS, Wero, tokenized deposits, stablecoins and the digital euro will coexist. A routing layer that chooses the rail per payment protects you from betting on one scheme. In Tokenized deposits vs stablecoins in 2026 I explain why the wholesale side, now settling in tokenised central bank money through Pontes, points the same way.
  7. Run scenario-based business cases. Model deposit outflows at holding limits of €500 and €3,000, merchant fee caps under both negotiating positions and the cost of offline support. Revisit the model after each trilogue.
  8. Plan for machine customers. Software agents that pay on a customer's behalf will need scoped permissions on every rail, including public money. The identity, signed intent and scoped credential model I described in Agentic payments in 2026 is a useful starting point for those controls.

Closing thought

The digital euro is not yet law, and the ECB says it will decide on issuance only after the regulation is adopted. But a central bank that has signed ten-year network contracts, selected 36 pilot providers and set 2029 as its readiness target is not waiting either. For banks the risk is not that the digital euro arrives too fast; it is that it arrives into a core banking and payments architecture that was never designed for a balance the bank does not own, with limits that change in real time and privacy rules that restrict what can be done with the data. The banks that start the integration work now, with the open questions modelled as parameters, will be ready whatever the final compromise looks like.

References

Related articles

Tokenized DepositsStablecoinsBlockchain PaymentsBanking Technology

Tokenized deposits vs stablecoins in 2026: how banks are putting money on a blockchain

Between September and late October 2026, banks completed live tokenized deposit payments on Swift's ledger, OCBC, VersaBank and SoFi launched tokenized deposit products, the OCC finalised its GENIUS Act stablecoin rule and an EY survey of 521 decision-makers found the market moving to implementation. What tokenized deposits are, how they differ from stablecoins, and what a bank technology leader should build now.

· 10 min read

Agentic PaymentsBankingAI AgentsPayments Security

Agentic payments in 2026: how banks and card networks are learning to trust AI agents

Within a few days in October 2026, American Express, Mastercard, FIS, HSBC and Ant Digital each addressed the same question: when an AI agent pays, who authorized it, and to do what? How agent identity, signed purchase intent and scoped credentials are reshaping payment authorization, and what bank and fintech leaders should do now.

· 10 min read

Core BankingAI AgentsBanking TechnologyAI Governance

Core banking modernization in 2026: AI agents on legacy cores, runtime guardrails and the wrap-or-replace decision

In October 2026 four announcements reframed core banking modernization. Sutherland and FlowX.AI offered to run more than 220 AI agents on top of the cores banks already own, Emprise Bank chose an AI-native core from Maximum, SBS put sovereign generative AI inside its core platform, and BBVA said it will explore NVIDIA's OpenShell Reference Architecture for governing agents at runtime. What each path means for legacy core banking systems, where the risks sit, and a practical playbook for bank technology leaders.

· 10 min read