GateCite: the regulatory basis, signed
Each rule, check and decision mapped to the FATF, EU and OFAC provisions it supports, signed into the receipt.
Start free sandboxTalk to us50 screenings a month free, no card.
On this page
GateCite in simple terms
Every decision KYTGate makes now carries a short list of the rules it answers: which FATF Recommendation, which EU article, which OFAC requirement.
That list sits inside the signed receipt, so an auditor sees why a deposit was held and which obligation the hold serves in one record, and can check every reference against its official source.
IN EVERYDAY TERMSThink of a recipe that lists, next to every step, the food-safety rule it follows, with a link to the rulebook.
What it does
GateCite keeps a library of the provisions KYTGate controls support (FATF Recommendations, the EU Transfer of Funds Regulation, the AML Directive and the AML Regulation that replaces it, and OFAC's reporting rules), each with its official source and the date it was last checked.
Every built-in policy rule, coverage dimension and decision is mapped to those provisions. When a screening finishes, the provisions for the rules that fired, the decision and the record itself are written into the Decision Receipt as its basis field, before it is signed.
The full map is public at /controls, as JSON at /api/public/citations and as a CSV control matrix for an auditor's spreadsheet. Evidence packs print the basis in their own section, and in the console every policy rule and every case shows the same references next to it.
Why a broker needs it
Examiners do not only ask what you decided; they ask which obligation the control serves and how you know it works. A matrix kept in a separate spreadsheet drifts from the system it describes. A basis signed into each decision cannot drift, because it is produced by the same run that made the decision.
How it works
Each receipt records the library version it was mapped with, so a later correction to the library never changes what an earlier receipt said. A rule you write yourself is listed as unmapped rather than given a borrowed article, and a control that goes beyond what any rule requires (reading stablecoin issuer freezes, for example) says so instead of citing one.
An article is cited only when its number has been read in the official text, and a provision not yet in force, such as the AML Regulation before 10 July 2027, carries the date it applies from.
Try it without an account: the control map · the CSV control matrix.
What it does not do
GateCite is a mapping, not legal advice. It shows which provision a control supports; it does not decide which obligations apply to you, which depends on your licence, jurisdiction and structure. National rules beyond the EU and OFAC are not mapped yet, and a tenant's own rules are not mapped at all.
API
GET /api/public/citations → library + control map (JSON)
GET /api/public/citations/csv → control matrix (CSV)
// inside every new Decision Receipt, covered by the signature:
"basis": { "library": "gatecite-2026-10-07",
"items": [ { "about": "rule:sanctions-direct", "citations": [ "fatf-r6", "fatf-r7", "us-ofac-501-603", … ] },
{ "about": "record:receipt", "citations": [ "fatf-r11", "eu-amld-art40", … ] } ],
"unmapped": [] }Full reference: /controls · OpenAPI 3.1