The European Payments Council (EPC) has started work on SCARLET, a common framework for accepting EU Digital Identity Wallets in payment authentication. The EPC Board approved the project on 24 September 2026, and the EPC announced it publicly on 19 October. The goal is simple: stop wallet acceptance from splintering across more than 3,000 payment service providers (PSPs) and at least 27 national wallet providers.

What Is SCARLET?

SCARLET stands for Strong Customer Authentication Acceptance Rulebook and Liability Framework for EUDIW Transactions. It will set shared business, contractual, functional, operational, and technical rules for using digital identity wallets in payments.

The EPC launched it to prevent fragmentation. Without common rules, each wallet or market could bring its own implementation demands, contracts, and processes. Banks and payment firms would then face higher costs. Customers would get an uneven experience from one country or provider to the next.

The EPC is working with the European Commission and the European Banking Authority (EBA). The technical work will build on the Commission’s Architectural Reference Framework, the TS12 specification, and findings from large-scale wallet pilots. SCARLET remains under development, so its dates describe a planned timetable and not a finished rulebook.

How Digital Identity Wallets Fit Into Payment Authentication

EU Digital Identity Wallets let people store and share verified credentials. Users can prove specific details about themselves when they access public or private services. In finance, that could mean identifying a customer, opening an account, or approving a payment.

Strong Customer Authentication (SCA) already sits at the core of EU payments law. Under PSD2, it generally requires two independent elements from the categories of knowledge, possession, and inherence. Exemptions apply in some cases.

A wallet can serve as one route to meet those requirements. However, it does not replace them. Any wallet-based authentication must still satisfy the relevant legal and technical standards.

The Commission says PSPs will need to accept wallets for SCA when users request it and the applicable obligations apply. It also describes wallet authentication as compatible with existing infrastructure, including card payments and account-to-account transfers.

The Regulatory Driver: eIDAS 2.0

Regulation (EU) 2024/1183, known as eIDAS 2.0, revised the EU digital identity framework. It created the legal basis for the wallets and gave users more control over what they share.

The regulation sets the direction, but it leaves practical questions open. Providers still need to know how authentication works, what data moves between parties, and which specifications apply. They also need clarity on who bears responsibility when something goes wrong.

SCARLET aims to answer those questions through industry-wide rules. It is not legislation. It is a standardization effort that supports consistent implementation.

The EPC plans two versions. Version 1.0 will cover the current PSD2 and EBA environment. Version 1.1 will then extend to the forthcoming Payment Services Regulation (PSR). This phased approach helps providers plan, and it keeps the rules aligned with changing law.

Why the 3,000-Plus PSP Figure Matters

Scale is the strongest argument for a shared rulebook. More than 3,000 PSPs and at least 27 national wallet providers will need to work together. They differ in size, technology, customer base, and market reach.

If each provider builds its own approach, a wallet might work smoothly with one PSP and awkwardly with another. Providers would also pay to build and maintain many separate integrations.

A common framework could ease that burden in several ways:

  • Banks could plan multi-market rollouts with more confidence.
  • Fintech firms would see clearer technical and contractual requirements.
  • Wallet providers would face a more consistent acceptance environment.
  • Customers could rely on one wallet across supported services.

Standardization alone will not guarantee smooth adoption, though. Providers must still implement the rules, test interoperability, and manage operational risk. The final impact will depend on the finished rulebook and on how wallets perform in real payment settings.

What SCARLET Could Mean for Banks and Fintechs

First, implementation could become more predictable. A shared reference point reduces the need to interpret every operational question alone. That helps institutions that operate in several European markets. The actual degree of reuse will depend on the final specifications.

Second, cross-border interoperability should improve. Compatible rules mean fewer differences for customers moving between markets. Still, common authentication rules will not remove national licensing requirements or differences in payment infrastructure.

Third, liability may become clearer. The framework’s name includes a liability element, which signals how much the allocation of responsibility matters. A single payment can involve the customer, the wallet provider, the PSP, and supporting infrastructure. The announcement does not settle liability in every scenario, so it is too early to predict specific outcomes.

Finally, wallets add another authentication route. Banks could build verified digital credentials into customer journeys. Success will depend on user adoption, ease of use, security, and integration with existing systems.

Technical Standards and European Coordination

The EPC does not plan to create a separate technical ecosystem. It will build on existing European specifications instead. That choice matters because interoperability needs compatible protocols, data structures, and procedures, not only shared policy goals.

Security and privacy shape the design too. The EU framework stresses user control and secure wallet design. It also promotes selective disclosure, which lets users prove one attribute without handing over a full personal profile. Payment providers must balance those principles against their own security and compliance duties.

Precise technical requirements will emerge as the rulebook moves through consultation.

The SCARLET Roadmap

The EPC has set out a phased plan:

  • 24 September 2026: The EPC Board approved the initiative.
  • 19 October 2026: The EPC announced SCARLET publicly.
  • Summer 2027: The EPC plans a public consultation on the first version.
  • December 2027: The EPC plans to publish version 1.0, focused on PSD2 and EBA standards.
  • 2028 or 2029: Version 1.1 is intended to extend to the PSR, aligned with the expected compliance period.

These dates reflect the announced plan. Final deadlines will depend on the finished rulebook and the underlying legislation.

What Payment Providers Should Watch

Several issues will decide how useful SCARLET proves in practice:

  • Scope: Which use cases, processes, and contracts the final rulebook covers.
  • Liability: How the rules divide responsibility among participants.
  • Interoperability: How SCARLET fits with Commission specifications and current authentication systems.
  • Privacy and security: How providers combine efficient authentication with data minimization and consent.
  • Customer experience: Whether the journey feels clear and reliable enough to drive adoption.

Providers should also follow official updates from the EPC, the Commission, and the EBA. The initial announcement is not a technical specification.

The FinRate Takeaway

SCARLET shows how closely digital identity and payment authentication are now linked in Europe. The scale of the market makes the project consequential, because inconsistent implementation would be costly for the industry and frustrating for users.

The initiative is not a finished standard yet. Even so, it marks an important step toward coordinated wallet acceptance. For banks, payment institutions, and fintech firms, the message is clear. Digital identity now belongs in payment authentication planning, and the next phase is turning regulatory direction into systems that work securely and consistently.

EPC Launches SCARLET to Standardize EU Digital Identity Wallet Acceptance for Payments