Crypto KYT evidence layer for exchanges and OTC desks
For exchanges that already have a screening vendor and still cannot reproduce last year's decisions. Your vendor gives you a score today. Your supervisor asks what a decision from eighteen months ago was based on, under the policy you had then.
What KYTGate does not try to do
KYTGate will not out-label Chainalysis, Elliptic or TRM, and its pricing page says so. Naming the owner of an address is a fifteen-year data business with law-enforcement sources behind it. A label we invented would look the same as one we had verified, so there are none. If attribution is what you need, you already buy it.
What that purchase does not give you is what an examiner asks for: a reconstruction of the decision. That means the inputs, the list version, the policy and the decision, as they stood on that date. Vendor scores move. An address labelled medium risk in March can be high risk in September because the vendor learned something. If your record shows today's score next to last year's decision, a reviewer may read it as a decision that was never really made.
Bring your own vendor key
Connect your existing Chainalysis or Elliptic licence with your own API key. The key is sealed with AES-256-GCM and can never be read back out. KYTGate calls the vendor at decision time and records the finding, naming the vendor as its source in every sentence it prints. The finding is filed with the public-source checks in the same case, receipt and replay. The vendor's answer then becomes part of a record that can be verified without trusting either vendor, instead of a screenshot in a folder.
Nothing about your customers is pooled or shared across tenants, and the database has no column for a name or a document. Your identity file stays where it is.
What KYTGate adds
Every decision is stored with the inputs that produced it and the policy version applied to them. It is then signed with Ed25519 and anchored in a daily Merkle attestation. Replay re-runs the stored inputs against the stored policy. No provider is re-queried, so the answer cannot drift. An evidence pack exports as self-contained JSON that a reviewer can verify with a published key, without trusting you or us.
The public-source checks run whether or not a commercial vendor answers. OFAC, UK and EU sanctions data is re-synced every six hours. Live USDT and USDC freeze status is read from the issuers' own contracts. On-chain verification confirms that the transaction you were told about exists, with the amount you were told.
Three common situations
Your vendor changes an address's label
The original decision keeps the finding as it stood, with the vendor named and the timestamp attached. The new label opens a fresh question instead of rewriting an answered one.
An OTC settlement agreed on a call
Screen the counterparty address before the transfer and attach the decision to the ticket. The receipt turns 'we checked' into something a counterparty's bank can read.
An examiner asks about a decision from March
Replay reproduces it deterministically from the stored inputs and the March policy version. Anything that has changed since shows up as a change rather than a contradiction.
Best fit: exchanges, brokers and OTC desks that already pay for attribution data and need the decision record, the policy versioning and the replay that their vendor does not sell.
Still working out which obligations apply to you? Who must screen crypto payments sets out the two layers: sanctions, which bind every EU business today, and due diligence, which binds a defined list of sectors from 2027, with the source next to each row.
Decision-support software, not legal advice. Which obligations apply to you depends on your licence and structure; confirm with counsel.