KYC, KYB and KYT: what each screens and why cross-border needs all three

KYC, KYB and KYT are the three screening disciplines that sit at the centre of anti-money-laundering and sanctions programmes for cross-border payments. They are often grouped together, but they answer different questions: Know Your Customer (KYC) verifies individuals, Know Your Business (KYB) verifies legal entities and their owners, and Know Your Transaction (KYT) examines the payments themselves. For institutions moving value across borders — and increasingly over stablecoin rails — understanding what each one covers, and what it misses on its own, is the difference between a defensible compliance posture and a fragmented one.

KYC — Know Your Customer: verifying the individual

Know Your Customer (KYC) is the process of confirming that a natural person is who they claim to be. It typically combines identity-document verification, proof of address, liveness or biometric checks, and screening against sanctions lists, politically exposed person (PEP) registers and adverse-media sources. KYC applies at onboarding and is refreshed periodically or when risk indicators change.

On its own, KYC establishes identity at a single point in time. It does not, by itself, reveal the corporate structures a person controls, nor does it observe how that person behaves once the relationship is live. A customer who passes KYC cleanly can still route illicit funds through accounts that were never re-examined. KYC is necessary, but it is the beginning of due diligence rather than the whole of it.

KYB — Know Your Business: verifying the entity and its owners

Know Your Business (KYB) extends due diligence to legal entities — companies, partnerships, trusts and other organisations. It verifies registration and good standing, maps the ownership structure, and identifies the ultimate beneficial owners (UBOs) and controlling parties so that the natural persons behind a corporate counterparty can themselves be screened. KYB applies when the customer is an institution rather than an individual, and is central to correspondent and business-to-business relationships.

KYB is where layered ownership and shell structures are meant to be unwound. Its limitation is similar to KYC’s: it confirms who controls an entity at onboarding, but it does not monitor the flows that pass through that entity afterwards. An entity can be entirely legitimate on paper and still be used to move funds in patterns that no static record would surface.

KYT — Know Your Transaction: monitoring the payments themselves

Know Your Transaction (KYT) shifts the focus from parties to payments. It analyses transactions — amounts, frequency, counterparties, geographies and, on blockchain rails, wallet exposure and on-chain provenance — to detect structuring, sanctions evasion, unusual velocity and links to high-risk or illicit addresses. KYT operates continuously, in or near real time, rather than at discrete onboarding moments.

What KYT cannot do is establish identity. It observes behaviour, but it relies on KYC and KYB to attach that behaviour to a verified person or entity. A transaction monitoring alert is far weaker if the institution cannot say with confidence who is on either side of the payment.

KYC and KYB tell you who you are dealing with; KYT tells you what they are actually doing. A programme that relies on any one of the three leaves a question the other two were designed to answer.

Why cross-border and stablecoin payments need KYC, KYB and KYT together

Cross-border payments combine multiple jurisdictions, multiple regulatory regimes and counterparties an institution may never deal with directly. Stablecoin settlement adds two further pressures: value moves in real time, and it moves on public ledgers where wallet activity is visible but identity is not. In this environment the three disciplines are complementary rather than interchangeable.

• KYC and KYB establish verified identity for the individuals and entities on each side of a payment, satisfying customer due diligence and supporting Travel Rule obligations.
• KYT links those verified identities to on-chain and off-chain transaction behaviour, screening wallets and flows for sanctions exposure and illicit-finance typologies.
• Together they let an institution attach originator and beneficiary information to a settlement and assess the risk of the payment itself — the combination that FATF guidance and Travel Rule expectations point toward for virtual-asset transfers.

Run in isolation, each leaves a gap. Identity checks without transaction monitoring miss behaviour that emerges after onboarding; transaction monitoring without verified identity cannot meet recordkeeping and Travel Rule requirements. Cross-border stablecoin flows expose those gaps faster than traditional rails because there is little settlement lag in which to catch them.

Operationalising KYC, KYB and KYT without slowing settlement

The practical challenge is sequencing these controls so they protect the institution without reintroducing the delays that real-time settlement is meant to remove. That means treating KYC and KYB as durable, reusable identity records rather than checks repeated at every payment, and embedding KYT inline so screening happens as the transaction is composed rather than in a batch afterwards.

• Resolve identity once at onboarding and reference it across subsequent payments, refreshing on a risk-based schedule.
• Screen sanctions, PEP and adverse-media data and wallet exposure inline, so a decision is available before settlement rather than after.
• Carry verified originator and beneficiary data with the payment message itself, in ISO 20022 (SWIFT MT/MX) structures, so compliance information travels with the settlement instruction.
• Maintain a single audit trail across all three controls, so investigators and examiners can reconstruct who was verified, what was screened and why a payment proceeded.

StableNet is built around this principle: it attaches Travel Rule, KYC, KYB, KYT and sanctions screening to stablecoin settlement and carries that compliance context inside ISO 20022 messaging, so institutions can apply all three disciplines as a single inline workflow rather than as separate steps bolted on around a payment.