Reusable KYC: Verify Once, Share Proof Not Raw Data

The average fintech customer completes identity verification three to five times across the services they use. Each onboarding collects the same passport scan, the same selfie, the same proof of address, and each creates another copy of that data sitting in another vendor's store. Reusable KYC proposes a different model: verify once, then share a cryptographic proof of that result with the next relying party, without re-transmitting the underlying documents.

What Reusable KYC Actually Moves

The term covers several architectures that are easy to conflate. In practice they differ on one question: what crosses the wire between providers?

• Attestation sharing. The original verifier issues a signed statement — "this subject passed document and liveness checks on 2024-03-11 at assurance level X" — and the relying party trusts the signature rather than re-running the check.
• Attribute sharing. Specific verified fields (full name, date of birth, nationality) are passed, but not the source images.
• Full dossier transfer. The complete document set is forwarded. This is the least private and, despite the "reusable" label, mostly just relocates the copy problem.

The privacy gain is largest with attestation sharing, where the relying party receives a verifiable claim and never touches the identity documents at all. Selective disclosure — proving you are over 18 without revealing a birth date, or proving residency in a jurisdiction without an address — sits at the same end of the spectrum.

Why Regulators Don't Let You Skip Your Own Diligence

Reliance on third-party verification is permitted under several frameworks, but it is conditional, not automatic. Under the EU's AML Directives and the FATF reliance provisions, the relying institution generally remains responsible for the adequacy of the customer due diligence even when it leans on another party's work. That typically means you must be able to obtain the underlying records on request, satisfy yourself the original verification met your standard, and document the arrangement.

Two practical consequences follow. First, an attestation that omits the method and assurance level is often useless for audit — "verified" with no detail cannot be defended to an examiner. Second, a stale attestation carries stale risk: an identity confirmed two years ago says nothing about sanctions or PEP status today. Reusable KYC speeds onboarding; it does not retire ongoing monitoring. This is general information, not legal advice — confirm reliance rules with counsel for your specific jurisdictions.

The Consent and Linkage Problem

Moving a verified identity between parties creates a new surveillance surface. If every relying party can resolve attestations back to a single persistent identifier, the scheme quietly builds a map of which services a person uses — a privacy harm the original verification never created. Good designs break that linkage with per-relying-party pseudonyms and pairwise identifiers, so two providers holding attestations about the same person cannot correlate them.

Consent also has to be granular and revocable. The subject should see which attributes are being shared, with whom, and for what purpose, and be able to decline sharing a birth date when a simple age-over threshold would satisfy the requirement. Bundled, all-or-nothing consent defeats the data-minimization rationale that makes reusable KYC worth doing.

Designing for Reuse Without Hoarding

A chat-based verification flow fits this model cleanly. The verification happens in a conversation the customer already trusts, the result is reduced to a signed attestation, and the images that produced it can be discarded once the proof is issued. A few principles hold the design together:

• Minimize at the source. Capture only the fields needed, derive the attestation, and apply configurable retention so documents expire rather than accumulate.
• Attest the method, not just the outcome. Record assurance level, check types, and timestamp so a relying party can judge fitness for its own risk appetite.
• Make proofs expirable. Tie validity windows to risk, and trigger re-verification on events rather than treating one pass as permanent.
• Separate identity proof from ongoing screening. Reuse the identity check; keep running your own sanctions, PEP, and adverse-media monitoring.

Done well, reusable KYC cuts onboarding friction and the number of document copies in circulation at the same time — a rare case where the privacy-preserving option is also the faster one.