Verify degrees against the awarding institution during the application.
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 degree issued as a verifiable credential is signed by the awarding institution and checks out instantly against that signature. The candidate presents it during application and you get an answer in the flow rather than a ticket in a queue. Transcripts, Erasmus records and language certificates behave the same way.
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
The candidate presents diploma, transcript or certificate credentials inside the application flow.
Step 02
We validate the issuer signature and revocation status, so a forged or withdrawn qualification fails immediately.
Step 03
Your ATS keeps a verified qualification and its evidence instead of an unverified line on a CV.
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 electronic attestations of attributes, GDPR
Diplomas issued as electronic attestations of attributes under eIDAS 2.0 carry the issuing institution’s signature. Recognition of a foreign qualification for a regulated profession is still a separate national decision. GDPR applies to everything you keep about candidates.
Employer-side diploma verification with instantly trusted academic credentials.
What it asks the wallet for
What the business gets back
Gradus is a fictional company built by Authbound. The wallet integration in it uses the real Authbound SDK.
Coverage grows as European universities issue under the European Digital Credentials for Learning framework and the eIDAS 2.0 attestation rules. Treat the wallet as the fast path and keep your existing background-check route for institutions that have not started.
Yes. Selective disclosure lets them prove they hold a specific degree without releasing the transcript, or prove a language level without the rest of it.
Only the qualification part. Criminal record checks, employment history and references stay separate.
Yes. Verify wallet-held diplomas instantly and keep your provider for institutions that do not issue digital credentials yet.
The verified qualification, such as degree, institution and award date, plus a verification ID. It can be stored against the candidate profile like any other check.
Use your current verification route. Coverage depends on which institutions issue digital credentials, and that grows over time.
The revocation check fails and the result says so. A forged or withdrawn qualification never shows as verified.
Yes. The institution’s signature is checked against the same trust framework wherever it was issued, which is where the time saving is largest.
No. It proves the degree is genuine. Professional recognition is a separate national process.
Now, for institutions already issuing digital credentials. Wallets themselves arrive by 24 December 2026, and institutional coverage follows.
HR & hiring
Another wallet flow for HR & hiring.
Banking & fintech
The same verify integration, applied to KYC.
iGaming
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.