> For the complete documentation index, see [llms.txt](https://docs.lumia.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lumia.org/ecosystem/lumia/compliance/kyt-know-your-transaction.md).

# KYT Know Your Transaction

**Who this is for:** issuers and operators who need ongoing transaction-level monitoring after an asset is already issued and distributed, not just at onboarding.

## What it verifies

KYT screens individual transactions rather than the identity of the parties involved: for patterns consistent with sanctions evasion, money laundering, or other suspicious activity. Where [KYC](broken://pages/3f0c1814aaf218aab7cae0c1ceaf99d9e47049cb) and [KYB](broken://pages/1c404b728a0e4b865a04eb664c5ecb418bd2f6c8) are point-in-time checks on a person or entity, KYT is a recurring check applied to activity over time.

## Where it applies

KYT is most relevant during the ongoing life of an asset rather than at issuance: Lumia's RWA lifecycle names this the **Service** stage, at [`/tokenize/lifecycle/service`](file:///tokenize/lifecycle/Stage-4-Service.md), where transfers, distributions, and other servicing events continue after an asset is live. As with the other checks, KYT is enforced at the application layer, by monitoring logic the issuer or a screening provider builds, not by the base chain. Lumia integrates no transaction-monitoring provider and recommends none. Choosing a screening provider, and deciding what to screen for, is the issuer's call and the issuer's responsibility.