PRODUCT

The crypto KYT platform: one gate for every funding decision

KYTGate is a crypto KYT platform that sits between your crypto processor and your ledger. Every deposit, withdrawal request and wallet a client registers goes through the same steps: screening against public sources, a decision under a versioned policy, and signed evidence. Each module below describes what it does and where it stops.

0x… addressOFAC · UK · EUUSDT / USDC liveresult +evidencenever stored
SCREEN

Screening against public sources

Sanctions lists, live issuer-freeze contracts, the chain itself and your own ledger events are read at decision time. Each check reports its own status. Nothing is compressed into one score, and a dimension that could not be covered is shown as not covered.

GateCoverage
Nine coverage dimensions per decision, each with its own status instead of a single score.
Learn more →
GateBehaviour
Deterministic, explainable rules on deposits, trading and withdrawals, the data only a broker has.
Learn more →
GateMonitor
Past counterparties re-checked against lists re-synced every 6 hours, with SLA breaches and stale lists flagged.
Learn more →
GateGraph
Your tenant's own relationship graph: which customers share wallets, addresses, devices, IPs, bank refs or card / IBAN tokens.
Learn more →
GateTrace
Observed transfers 1–3 hops around one transaction, from public RPC and Blockscout only, with no attribution.
Learn more →
GateDNA
A deterministic wallet fingerprint from public history: age, activity, stablecoin share, counterparties.
Learn more →
GatePoolIN DEVELOPMENT
In development: know when a wallet caused chargebacks or fraud at other brokers before it funds an account.
Learn more →
DECIDE

Decisions under a versioned policy

Every screening ends in one of four decisions: ALLOW, REVIEW, BLOCK_PENDING_MLRO or TECHNICAL_HOLD. The policy is plain JSON you can read, and each change creates a new immutable version you can roll back to. Anything other than ALLOW opens a case, and blocks close under four eyes. Software never bounces funds.

GateBacktest
Run a candidate policy over your last N days before activating it: what changes, which cases open or close.
Learn more →
GateShadow
Send your current decision alongside ours: agreement matrix over 30 days, where we are stricter, where looser.
Learn more →
GateReconcile
Ledger, processor and on-chain amounts compared per deposit; a mismatch opens a case and fires a webhook.
Learn more →
GateRemediate
One-time customer link from a case: ownership signature, exchange receipt, source-of-funds answers, documents.
Learn more →
PROVE

Signed evidence for every decision

Every decision carries an Ed25519-signed receipt with the list snapshot hashes and policy version that applied. Months later you can replay it, export it as an evidence pack, or give it to an auditor, who can verify the signature without trusting us.

GateReceipt
An Ed25519-signed Decision Receipt on every screening: inputs, list snapshot hashes, policy version, signals.
Learn more →
GateCite
Each rule, check and decision mapped to the FATF, EU and OFAC provisions it supports, signed into the receipt.
Learn more →
GateAttest
A daily Merkle root over all Decision Receipts, published for good and committed to Bitcoin. Once confirmed, no receipt can be backdated.
Learn more →
GateReplay
Re-run any stored decision under its recorded policy, or a candidate one, without re-querying a provider.
Learn more →
GateProof
Evidence pack as JSON or PDF, a monthly compliance report, and a browser-side receipt verifier anyone can use.
Learn more →

Nothing is released by software alone

Decisions are one of four (ALLOW, REVIEW, BLOCK_PENDING_MLRO or TECHNICAL_HOLD) and there is no automatic reject. Anything other than ALLOW opens a case. Releasing a block takes two different people, verified by login, and the override is labelled everywhere it appears.

caseBLOCK_PENDING_MLROreviewer Aproposes RELEASEreviewer Bdifferent login · approvesoverridelabelled on:receipt · PDFmonthly reportbreak-glass keyadmin · no login identity×cannot approve, because it is not a second persontwo different people, verified by login rather than a typed name

API and console

Everything above is reachable from a REST API with an OpenAPI description and a free sandbox, and from a console your compliance team uses for cases, wallets, reconciliation, policy and users. Your team signs in with tenant-scoped accounts that see only your data. KYTGate staff act only on your documented instruction. Signed webhooks push screening results, case events, SLA breaches and reconciliation mismatches into your own systems.

Start free sandbox Talk to usRead the API docs