Check licence categories and expiry as data, the same way for every member state.
Today
With the EUDI Wallet
The wallet changes how the evidence is collected. The step at the end stays yours.
Why the wallet helps
A mobile driving licence is signed by the licensing authority. Request it and the categories, expiry and issuing country come back as structured fields you compare in code instead of by eye. Same check for every member state.
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
Run it during reservation so a wrong-category or expired licence surfaces before the customer drives to the depot.
Step 02
Categories, expiry and issuing country arrive as data, alongside holder identity if your terms need it.
Step 03
Your booking engine compares the returned categories against the vehicle and blocks or upsells without an agent involved.
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
ISO/IEC 18013-5 mDL, eIDAS 2.0, national road traffic law
Licence validity and categories are defined by national road traffic law and the EU driving licence directive. The mobile driving licence follows ISO/IEC 18013-5 and is one of the credentials eIDAS 2.0 wallets carry. Insurance terms, age surcharges and deposit rules remain yours to apply.
Cross-border car rental with instant EUDI driving licence verification.
What it asks the wallet for
What the business gets back
Roamline is a fictional company built by Authbound. The wallet integration in it uses the real Authbound SDK.
An mDL is issued and signed by the licensing authority under ISO/IEC 18013-5. A photo is an image you have to trust. An mDL is data you verify against a signature and a revocation list.
Yes, and that is most of the point. The verification path and trust list are identical regardless of issuing state, so cross-border rentals stop being a special case.
You keep the verified fields and the signed record your terms and insurer require. There is no image to retain, which removes a familiar retention headache.
Yes. Customers with a mobile driving licence take the fast path, and everyone else goes through your current counter or upload process.
The licence categories, expiry date and issuing country as structured fields, and holder identity if your terms need it. The verification ID and your booking reference come with it.
The revised EU driving licence directive makes the digital licence the default format, with national rollout over the next few years. Some member states already issue it into the wallet, so coverage will be uneven for a while.
The revocation check fails and you get a failed result with a reason. The booking can stop there instead of at the counter.
Yes. The customer scans a QR code on a screen or tablet at the desk, so the same check works online and in person.
Yes. Request age_over attributes or birth date from the PID alongside the licence, depending on what your pricing needs.
Only if their licence is issued as a compatible mDL and trusted. Otherwise they use your existing process.
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.