CONCEPT Cited by 1 source
Know Your Customer (KYC)¶
Definition¶
Know Your Customer (KYC) is the financial-services discipline of verifying customer identities, assessing risk profiles, and monitoring transactions for signs of money laundering, terrorist financing, fraud, or identity theft. Regulators require it; banks own the consequences of getting it wrong.
(Source: sources/2026-04-23-aws-modernizing-kyc-with-aws-serverless-solutions-and-agentic-ai.)
Four load-bearing functions¶
IBM + AWS enumerate KYC's job:
- Regulatory compliance with anti-money laundering (AML) and counter-terrorist financing (CTF) rules.
- Fraud prevention — detecting identity theft, forged documents, same-device / same-IP collision patterns.
- Risk management — profiling the customer, monitoring transactions for anomalies.
- Customer trust — transparency about what is verified.
Regulatory surface¶
KYC compliance is jurisdiction-specific. The post names five named frameworks as the working set:
| Jurisdiction | Framework |
|---|---|
| United States | Bank Secrecy Act (BSA); USA PATRIOT Act |
| European Union | Anti-Money Laundering Directives (AMLD) |
| Singapore | Monetary Authority of Singapore (MAS) |
| International | Financial Action Task Force (FATF) |
Banks operating across jurisdictions must satisfy all applicable frameworks per customer. This is why the KYC architecture uses context-aware retrieval to ground decisions in jurisdiction-matched regulatory guidance rather than a single global policy.
Why it's hard to do at scale¶
The post enumerates the legacy-KYC failure modes the agentic architecture is meant to solve:
- Batch, not real-time. Legacy systems process in batches; "instant onboarding [is] impossible".
- Manual validation across jurisdictions — inconsistent compliance because humans interpret the rules.
- No event-driven integration — legacy KYC can't absorb new fraud patterns without manual reconfiguration.
- Monolithic architecture — latency, availability, scalability bottlenecks coupled to the monolith.
- Product surface expansion: traditional banking + digital wallets + investment + crypto each bring different identity and risk requirements. Each adds to the KYC surface.
- Segment expansion: retail + SME + corporate each have different identity structures and risk profiles.
Canonical latency baseline¶
The post frames the KYC speedup in explicit numbers:
- Traditional KYC validation: 3–5 days for standard cases.
- Agentic architecture target: sub-5 minutes for standard cases, via parallel sub-agent execution (patterns/parallel-subagent-execution-for-latency).
This is the clearest wiki-disclosed before/after for KYC latency to date — though the after is a design target, not a measurement. (See caveat in the source page.)
Caveats¶
- Reference architecture, not field measurement. The 3–5-day baseline is generic legacy-KYC framing, not a specific institution's number.
- Human review is not eliminated. Even the sub-5-minute target applies to standard cases; the <75 %-confidence tail escalates to human review. The compliance-specialist workload shifts, it doesn't disappear.
- Jurisdictional detail is collapsed. The post lists five frameworks but doesn't detail how the Compliance sub-agent reconciles conflicts (e.g. EU data-residency vs US reporting requirements) — that's left as implementation detail.
Seen in¶
- sources/2026-04-23-aws-modernizing-kyc-with-aws-serverless-solutions-and-agentic-ai — canonical wiki introduction of KYC as an orchestration problem amenable to specialized sub-agent decomposition and systems/amazon-msk-backed event- driven infrastructure.