KYT vs KYC: What Runs Before a Payout Leaves

10 min read
Robert Romaniuk
KYT vs KYC: What Runs Before a Payout Leaves

A payout is held and the finance team asks the wrong question. They ask whether the payee “passed KYC,” when the thing that stopped the transfer was a score on a destination address the payee has used for eighteen months. KYT vs KYC is not a matter of terminology: the two controls examine different objects at different moments, and only one of them is built to re-run on every single transfer. This article sets out which control asks what, when each one runs, and what actually happens to a payout when one of them fires.

Four controls, four different questions

Most content on this topic lists the acronyms. The useful version states what each control interrogates, because that is what determines whether a clean payee can still produce a blocked payout.

ControlWhat it examinesWhen it runsWhat a failure blocks
KYB: know your businessThe paying company: registration, ownership, UBOs, source of funds, markets servedOnce, at onboarding, before any operational accessAccess to the platform itself, not one payment
KYC: know your customerA natural person’s identityAt onboarding of that person; on counterparties where the relationship requires itThat person’s access or that relationship
Sanctions and watch-list screeningA name and identity against restricted-party listsAt onboarding and, depending on the provider’s controls, again on transfersThe specific transfer, and usually the relationship
KYT: know your transactionThe destination address and its on-chain historyEvery transfer, individually, every timeThat single transfer

The two columns that matter are the third and the fourth. KYB and KYC are state; KYT is an event, and sanctions screening usually is too. A payee who cleared onboarding in March has a permanent KYC record and no permanent anything else. The address they gave you is re-scored on Friday against the lists and the chain as they stand on Friday.

What is the difference between KYC and KYT? KYC verifies the identity of a person or business once, at onboarding. KYT screens an individual transaction (in crypto payouts, the destination address and its transaction history) every time value moves. KYC tells you who your counterparty is. KYT tells you whether this particular transfer, to this particular address, is acceptable today.

KYB: the gate to the platform, not to a payment

At INXY, onboarding compliance is a prerequisite for operational access rather than a step inside any payment flow. Until it completes successfully, an organisation is not a product-ready client: it may have an account and be able to sign in, but it is not cleared for balances, payments, payouts, exchange or API integration. Access combines organisation status and user status, so an approved company can still have a user who cannot transact.

Part of onboarding is manual approval where automated data is not sufficient, so your go-live date has a human in it who is not on your project plan. And a stalled onboarding looks like a product problem rather than a compliance one, so the first question on a blocked launch is “what is our onboarding status”. The document list is in our walkthrough of what merchant verification involves.

KYC on your payees is frequently the provider’s obligation rather than yours, so get that split in writing. What is unambiguously yours is the accuracy of the beneficiary data you submit.

Sanctions and PEP screening: names, not addresses

Sanctions screening matches identity data against restricted-party lists. It is list-driven, it is name-driven, and it has a false-positive profile that address screening does not: common names, transliterations from non-Latin scripts, and partial date-of-birth matches all generate hits that resolve to nothing. A mature operation is measured by how fast it clears the noise.

Politically exposed person screening is a related but distinct control. A PEP is not a sanctioned party: the designation triggers enhanced due diligence rather than a prohibition, meaning senior management approval, establishing source of wealth and source of funds, and enhanced ongoing monitoring. In the EU that obligation sits today in Articles 20–23 of Directive (EU) 2015/849 as transposed nationally. From 10 July 2027 it moves into Articles 42–46 of Regulation (EU) 2024/1624, the AML Regulation, which applies from that date under Article 90(2) and treats crypto-asset service providers as obliged entities alongside banks. Firms building screening capability now are building against both: today’s national rules, and the single rulebook that replaces them.

INXY runs real-time KYT screening on the payout leg, with AML and Travel Rule controls built into the rail rather than bolted on, and is licensed across multiple jurisdictions and authorised as a crypto-asset service provider under MiCA. What none of that does is reduce your own obligations. A regulated provider runs the controls, it does not remove them, and no rail helps anyone bypass KYC, sanctions screening or reporting.

This article describes regulatory and market conditions for general information. It is not legal, tax, or financial advice. INXY Payments is a payment infrastructure provider, not a law or accountancy firm, and decisions with regulatory consequence should be reviewed by qualified counsel in the relevant jurisdiction.

KYT: the control that re-runs on every transfer

KYT scores the destination address. A risk provider returns a result based on the address and the company it keeps on-chain: proximity to sanctioned entities, mixers, known theft proceeds, high-risk venues.

Three things follow that matter operationally and are routinely missed.

A passed screen is not a permanent pass. An address that scored acceptable last month can score unacceptable this month because the chain changed, not because your payee did. This is the single most important sentence in this article for anyone building a payout schedule: there is no such thing as a pre-cleared address.

Address risk and identity risk are independent. Your payee can clear every name-based check and fail on the address they supplied, and the reverse. Both are blocking, and they are remediated by different people: one by your compliance function, one by asking the payee for a different address.

Chain and network choice change the risk surface. The same beneficiary on a different network is, to a screening engine, a different address with a different history.

What actually happens when a payout is held

Here is the part that decides how you staff a payout Friday. In INXY’s outbound flow a payout is created as a request, not as a send: nothing is on-chain while the checks run. The order, as it applies to every recipient in an INXY mass crypto payout:

  1. Pre-send validation. Early checks run before the withdrawal flow starts. A failure stops the operation, returns an error, and no transaction is formed.
  2. Screening of the destination. The recipient address is checked against blacklists and screened by KYT at the moment of the payout, on current data. A previous result is never treated as a clearance. A high-risk result fails the request.
  3. Travel Rule message exchange. Only after screening has passed is originator and beneficiary information exchanged with the counterparty provider where one exists. The field-level detail is in what the Travel Rule actually requires on a payout.
  4. The transaction is created and sent.

Alongside that sequence sits a separate control: the contact list. A recipient does not have to be in it for a payout to start, but a recipient who is in it with a declined status will not be paid, whatever the screening result. It is the control a finance team uses to keep a vetted payee set for recurring and mass runs.

Screen first, then transmit, then send. A provider that exchanges Travel Rule data before screening has told you something about its architecture. And note that even an address you have paid many times is screened again: the “no pre-cleared address” principle, built into the flow.

The distinction nobody explains: an early gate is not a case

On the INXY outbound path, a negative outcome is an early gating outcome: the request fails checks, no transaction is created, and the client receives an error. That is a different event from a compliance case opened on a transaction that already exists, where the transfer sits in a review state while someone decides.

Why you should care: the two shapes have opposite costs.

  • Early gate, hard error. Nothing to unwind, no funds in limbo, your integration learns immediately. The cost is that a false positive gives you an error code rather than a case to escalate, so remediation lives in your process, not the provider’s queue.
  • Case on a live transaction. You get a review path inside the transfer. The cost is that value is already committed, the payee is already waiting, and you are explaining a pending state to someone who was promised Friday.

Ask which one you are buying before your first large run, not during it.

The regulatory backdrop, cited to the instrument

  • FATF. The Travel Rule reaches virtual-asset transfers through the Interpretive Note to Recommendation 15, paragraph 7(b), which permits jurisdictions a USD/EUR 1,000 de minimis threshold. Separately, Recommendation 16 itself was revised at the FATF June 2025 Plenary, clarifying who in the payment chain is responsible for information in payment messages and standardising the information that accompanies peer-to-peer cross-border payments above USD/EUR 1,000; for the originator, that includes name, address and date of birth. FATF states the changes “will come into effect by the end of 2030” (FATF, 18 June 2025); implementation guidance went to public consultation in June 2026. The announcement does not say how the revision carries through to virtual-asset transfers, so treat it as direction of travel, not a new crypto obligation.
  • EU. Regulation (EU) 2023/1113 has applied since 30 December 2024 and has no de minimis threshold: Recital 30 states that transfers of crypto-assets “should be subject to the same requirements regardless of their amount”. For a transfer exceeding EUR 1,000 to a self-hosted address, the originator’s provider must also assess whether that address is owned or controlled by the originator (Article 14(5), second subparagraph). EBA guidelines EBA/GL/2024/11 set out how providers detect and handle transfers with missing or incomplete information. Regulation (EU) 2023/1114 (MiCA) governs authorisation of crypto-asset service providers.
  • EU AML package. Regulation (EU) 2024/1624 entered into force in 2024 and applies from 10 July 2027 (Article 90(2)).

Confirm the current position in your own jurisdiction with counsel.

What breaks in production

Name mismatch and transliteration. Legal name versus trading name, or a different transliteration from a non-Latin script. The most common single cause of a hold: a data-quality problem dressed up as a compliance one, preventable by capturing the name as the beneficiary’s own provider holds it.

A past pass used as a control. Someone builds a “pre-approved address” list from last quarter’s successful payouts and treats it as a screening bypass. It is not one, and the first re-score proves it.

Self-hosted address attestations collected at payout time. If address-control verification is requested when the batch runs rather than when the payee is onboarded, you discover it mid-cycle.

A declined contact nobody remembers declining. A payee marked declined in the contact list blocks silently from the payer’s point of view, because the error does not say “someone on your team did this in March.” Audit that list before a large run.

Treating a screening error as a transient failure and retrying. A request that failed screening will fail again. Retry logic that does not distinguish a compliance rejection from a network timeout generates noise and, on a non-idempotent integration, risk.

Assuming a vertical changes the controls. It does not. High-risk vertical is an underwriting and settlement question, not a screening-optional one: the framing we use in compliance for fintechs offering stablecoins.

Decision framework

1. Do you send, or only receive? Acceptance is the easier half. On a payout you are the originator, which is where sanctions screening, address risk and transfer-information requirements bite. If you will ever send, test the payout leg during evaluation.

2. Where are your beneficiaries? Your corridor list, not your own jurisdiction, determines how much counterparty variation you will meet.

3. Which failure shape do you want? Early hard gate, or case on a live transaction. Decide deliberately, and build the matching internal process.

4. Do you want to own the screening stack? If not, require validation, blacklist, KYT, contact-list and Travel Rule exchange inside the payout flow, exposed through API and webhooks so a mass run applies them per recipient. That is the model behind INXY mass crypto payouts; the asset-level detail starts with USDC mass payouts.

Where a payment rail is not the answer. If your own licence or auditor requires a case-management record for every decision (analyst queues, documented dispositions, sign-off on each override, an audit file per case), that record belongs to your compliance function. You will need compliance tooling of your own alongside any payment provider: a rail runs the controls on the transfer, it does not replace your compliance desk. If your screening question is about this quarter’s payout corridors instead, talk to a payments specialist with your payee list and corridor split.

FAQ

What is the difference between KYC and KYT?

KYC verifies the identity of a person or business once, at onboarding. KYT screens an individual transaction (for crypto payouts, the destination address and its on-chain history) every time value moves. KYC tells you who your counterparty is; KYT tells you whether this specific transfer is acceptable today.

Is KYB the same as KYC?

No. KYB verifies a business: registration, ownership, beneficial owners, source of funds and the markets it serves. KYC verifies a natural person. At INXY, KYB is onboarding compliance and a prerequisite for operational access to the platform, separate from the checks that run on any individual transaction.

Why was my payout blocked when the payee passed KYC?

Because identity screening and address screening are independent. The payee can clear every name-based check and the destination address can still fail a KYT risk score or a blacklist match. Both are blocking, and they are fixed by different actions: one by compliance review, one by obtaining a different address.

Does the Travel Rule run before or after screening?

After, on a well-ordered rail. INXY exchanges Travel Rule information only once pre-send validation and address screening have passed. A provider that transmits originator and beneficiary data before screening the transfer has sequenced its controls in a way worth asking about.

Do PEP matches block a payment?

Not automatically. A politically exposed person is not a sanctioned party: the designation triggers enhanced due diligence rather than a prohibition. Sanctions matches are the blocking category. Treat the two as different workflows with different outcomes.

Does using a regulated provider reduce my AML obligations?

No. It moves the operational work (screening, list maintenance, message exchange, recordkeeping) to a provider built for it. Your obligations remain yours, including supplying accurate beneficiary data and keeping it current. No provider helps anyone bypass KYC, sanctions screening or reporting.

Important notice for UK visitors

This website and its content have been produced and disseminated for persons outside of the United Kingdom. The information provided is not directed at or intended for distribution to, or use by, any person or entity located within the UK. The financial products and services mentioned on this website are not eligible for the UK. Cryptoassets are classified as Restricted Mass Market Investments in the UK, meaning that they are high-risk investments and are not suitable for most retail investors. We expressly disclaim any responsibility or liability for any access to or use of this website by any person located within the UK.