KYC (Know Your Customer)
Prove who you are before the account opens — the document-heavy front door of regulated finance.
KYC (Know Your Customer) is the regulatory obligation on financial institutions — and a widening circle of fintechs, platforms, and gambling and crypto businesses — to verify who their customers are before and during the relationship: establishing identity, assessing risk, screening against sanctions and watchlists, and understanding enough about the customer (occupation, source of funds, expected activity) to recognize when something doesn't fit. It anchors the AML framework: transaction monitoring and suspicious-activity reporting presume the institution knows whose transactions it's watching.
Operationally, KYC is a document pipeline. Identity documents (passports, national IDs, licenses) get parsed, authenticated, and — in remote onboarding — paired with liveness-checked selfie matching; proof-of-address documents (utility bills, statements) get extracted and cross-checked; enhanced due diligence adds source-of-wealth documentation, and the whole file gets screened against sanctions, PEP, and adverse-media sources. Document AI transformed each step this glossary covers individually — ID parsing with MRZ validation, forgery and spoofing detection, cross-document consistency checks (the name, address, and dates agreeing across the pack), and completeness logic that chases gaps at intake rather than days later. The measurable effect is onboarding compressed from days to minutes for clean cases, with abandonment rates falling accordingly — while analyst attention concentrates on the flagged minority.
The compliance architecture around the automation is as important as the automation: risk-based tiers determining verification depth, human review on adverse and uncertain outcomes, audit trails recording what was checked and concluded per customer (the file the regulator examines), and periodic refresh plus event-driven re-verification, since KYC is a lifecycle, not a gate. And because KYC files concentrate the most sensitive identity data an institution holds, the processing architecture is itself a control — data residency, retention, access, and increasingly the requirement that the models reading passports run inside the institution's own perimeter.
Who really owns this company? — corporate identity verified through registries, documents, and ownership chains.
Follow the money — the regulatory regime that makes banks read mountains of documents to prove their customers' money is clean.
Passports, national IDs, residence permits — thousands of formats, one job: read and verify the identity.
Proof Perimeter runs document AI inside your own perimeter — with a provenance record on every field.
Book a demo