Every compliance team knows the numbers by heart: document-based KYC costs somewhere between 3 and 25 euros per verified customer depending on the vendor and the fallback-to-manual-review rate, and it loses between 20% and 40% of applicants before they finish. The EUDI Wallet does not tweak this process — it replaces its foundation. Instead of asking a user to photograph a passport and record a liveness video that a model then tries to match, you ask their wallet for a signed Person Identification Data (PID) attestation that a government already issued and cryptographically vouches for.
Why document scans are structurally expensive
The cost of document-based onboarding is not the OCR call — it's everything around it:
- Manual review queues for low-confidence liveness scores, blurry uploads, and edge-case documents.
- Re-verification when a user fails the first attempt, which is common on older phones and in poor lighting.
- Ongoing model retraining as document templates change across 27 Member States plus third countries.
- Fraud losses from synthetic identities and high-quality forged or stolen documents that pass automated checks.
None of these costs disappear with a better vendor. They are inherent to verifying a physical document with a camera. A signed PID attestation removes the entire category: the wallet already did the liveness and identity-proofing work once, at issuance, under government supervision.
What changes for drop-off
Abandonment during document capture peaks at exactly the steps users find intrusive: uploading an ID photo, granting camera access for a selfie video, and waiting for a review decision that sometimes takes minutes or hours. Wallet-based presentation collapses this into a single consent screen: the user sees which attributes are requested, taps approve, and the attestation is returned in seconds. Early pilots across EU digital identity wallet large-scale trials report presentation completion times under 30 seconds for a PID share, against multi-minute median times for document + liveness flows.
Fraud reduction is structural, not incremental
A forged passport image can fool a document-verification model that has never seen that particular template. A forged wallet attestation cannot exist without either compromising a government issuer's signing key or cloning the wallet's device-bound private key — both several orders of magnitude harder than producing a convincing fake PDF or printed document. Synthetic identity fraud, which relies on assembling plausible-but-fake documents, loses its raw material entirely: there is no PID attestation for a person who does not exist in a national population register.
Document-based KYC verifies that a document looks real. Wallet-based KYC verifies that a government-issued signature is valid. Those are different problems, and the second one is much harder to fake.
Where this fits AMLD and CDD obligations
Customer due diligence rules do not ask for a specific verification technology — they ask for reliable, independent sources of identity data. A government-issued, cryptographically signed PID attestation, verified against the EU Trust List, is at least as strong an evidentiary basis as a certified copy of a passport, and considerably stronger than an unsupervised remote document scan. Obliged entities under the anti-money laundering framework should treat wallet-based identification as satisfying, not merely supplementing, standard CDD identity-verification requirements, while keeping the usual risk-based approach for enhanced due diligence cases such as PEPs or high-risk jurisdictions.
A realistic migration plan
- Keep your existing document-based flow live as a fallback for users without a wallet yet — adoption will be gradual through 2026 and 2027.
- Add wallet presentation as the first-offered path at the identity-verification step, not a buried alternative.
- Request only the PID attributes your CDD obligation actually needs — name, date of birth, and a national identifier are usually sufficient at onboarding.
- Route wallet-verified customers straight past manual review; route document-based customers through your existing risk engine unchanged.
- Instrument both paths separately so you can measure completion rate, cost per verified customer, and false-positive fraud flags, and use that data to justify sunsetting the document path per segment.
The integration reality
Accepting a wallet credential requires registering as a Relying Party, obtaining and rotating access certificates, and staying conformant as the Architecture and Reference Framework evolves — separately in every Member State whose wallet you want to accept. Most compliance and engineering teams do not want to run that as a permanent function alongside their actual product. Arkadiz operates as the intermediary Relying Party: you integrate once against a single API, and Arkadiz carries registration, certificate lifecycle and multi-wallet conformance across the EU, so your onboarding team ships a faster, cheaper KYC flow instead of a standing regulatory programme.
What to measure before and after
- Cost per successfully onboarded customer, split by verification path.
- Time-to-decision from start of identity verification to account activation.
- Manual review rate and average review turnaround time.
- Confirmed fraud incidents per 10,000 onboardings, by verification path.
Institutions that track these four numbers consistently find that wallet-based onboarding pays for its integration cost within the first few thousand verified customers, purely from reduced manual review and lower abandonment — before counting the fraud-loss avoidance at all.