If you're evaluating an integration with the European digital identity wallet, you've probably already run into these two acronyms without finding a clear explanation. Here's what we've verified while building Todis.
RPAC and RPRC, in two sentences
A relying party (you, or a service like Todis acting on your behalf) must register with its member state to be recognized by eIDAS 2.0 wallets. That registration produces two distinct documents: the RPAC (Wallet-Relying Party Access Certificate) attests to who you are and authenticates your requests to the wallet; the RPRC (Wallet-Relying Party Registration Certificate) specifies which data you're authorized to request, per declared use case.
A recent development worth knowing: the final regulation makes the RPRC optional. Without it, the wallet can query the national register directly (via a URL referenced in the RPAC) to check what a relying party is authorized to request: one less administrative burden for an integration that doesn't have dozens of distinct use cases to get certified.
You don't choose your country
A commonly misunderstood point: Article 5b of the implementing regulation requires registering in the member state where the company is legally established, not the one with the most advanced system. Once registered, however, recognition is supposed to work across the whole EU: each member state publishes its register in a harmonized way (electronically signed, machine-readable), and a common API lets any wallet verify an RPAC issued elsewhere. A single registration should therefore be enough, not one per target country.
The timeline
The Commission adopted the implementing regulation on relying party registration in May 2025. It applies from December 24, 2026: that's the date by which every member state must have an operational national register. Before that deadline, no country has any legal obligation to have anything in production, which explains why, as of today, no RPRC/RPAC register is yet legally active anywhere in the EU.
Who's where (July 2026)
| Country | Status |
|---|---|
| France | Public sandbox (France Identité), legal register not yet active |
| Germany | Public sandbox (SPRIND) open to testing even outside Germany, citizen rollout planned for early 2027 |
| Spain | Project announced, no public sandbox yet |
| Denmark | Ahead on citizen wallet rollout, RPRC/RPAC infrastructure still under construction |
France and Germany are part of the most advanced group at this stage, though neither has crossed the line of a legally operational register.
What this means in practice
As long as this register is active nowhere, a real, production wallet will refuse a request signed by an unregistered relying party, even one that's technically flawless. That's something we saw ourselves when testing against a real wallet: the request is fetched successfully, but no response is ever sent back. This isn't an integration bug, it's the current state of the ecosystem.
What remains possible, and useful, right now: building and testing your integration against test wallets and pilot environments (see our roadmap), so you're ready the day your own country's register opens, without having to redo the technical integration itself at that point.
Sources: implementing regulation on the registration of wallet-relying parties (European Commission, May 2025); ARF (Architecture and Reference Framework) documentation, "Relying Party Registration" section; deployment tracking by member state, eIDEasy (July 2026); public announcements from SPRIND (German sandbox) and France Identité.