Replace document upload with identity attributes signed by the issuing 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 wallet already holds identity attributes signed by the issuing member state. You ask for the ones your due diligence actually needs and get them back as structured data. No image to grade, no OCR to fail, no transliteration argument.
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
Your signup calls the Authbound API with the claim set your due diligence requires, and nothing else.
Step 02
QR on desktop, deep link on mobile. They see exactly what is being asked before they consent.
Step 03
We check the issuer against the EU trust list, check revocation, confirm device binding, and hand your backend a verified result with an audit record.
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
AMLD5 and AMLD6 customer due diligence, eIDAS 2.0
Banks and payment service providers are named relying parties under eIDAS 2.0 Article 5f and must accept the wallet for identification from December 2027. AML customer due diligence still applies in full: the wallet changes how identity is evidenced, not your obligation to assess risk, screen sanctions and PEPs, and monitor the relationship. Before going live you also register as a relying party and declare which attributes you request and why.
A neobank signup that turns KYC into a 30-second wallet step.
What it asks the wallet for
What the business gets back
Nordhaus is a fictional company built by Authbound. The wallet integration in it uses the real Authbound SDK.
eIDAS 2.0 puts wallet presentations at the high assurance level, which is what AML regimes accept for remote onboarding. You still run your own risk scoring, sanctions and PEP screening. The wallet replaces identity proofing, not your AML program.
Keep your current provider as the fallback and route wallet holders to the faster path. We return a clean unsupported result you can branch on rather than failing the session.
There is no document to store. You keep the attributes you are required to retain plus the signed verification record, which is a much smaller thing to protect than a passport scan sitting in a bucket for five years.
Yes. Authbound adds the wallet path next to it rather than replacing it. Most teams offer the wallet first and keep the document flow for applicants who do not have one yet.
A verification.completed webhook with the attributes your policy requested, such as name, date of birth, nationality and address, plus the verification ID and your own customer reference. A failed check arrives as verification.failed with a failure code.
No. Resident address is an optional attribute in the PID, and not every member state includes it. Keep a proof-of-address fallback for applicants whose PID does not carry one.
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. For banks the trigger is already met, because they require strong authentication today.
Yes. Every certified wallet presents over the same protocol and is checked against the same EU trust lists, so a Spanish applicant at a Finnish bank is not a separate integration.
The verification ends as failed with a reason such as an untrusted issuer or a revoked credential. Nothing is half-onboarded. You route the applicant to your existing method.
Yes. Relying parties register in their member state and declare the purpose and the attributes they request, and the wallet shows that registration to the user. Keep your Authbound policy aligned with what you declared.
A wallet button or QR step in signup, a webhook handler, and the onboarding logic that runs on the result. The protocol, trust list and revocation work sits with Authbound.
iGaming
The same verify integration, applied to age verification.
E-commerce
The same verify integration, applied to age verification.
Mobility
The same verify integration, applied to licence 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.