KYC/AML
Know-your-customer and anti-money-laundering checks, the regulated-industry use case Lumen Sovereign targets.
Last refreshed: 15 June 2026 · Appears in 1 active topic
Why can a bank not run KYC checks through a US hyperscaler's API?
Timeline for KYC/AML
Cosine builds Britain's sovereign AI model
UK Startups and Innovation- Why can banks not use US cloud AI for KYC checks?
- UK GDPR, FCA operational resilience rules, and the Money Laundering Regulations create compliance risk when sensitive KYC data is routed to non-UK infrastructure without adequate jurisdictional safeguards. Sovereign on-premises AI is designed to close this gap.Source: FCA Handbook / UK GDPR
- What is the difference between KYC and AML compliance?
- KYC verifies a customer's legal identity before account opening; AML screens ongoing transactions for money-laundering or terrorist-financing patterns. Both are required by the Money Laundering Regulations 2017 and FATF recommendations.Source: FATF / Money Laundering Regulations 2017
- What regulated datasets does Cosine's Lumen Sovereign train on?
- Lumen Sovereign trains on more than 30 regulated datasets covering KYC/AML checks, cybersecurity, clinical-trial coordination, and legal review, running entirely on UK sovereign compute with no external data transfer.Source: Lowdown
- Which UK law governs anti-money-laundering obligations?
- The principal statute is the Proceeds of Crime Act 2002. Day-to-day obligations flow from the Money Laundering, Terrorist Financing and Transfer of Funds (Information on the Payer) Regulations 2017 and FCA rules in SYSC 6.3.Source: Proceeds of Crime Act 2002 / MLRs 2017
Background
KYC (know your customer) and AML (anti-money-laundering) are the two pillars of regulated-industry compliance in financial services. A KYC check verifies the legal identity of a customer before a bank, insurer, or broker opens an account; AML controls screen ongoing transactions for patterns associated with money laundering or terrorist financing. Together they are mandated by the Financial Action Task Force (FATF) recommendations, the UK's Proceeds of Crime Act 2002, the Money Laundering Regulations 2017 and their post-Brexit successors. Banks that fail them face regulatory censure and fines of hundreds of millions of pounds.
The data involved is acutely sensitive: passport scans, transaction histories, beneficial-ownership records and politically-exposed-person flags. UK regulators and their legal teams hold that routing this data to a non-UK cloud infrastructure without adequate contractual and jurisdictional safeguards carries material compliance risk under the UK GDPR and the FCA's operational resilience rules. That constraint is precisely the market Cosine's Lumen Sovereign model is targeting: it trains on 30-plus regulated datasets covering KYC/AML, cybersecurity and clinical trials, runs entirely on-premises on UK sovereign compute, and transfers no data externally .
The commercial case rests on the gap between what large-language-model inference can do for KYC throughput and what a compliance team can actually route through an offshore API. Sovereign on-premises AI closes that gap, making KYC/AML the anchor use case for the entire UK sovereign-AI stack.