Verify work authorisation and licences, then sign the contract, in one flow.
Today
With the EUDI Wallet
The wallet changes how the evidence is collected. The step at the end stays yours.
Why the wallet helps
Work authorisation and licences are attestations from bodies that already hold the record. Request them and you get verified status with validity dates attached, so an expired licence fails at verification rather than at audit. The contract is then signed with a qualified signature tied to the identity you just verified.
01
You request identity and supporting attestations
02
The user gets the request by QR or deep link
03
The wallet shows the data and the document
04
The user approves on their device
05
The wallet presents credentials and signs
06
Authbound verifies presentation and signature
07
Your backend receives the result and signed document
08
Your existing workflow continues
Step 01
Request the attestation and receive verified status with its validity period.
Step 02
For regulated roles, request the professional licence credential and validate it against the issuing body.
Step 03
The new hire signs with a qualified signature bound to the identity verified moments earlier.
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
National employment and right-to-work law, eIDAS 2.0, GDPR
Right-to-work and professional licensing rules are national, and so are retention periods for employee records. eIDAS 2.0 makes authority-issued attestations and qualified signatures available through the wallet. The employer’s duty to check and keep evidence stays with you.
Employee and contractor onboarding with right-to-work proof, licences, and wallet-based contract signing.
What it asks the wallet for
What the business gets back
Onward is a fictional company built by Authbound. The wallet integration in it uses the real Authbound SDK.
Where a member state issues residence or work permit attestations into the wallet, yes. Coverage varies by country and permit type, so keep the document route as a fallback.
Yes. Credentials carry validity periods and revocation status, so a scheduled recheck is an API call rather than another document chase.
A qualified signature has the legal effect of a handwritten one under eIDAS across the EU, which puts it ahead of most e-signature tools used for employment contracts today.
Yes. Verified results and signed contracts land in your HR system through the API and webhook, and your existing tools keep handling everything else.
Verified work authorisation and licence status with validity dates, the signed contract, and a verification ID for the employee file.
Use your current document process. The wallet makes the common case fast without removing the fallback.
Yes. Identity and attestations from any EU wallet are verified the same way.
The revocation check fails at verification, so the problem surfaces before the start date rather than at audit.
Wallet QES is free for non-professional use. An employee signing their own contract is generally treated as private use, but member state rules can differ.
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. Attestation coverage for licences and permits will grow country by country.
HR & hiring
Another wallet flow for HR & hiring.
Real estate
The same sign integration, applied to digital signatures.
B2B & procurement
The same sign integration, applied to business identity / KYB.
Built on Authbound Digital Signatures. 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.