Reusable KYC

The Problem

Every financial institution demands the same information:

• Proof of identity - Government-issued ID, utility bill, selfie verification
• Source of funds - Bank statements, employment verification, tax returns
• Risk assessment - Credit check, sanctions screening, PEP (Politically Exposed Person) status

When a customer interacts with multiple institutions—a bank, an insurer, a crypto exchange, a wealth manager—they upload the same documents over and over. Each institution performs redundant verification. The customer waits days. The institution spends $80-$200 per KYC check.

This isn’t a future problem. Banks collectively spend over $500 million annually on redundant KYC verification for customers who’ve already been verified elsewhere. Customers abandon applications: 40% of users drop off during lengthy KYC processes (Signicat, 2025).

Why It Matters Now

Regulators are pushing reusable digital identity:

• MAS TechRisk (Singapore Monetary Authority, 2027): Mandates support for reusable digital identity credentials in financial services
• eIDAS 2.0 (EU, 2027): Requires member states to accept verifiable identity credentials across borders
• UK Digital Identity and Attributes Trust Framework (2026): Sets standards for reusable identity credentials

The infrastructure is converging: W3C Verifiable Credentials, selective disclosure via zero-knowledge proofs, real-time trust registries. The institutions that adopt reusable KYC first will win on customer experience and operational cost.

---

How Affinidi Enables Reusable KYC

The key shift: Instead of each institution maintaining a private KYC database, customers hold cryptographically signed credentials in their own wallets. When they apply to a new institution, they present the credential. The institution verifies:

1. Who issued it - Is the issuer a trusted KYC provider?
2. Is it still valid - Has it been revoked or expired?
3. Does it match this person - Cryptographic binding to the customer’s identity

All of this happens in seconds, with no document upload, no manual review, no redundant verification.

Technical Foundation

• Elements Services issue W3C Verifiable Credentials containing KYC data (name, address, verified date, risk tier)
• Affinidi Vault stores credentials on the customer’s device—private keys never leave the secure enclave
• BBS+ Selective Disclosure lets customers reveal only what’s needed (e.g., “I’m over 18” without revealing exact birthdate)
• Trust Registry (TRQP) lets verifiers query in real-time: “Is this issuer authorized to perform KYC?” and “Is this credential still valid?”
• did:webvh identifiers bind credentials to the customer cryptographically—tamper-evident, time-travelable

Example Flow

Customer verified by Bank A
  ↓
[Bank A issues KYC credential via Elements Services]
  ↓
Customer stores credential in Affinidi Vault
  ↓
Customer applies to Insurance Company B
  ↓
[Insurance Company B requests: "Prove you're KYC'd"]
  ↓
Customer presents credential with selective disclosure
  ↓
[Insurance Company B verifies:]
  1. Signature valid? ✓
  2. Issuer trusted? (TRQP query) ✓
  3. Not revoked? (TRQP query) ✓
  ↓
Insurance application proceeds immediately

What this means:

• Customer uploads documents once (to Bank A)
• Bank A performs verification once
• Insurance Company B trusts Bank A’s verification without seeing raw documents
• Customer controls what’s shared (e.g., verify age without revealing birthdate)
• Both institutions have audit-ready proof of who verified what, when

---

Real-World Applications

Banking: Multi-Institution Customer Journeys

Problem: Customer opens checking account at Bank A (full KYC: 3-5 days). Six months later, applies for mortgage at Bank B—starts from zero.

Solution: Bank A issues KYC credential. When customer applies to Bank B, they present it. Bank B queries Trust Registry: “Is Bank A authorized to issue KYC credentials?” (yes), “Is this credential still valid?” (yes). Bank B accepts it.

Outcome:

• Mortgage application approved same-day instead of re-starting KYC
• Bank B saves $120 per verification (no duplicate ID checks, no manual review)
• Customer experience improves: no document re-upload, no waiting

---

Insurance: Cross-Carrier Underwriting

Problem: Policyholder verified by auto insurer (full KYC for premium calculation). Now applies for life insurance at different carrier—carrier demands fresh KYC documentation despite identical identity.

Solution: Auto insurer issues KYC credential with BBS+ selective disclosure. Life insurer requests only: “Proof of identity + age + address” (not driving history, not auto claims). Customer presents credential with only those fields revealed.

Outcome:

• Life insurance underwriting starts immediately with trusted identity
• Auto insurer’s sensitive data (claims history) stays private
• Regulatory compliance maintained: life insurer has audit trail of KYC source

---

Crypto Exchange: Borderless KYC

Problem: User completes KYC on Exchange A (uploads passport, selfie, address proof). Wants to trade on Exchange B—Exchange B doesn’t trust Exchange A’s records and demands full re-verification.

Solution: Exchange A issues KYC credential. User presents it to Exchange B. Exchange B verifies:

1. Issuer signature (cryptographic proof it’s from Exchange A)
2. Issuer authorization via TRQP (is Exchange A a licensed KYC provider?)
3. Credential status via TRQP (not revoked, not expired)

Outcome:

• User trades within minutes instead of waiting days for re-KYC
• Exchange B reduces KYC backlog by 70%—most users already verified elsewhere
• Both exchanges comply with FATF Travel Rule: cryptographic proof of customer identity

---

Wealth Management: High-Net-Worth Mobility

Problem: High-net-worth client moves between wealth advisors (consolidating accounts, switching strategies). Each advisor demands fresh KYC documentation—passport copies, bank statements, tax returns—despite client already verified by previous advisor.

Solution: Initial advisor issues KYC credential with comprehensive verification. When client switches advisors, they present credential with selective disclosure:

• New advisor requests: “Accredited investor status + proof of identity”
• Client reveals only those fields (not net worth details, not account history)

Outcome:

• Client switches advisors without document chase (no faxed forms, no re-scanning IDs)
• New advisor trusts cryptographic proof from previous advisor
• Client maintains privacy: only minimum necessary data revealed

---

Why Affinidi

	Affinidi Reusable KYC	Manual KYC	Centralized Utilities	Blockchain Registries
Customer owns data	✓ Vault on device	✗ Institution controls	✗ Utility controls	✗ On-chain = public
Selective disclosure	✓ BBS+ ZK proofs	✗ All or nothing	✗ All or nothing	✗ All data on-chain
Real-time revocation	✓ TRQP queries	✗ Manual checks	⚠ Batch updates	⚠ Chain bloat
No central registry	✓ Peer-to-peer	N/A	✗ Single point failure	✗ Chain as registry
Regulatory alignment	✓ MAS, eIDAS 2.0	⚠ Per jurisdiction	⚠ Region-locked	✗ Non-standard

What this means:

• Manual KYC repeats the same verification for every institution—waste of time and money
• Centralized utilities (e.g., identity bureaus) create single points of failure and don’t support selective disclosure
• Blockchain registries put KYC data on-chain (privacy nightmare) or use smart contracts (can’t handle selective disclosure without ZK infrastructure)

Affinidi provides user-owned credentials + selective disclosure + real-time trust verification—the only architecture that scales across institutions without compromising privacy or creating central honeypots.

Proof It Works

• W3C Verifiable Credentials - Industry-standard credential format
• BBS+ Selective Disclosure - Production-ready zero-knowledge proofs (no custom crypto)
• TRQP Integration - Real-time trust queries for issuer validation and revocation checks
• Self-hostable - Deploy trust infrastructure on your own servers, not ours

---

Get Started

For Developers

Build your first reusable KYC flow

Issue a KYC credential, store it in Affinidi Vault, present it to a verifier—end-to-end in under an hour.

Start building →

---

For Compliance Teams

See a live demo of reusable KYC

Walk through a customer journey: verify once at Bank A, apply to Insurance Company B, credential verified in seconds.

Schedule demo →

---

For Enterprises

Custom deployment consultation

Integrate reusable KYC into your existing onboarding flows, connect to your KYC providers, configure trust registries.

Talk to an expert →

---

Related Resources

Technical Deep Dives

• Verifiable Credentials - How cryptographically signed credentials work
• Zero-Knowledge Proofs - BBS+ selective disclosure explained
• Trust Registries & TRQP - Real-time issuer validation

Related Solutions

• Cross-Org Agent Trust - How agents prove identity across institutions
• Passwordless Authentication - Verifiable credentials for login flows

Case Studies

(Coming soon: Bank implementation of reusable KYC)