Two ways to get relying party status

This page explains a choice every Nexiel client eventually faces: whether your own organization registers to verify EU Digital Identity Wallet credentials directly, or Nexiel registers and verifies on your behalf. It assumes no prior background in eIDAS 2.0 (the EU regulation governing digital identity) or EU Digital Identity Wallets. If wallet basics such as selective disclosure are new to you, read What is an EU Digital Identity Wallet? first, then come back here.

What a relying party is

Under eIDAS 2.0, any organization that asks someone to prove something from their EU Digital Identity Wallet is called a relying party. A bank running an identity check, a video platform confirming someone is over 18, and an employer checking a job candidate's diploma are all relying parties the moment they ask a wallet to disclose a claim.

An organization is not automatically allowed to make that request. eIDAS 2.0 requires a relying party to be registered with an authority in an EU member state before it can rely on what a wallet discloses. Nexiel running the technical verification on your behalf does not remove this requirement. Someone, either your organization or Nexiel acting for it, has to hold that registered standing.

Two ways to hold that standing

Nexiel registers as your relying party intermediary

The amended eIDAS Regulation allows a company like Nexiel to register once as a relying party intermediary, then act as the relying party for other organizations under that registration. Your organization still needs its own registration record, filed in its home EU member state, but Nexiel is the one filing it and operating the wallet verification.

This path means your organization never has to obtain its own relying party certificate or run wallet-verification infrastructure. It also means your ability to verify wallet credentials depends on Nexiel's own registration staying current in your country, and on Nexiel remaining your registered intermediary.

Your organization registers directly

Your organization applies to its own EU member state's registration authority, obtains its own relying party certificate, and is verified under its own name rather than Nexiel's.

This path gives your organization independent standing that does not depend on Nexiel's own registration. It also means your organization does the registration work itself, and does it again separately in every member state where it operates.

Where this stands today

As of now, no EU member state has a live, operational registrar for either path, an organization's own relying party registration or a registered intermediary such as Nexiel acting on an organization's behalf. Estonia is furthest along, with a target sometime in late 2026 or early 2027.

This gap is not specific to Nexiel. No organization anywhere in the EU can use either path in production today, because the registrar each path depends on has not launched in any member state yet. This page describes the choice ahead of you, not a decision you need to make now.

For what a wallet credential is and how selective disclosure works, see What is an EU Digital Identity Wallet? For how Nexiel Verify uses wallet-presented credentials today in sandbox mode, see the Verify API quickstart.