SØGEMULIGHEDER
Hjem Medier Explainers Forskning & Offentliggørelser Statistik Pengepolitik €uroen Betalinger & Markeder Kariere & Job
Forslag
Sortér efter
Findes ikke på dansk

FAQs on the digital euro pilot

Updated on 5 March 2026

Digital euro pilot overview

Pilot roles and responsibilities

Application process and participation in the pilot

Q1 What is the digital euro pilot?

The digital euro pilot is a limited practical exercise to help the Eurosystem learn how a digital euro could work in everyday situations. The pilot will help the Eurosystem assess its technical, operational and user readiness for a potential digital euro by validating the infrastructure in real-life conditions and gathering evidence to inform future decisions.

It will give the Eurosystem hands-on insights by enabling a limited group of individual end users (Eurosystem staff) and business end users (e.g. merchants) to make and receive payments using a beta version of the digital euro. For example, an ECB staff member could send money to a colleague, pay at the ECB canteen using their phone, or buy an item online, while the Eurosystem monitors the process and collects feedback. This will support an assessment of the system’s robustness, scalability and usability, and strengthen cooperation between payment service providers (PSPs), merchants and central banks.

The pilot will also help the Eurosystem to refine the digital euro design and user experience and to assess communication and branding approaches. Updates will be communicated transparently, reflecting the Eurosystem’s commitment to building trust by preparing responsibly for the potential introduction of a digital euro, should a decision to issue be taken in the future.

Q2 Does the digital euro pilot mean that the ECB has decided to issue a digital euro?

No. Preparing for the digital euro pilot does not pre-empt any decision to issue the digital euro. The ECB will only take a decision on whether to issue the digital euro once the EU co-legislators adopt the Regulation on the establishment of the digital euro (digital euro Regulation).

In the current phase of the digital euro project, the Eurosystem is continuing to prepare for the potential introduction of a digital euro, following a flexible approach to ensure alignment with the legislative process. The pilot will ensure that the Eurosystem is technically and operationally ready to act efficiently and effectively when the legislative process concludes.

Q3 How would a beta digital euro differ from the digital euro?

The pilot will use a digital means of payment referred to as the “beta digital euro” that is different from the digital euro foreseen in the legislation.

The beta digital euro will be a digital means of payment issued by the Eurosystem central banks upon receipt of funds from pilot PSPs, leading to the creation of Eurosystem liabilities vis-à-vis third parties. It will be a liability (representation of value in the books of the Eurosystem) subject to the rules for cashless payment transfers applicable to PSPs, individual end users and business end users. As regards the online beta digital euro exclusively, it will be considered as “scriptural money”, falling under the current definition of “funds”, under the revised Payment Services Directive (including relevant level 2 legal acts). It will not be a banknote and/or a coin, and it will not constitute an account held directly with the ECB or any other Eurosystem central bank.

Participants would hold or open a commercial bank money account with participating payment service providers (pilot PSPs) for the duration of the pilot.

Q4 What is the timeline for the digital euro pilot?

The envisaged timeline for the digital euro pilot consists of the following three phases.

  1. Pilot preparation phase (first half of 2026): the call for expression of interest was published on 5 March 2026. PSPs must submit their applications by 14 May 2026. Additional relevant documentation will be provided to PSPs during the application window, including user journeys, end-to-end flows, functional requirements and the PSP participation agreement. The ECB and participating national central banks (NCBs) will evaluate PSP applications and notify applicants of the selection outcome by the end of June 2026.
  2. Pilot development phase (starting in the third quarter of 2026): after signing the PSP participation agreement, pilot PSPs will start preparing for their participation in the pilot. This entails the development of pilot payment services, digital euro service platform (DESP) onboarding and integration, user testing and back-end certification, and the onboarding of end users.
  3. Pilot operational phase (starting in second half of 2027, 12-month duration): once the pilot becomes operational, pilot PSPs will provide pilot payment services in close cooperation with the ECB and their national central bank (NCB) counterpart. Their tasks will include onboarding end users, processing operational transactions for specific use cases and facilitating the collection of feedback from end users for assessment by the ECB.

Throughout all phases of the pilot, the ECB and participating NCBs will actively engage with pilot PSPs to collect feedback, clarify requirements and ensure adequate support.

Q5 What is the geographical scope of the digital euro pilot?

The pilot will take place on-site at the ECB and at participating NCB across the euro area.

All interested PSPs are encouraged to apply to participate in the pilot. The Eurosystem welcomes a broad geographical distribution of participants.

Pilot PSPs must sign a PSP participation agreement with the NCB of a country where they have an established headquarters or branch, or to which they are passporting their EU license. Provided they are authorised to operate in that country, this set-up enables cross-border participation, allows pilot PSPs to provide pilot payment services to individual end users (Eurosystem staff) in locations other than at the site of NCB with which they have signed the participation agreement.

Q6 What payment use cases will the digital euro pilot cover?

The pilot will validate four use cases:

  • Online P2P transactions using a user alias[1] or DEAN[2]: a payer transfers funds to a payee (both are individual end users), initiating the transaction by entering the unique identifier of the payee in the payment application. The transaction typically takes place remotely and can be completed when the payer and payee are not in physical proximity. The transaction is completed when the payer’s device is connected to the internet. Therefore, it is classified as an online payment.
  • Offline P2P transactions via NFC: a payer transfers funds to a payee (both are individual end users), initiating the transaction by entering the amount in the payment application on the payer’s device without the need for either device to be connected to the internet. The transaction is completed via NFC by tapping the two devices together. Since the transaction is settled instantly between the participating devices and does not require an internet connection, it is classified as an offline payment.
  • Online P2B transactions at the point of sale via NFC: a payer (individual end user) transfers funds via their payment application to a payee merchant (business end user) as payment for goods or services at the point of sale. The payee is equipped to accept payments via a SoftPOS[3] application on their device. The transaction is initiated when the amount is entered in the SoftPOS application, either automatically by the cashier system or manually by the payee. The transaction is completed by tapping the devices of the payer and the payee together, allowing the transaction details to be exchanged between the devices via NFC. Since both devices must be connected to the internet for the transaction to be completed, it is classified as an online payment.
  • Online P2B transactions in e-commerce or m-commerce using a user alias or DEAN: a payer (individual end user) transfers funds to a payee (business end user) as payment for goods or services on an e-commerce or m-commerce platform. The transaction is initiated when the payer selects the beta digital euro as the payment method on the payee’s mobile website or payment application. If available, the default payment application opens via overlay (seamless embedded app-to-app redirect). If no default payment application has been defined, the payer inserts their unique identifier (alias or DEAN) in the payment gateway provided by the payee and is prompted to open their payment application. In both cases, the payer verifies the payee and payment details and then confirms, authenticates and authorises the transaction. The payer receives confirmation of the payment in their payment application and on the payee’s mobile website or payment application. The transaction is completed via the internet. Therefore, it is classified as an online payment.

Q7 What is the role of pilot PSPs in the digital euro pilot?

As key partners of the Eurosystem during the pilot, pilot PSPs will enable pilot payment services for end users and support the collection of feedback. The pilot distinguishes between two PSP roles: distributing and acquiring. Each pilot PSP will fulfil one or both of these roles.

  • Distributing PSPs will enable individual end users to use pilot payment services – such as access, liquidity and transaction management – through the Eurosystem-provided digital euro app or via integration in the PSP’s proprietary app.
  • Acquiring PSPs will enable business end users (merchants) to use pilot payment services, including access, liquidity and transaction management and payment acceptance functionalities. For example, they may be asked to offer a SoftPOS solution and/or an e-commerce/m-commerce solution to enable the acceptance of beta digital euro by merchants.

The Eurosystem provides the digital euro service platform (DESP)[4] and enables pilot PSPs to connect to it during the pilot, ensuring end-to-end product testing and validation of the value proposition. Pilot PSPs will gain first-hand experience of the beta digital euro ecosystem and provide feedback that will help to further shape its technical specifications.

Q8 What are the roles of the ECB and euro area NCBs in the digital euro pilot?

The ECB is coordinating the digital euro pilot at the Eurosystem level, with euro area NCBs acting as the main operational counterparts for pilot PSPs at the national level.

During the pilot, participating NCBs will, with support from the ECB:

  • provide pilot PSPs with the documentation (e.g. technical specifications, user journeys) necessary to develop and release pilot payment services for the use cases covered in the pilot;
  • facilitate liquidity operations related to the digital euro pilot on behalf of their pilot PSPs;
  • collect feedback from pilot PSPs and support their collection of feedback from end users.

Q9 Who is eligible to participate in the digital euro pilot as an individual end user or a business end user (merchant)?

The individual end users in the digital euro pilot will be members of staff from participating Eurosystem central banks. To be eligible to take part, they must be or become a customer of a pilot PSP.

Merchants (both in-store and e-commerce/m-commerce) are eligible to participate in the digital euro pilot if they have both:

  • a contractual relationship with the ECB or a participating NCB for the duration of the pilot;
  • a contractual relationship with a pilot PSP for acquiring services.

Q10 How can PSPs apply to participate in the digital euro pilot? 

To apply, PSPs are required to complete a questionnaire (published as Annex 2 to the call for expression of interest) and submit it to the Eurosystem together with any evidence needed to support their application. The call and the related documentation are published on the ECB’s website.

The application window opened with the launch of the call for expression of interest on 5 March 2026. Applications must be submitted to digitaleuro-pilot@ecb.europa.eu by 17:00 CEST on Thursday, 14 May 2026.

Q11 Are there specific eligibility requirements for pilot PSPs? How will PSP applications be assessed?

Yes. The Eurosystem will assess all applications based on two defined sets of selection criteria: eligibility requirements and weighted evaluation criteria. These are set out in Annex 2 to the call for expression of interest.

The eligibility requirements ensure that only PSPs with the necessary regulatory license and technical and operational capabilities are eligible to proceed to the weighted evaluation stage. PSPs that do not meet all the eligibility requirements will not be considered for selection.

The weighted evaluation criteria assess eligible PSPs based on factors that are relevant to achieving the objectives of the pilot, in order to ensure that the pilot has comprehensive coverage (for example, in terms of geographical footprint, use cases and end users). PSPs are not required to meet all the weighted evaluation criteria to be considered for selection.

Q12 Can PSPs submit joint applications or apply as a joint venture?

No. Joint applications and joint ventures are not permitted. Organisations wishing to participate in the digital euro pilot together should instead designate one PSP as the official applicant. This PSP would submit the application and, if successful, act as the formal participant in the pilot. The other organisation(s) would act as technical service providers (TSPs) and do not need to be declared individually in the application.

For example, if a distributing PSP relies on a third party to provide specific services, such as infrastructure services or a front-end solution, the distributing should submit the application covering the services it intends to provide in the pilot, including those delivered with support from that third party, even if under their existing contractual arrangement, the third party would be considered a technical service provider (TSP) for the purposes of the pilot. This also includes cases where a distributing PSP relies on a third-party front-end solution (e.g. an external wallet or payment app) to provide certain user-facing functionalities.

Q13 Can PSPs participate in the digital euro pilot via a direct contract with the ECB?

No. Pilot PSPs must sign the PSP participation agreement with a participating euro area NCB (typically the NCB of a country where they are established or operate under passporting). Once selected, and after signing the agreement, a PSP may provide pilot payment services on-site at the ECB (e.g. by ECB staff and participating merchants) as part of the overall pilot set-up.

Q14 To what extent can pilot PSPs reuse investments made in the context of the digital euro pilot (e.g. infrastructure, integration, compliance)?

As the Eurosystem is following a flexible and modular approach in its continued preparation for a digital euro, in line with the legislative process, it is envisaged that pilot PSPs and all other stakeholders, including the Eurosystem, will be able to build upon the investments made during the pilot when implementing digital euro services, should a decision to issue the digital euro be taken.

The extent to which pilot PSPs can reuse their investments will, however, depend on their individual implementation strategy and other factors, such as the final content of the digital euro Regulation.

Q15 Why should PSPs participate in the digital euro pilot?

Participation in the pilot offers PSPs an opportunity to actively contribute to shaping the future of payments in Europe, and to engage directly with the Eurosystem’s operational and technical teams.

The pilot has already attracted interest from a range of PSPs, many of which joined a preliminary focus session in January, underlining the market relevance of the project.

Pilot PSPs will gain early operational experience with the envisaged set-up for providers of digital euro services, including onboarding, settlement, liquidity management, incident handling and refunds, and will be able to identify practical implications for their systems, processes and resourcing.

Participation also provides a structured channel to share evidence-based feedback on how the beta digital euro infrastructure and priority use cases perform in real-life conditions, helping inform potential improvements. In addition, pilot PSPs will be well placed to suggest ways to optimise implementation choices (e.g. integration approach, use of existing components and partners, internal vs. external development), which can help manage costs, compliance and capacity needs.

The pilot also provides first-hand experience with the beta digital euro product, which can support PSPs’ preparation for a potential roll-out of the digital euro and enable them to develop value-added services.

Q16 What are the expected workload and costs for pilot PSPs? 

The workload and costs of participating in the digital euro pilot will be different for every pilot PSP and will depend on their individual business model, existing infrastructure and internal cost structures. Key cost drivers may differ according to the level of integration required, the balance between internal and external development and the scope of the PSP’s participation in the pilot. The workload required may vary based on aspects such as the extent of system modularity, prior experience with comparable initiatives, and the scope of pilot activities chosen by the pilot PSP. Additionally, pilot PSPs are invited to cooperate with subcontractors such as TSPs to support their development efforts, as well as to leverage existing technical solutions. Pilot PSPs will bear their own costs related to their participation in the pilot and no subsidy is foreseen.

Q17 Will participating PSPs be remunerated?

No. Pilot PSPs will not receive any remuneration or incentives of any kind (financial or non-financial) from the Eurosystem for their participation in the pilot, and their expenses will not be reimbursed. The same applies to business end users and individual end users.

Q18 Will PSPs receive operational support during the pilot?

Yes. The ECB and participating NCBs will provide operational support to pilot PSPs during the pilot development phase and operational phase of the pilot, including with liquidity management. Additionally, all pilot PSPs will be connected to the overarching pilot exercise, together with all other participating NCBs and the ECB. More detailed information (including on onboarding, testing and training) will be shared with pilot PSPs after the selection process.

Q19 What will PSPs need to develop when participating in the digital euro pilot?

Pilot PSPs will develop pilot payment services for the priority use cases during the digital euro pilot. They will receive detailed documentation on several aspects of the envisaged set-ups for these use cases, including connectivity setup, requirements for front-end implementation, common services and back-end infrastructure. While pilot PSPs are expected to develop pilot payment services independently, they will be able to contact the Eurosystem for technical clarifications and support. To ensure efficient development, pilot PSPs should decide on their implementation approach and plan delivery accordingly, and are invited to cooperate with subcontractors such as TSPs.

Q20 Can PSPs outsource pilot activities to third parties such as technical service providers (TSPs)?

Yes. Outsourcing will be possible, as it can give pilot PSPs more organisational flexibility and support their development efforts. Pilot PSPs may, for example, call on TSPs to leverage specialised expertise or implement specific functionalities more quickly, including through existing technical solutions and partnerships. In line with the EBA's guidelines on outsourcing arrangements, the pilot PSP remains fully responsible for its role and obligations in the pilot.

The ECB recognises the key role TSPs play in today’s retail payment ecosystem supporting PSPs with technical solutions or services. The ECB is engaging with TSPs directly via dedicated workshops to facilitate their critical role during and after the pilot and to ensure market readiness.

These FAQs support payment service providers (PSPs) by addressing common questions and providing clarifications related to the PSP call for expression of interest to participate in the digital euro pilot.

If your question is not covered, please submit a new question.

The replies to the FAQs are non-binding and do not extend in any way the rights and obligations deriving from applicable legislation nor introduce any additional requirement than those included in the relevant contractual documentation for the pilot. The expressed views are not authoritative and cannot prejudge any future actions the ECB may take.

  1. A unique pseudonymous identifier that is used to protect the user’s identity when processing payments. It can only be attributed to an identifiable natural or legal person by the pilot PSP distributing the beta digital euro or by the beta digital euro end user.

  2. The compulsory unique identifier of a beta digital euro account with technical and design elements similar to the digital euro access number (DEAN) provided for in the proposed Regulation on the establishment of the digital euro.

  3. SoftPOS (software point of sale) is a software-based solution facilitating contactless payment acceptance via a commercial off-the-shelf device, for example a smartphone.

  4. The DESP is the technical platform which enables issuance and redemption of beta digital euro and provides functions such as access management and alias lookup services. A more detailed overview of the DESP can be found in the high-level architecture of the beta digital euro.