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 and KYB 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, 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.
Last updated
Was this helpful?