Does this satisfy AML customer due diligence?

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.

What about applicants without a wallet?

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.

Do we still store an identity document?

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.

Banking & fintech

KYC onboarding for banks and fintechs

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.

The problem

What teams do today

Document upload is where consumer banking signups go to die. The applicant photographs a passport, waits for OCR and liveness, then lands in manual review because of glare or a name spelled two ways. Every retry costs conversion. Every review costs an analyst. The vendor bills per attempt, not per success.

01: No capture, OCR or liveness retry loop in the signup path
02: Manual review becomes the exception instead of the default
03: A wallet from any member state verifies the same way

How it works

Three steps with Authbound

Step 01
Ask for the attributes
Your signup calls the Authbound API with the claim set your due diligence requires, and nothing else.
Step 02
The applicant approves
QR on desktop, deep link on mobile. They see exactly what is being asked before they consent.
Step 03
Get a signed result
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.

Rules in play

AMLD5 and AMLD6 customer due diligence, eIDAS 2.0

Live demo

We built Nordhaus, a company that does not exist, to show this running inside a finished product. The wallet flow in it is the real SDK.

Open the Nordhaus demo

Questions

What people ask

Does this satisfy AML customer due diligence?: 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.
What about applicants without a wallet?: 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.
Do we still store an identity document?: 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.

Built on Authbound Identity Verification. One API key covers every flow you add later.

Keep reading

Related use cases

iGaming

KYC onboarding for banks and fintechs

What teams do today

Three steps with Authbound

Ask for the attributes

The applicant approves

Get a signed result

What people ask

Related use cases

Age and identity verification for online gambling

Age verification for alcohol and restricted goods

Driving licence verification for rental and car sharing