One high-assurance patient login instead of one eID integration per country.
Today
With the EUDI Wallet
The wallet changes how the evidence is collected. The step at the end stays yours.
Why the wallet helps
The wallet is one high-assurance mechanism recognised across every member state. A single integration replaces the per-country stack and authenticates a patient from anywhere in the EU at the same level. Selective disclosure also means you can authenticate somebody without collecting attributes you have no clinical reason to hold.
01
You request specific attributes
02
The user gets the request by QR or deep link
03
The wallet shows exactly what is asked
04
The user approves on their device
05
The wallet presents the signed credential
06
Authbound verifies the presentation
07
Your backend receives a structured result
08
Your existing workflow continues
Step 01
Put it beside your existing national schemes and route holders through it.
Step 02
The patient approves in their wallet and you receive verified attributes bound to their device.
Step 03
Your session carries the verified subject, so record access rests on a high assurance identity.
Technical flow
const verification = await authbound.verifications.create({
policyId: 'pol_…', // the claims this flow requests
customerUserRef: user.id,
});
// Your webhook then receives verification.completed
// with the verified result and its audit record.Wallet presents
Terms to know
Regulatory context
eIDAS 2.0 high assurance level, GDPR Article 9 special category data
Access to health records requires high-assurance authentication, and eIDAS 2.0 places wallet authentication at level of assurance high. Health data is special category data under GDPR Article 9, so request only what the clinical purpose needs. Clinical consent and record access rules remain yours.
A telemedicine login surface that uses the EUDI Wallet instead of bank-ID sprawl.
What it asks the wallet for
What the business gets back
Tervion Etäklinikka is a fictional company built by Authbound. The wallet integration in it uses the real Authbound SDK.
eIDAS 2.0 places wallet authentication at the high assurance level, which is the tier national health services already require for record access. Device binding and holder consent are part of the protocol rather than bolted on afterwards.
Yes, and you should during the transition. Run wallet login as an extra option and move traffic across as coverage grows in each market.
Sector credentials such as a national insurance or health card number can be requested alongside identity attributes where the issuer supports them, so the login can carry the entitlement your clinical system needs.
A verified subject with the identity attributes you requested, bound to the patient’s device, plus a verification ID you can tie to the session.
They keep using your current login. Run the wallet as an extra option and move traffic over as coverage grows.
Yes. One integration accepts wallets from every member state at the same assurance level, which is the main reason to add it.
Match on the verified attributes you are allowed to use, or on a pseudonymous identifier where you do not need full identity.
Representation rules are national and only partly covered by wallets today. Keep your existing proxy process for those cases.
Every member state has to offer a wallet by 24 December 2026. Private services that are legally or contractually required to use strong user authentication have to accept it from December 2027 when the user asks. Health services that already require strong authentication fall inside that acceptance duty.
The login button, the session handling after a verified result, and your record access rules. The wallet protocol and trust checks sit with Authbound.
Banking & fintech
The same verify integration, applied to KYC.
iGaming
The same verify integration, applied to age verification.
E-commerce
The same verify integration, applied to age verification.
Built on Authbound Identity Verification. One API key covers every flow you add later.
Tell us what you are trying to build. We will map the user journey, the credentials and the wallet interaction to an implementation.