GateProof: evidence packs and reports
Evidence pack as JSON or PDF, a monthly compliance report, and a browser-side receipt verifier anyone can use.
Start free sandboxTalk to us50 screenings a month free, no card.
On this page
GateProof in simple terms
GateProof turns a case into a ready file: a PDF showing what was checked, what was found, who decided and why, with the signed receipt inside.
It also produces a monthly report of all your decisions and a draft suspicious-activity report that your MLRO finishes and files.
IN EVERYDAY TERMSThink of a complete patient file you can hand to a second doctor: everything in one folder, nothing to reconstruct from emails.
What it does
For any screening that opened a case, GateProof produces a dated, human-readable PDF: decision, subject, the coverage matrix (what was and was not checked), every signal, the append-only timeline including four-eyes closure and any MLRO override, and the signed receipt with its hashes and verification instructions. A machine-readable JSON pack with the raw receipt is available from the console.
The monthly compliance report covers one calendar month of your tenant: screenings by decision, trigger, network, assurance tier and policy version; what the sources found; cases opened and closed and how they ended; every MLRO override with both names and the reason; SLA breaches and median time to close; wallets, reconciliation outcomes, shadow agreement, list snapshot freshness and console activity.
The receipt verifier at /tools/receipt-verifier lets an auditor check any receipt's signature in their browser, without an account and without uploading anything.
GateReport turns a case into an STR/SAR draft (GET /api/v1/cases/{id}/sar?format=json|goaml|narrative, or the console): the reporting entity from your settings, the subject as your customerRef only, every address, transaction hash, chain and amount involved, the timeline from screening through rule hits to remediation answers, four-eyes and any override, the coverage matrix, list snapshot hashes and the signed receipt, as structured JSON, goAML v4-style XML shaped for completion in the FIU's own portal, or a who / what / when / where / why / how narrative pack. The reasons for suspicion are always left empty for the MLRO, with the fired rules listed as prompts; nothing in it is written by the system beyond stored facts.
Why a broker needs it
Regulators and banks ask "show me why you accepted this deposit" and "show me your month". The answer should be a download rather than a week of reconstruction from logs and e-mails, and the person asking should be able to check it without trusting you or us.
How it works
GET /api/v1/screenings/{id}/evidence.pdf for a case; GET /api/v1/reports/monthly?month=YYYY-MM&format=json|pdf for the month. Both are generated from stored records only, with nothing recomputed at download time, so what you export is what was recorded. The console offers the same downloads per case and per month.
Try it without an account: Decision Receipt verifier (in-browser, no account).
What it does not do
An evidence pack documents a decision; it does not make one. Nothing in it is re-screened or re-scored at export time, and it contains only what your tenant recorded. A document the customer never sent is not in it. The report counts decisions; it does not draw conclusions about your programme.
API
GET /api/v1/screenings/{id}/evidence.pdf → dated PDF for one case
GET /api/v1/cases/{id}/sar?format=goaml → STR/SAR draft (json | goaml | narrative), "why" left for the MLRO
GET /api/v1/reports/monthly?month=2026-08&format=pdf → one month, board-ready
GET /api/v1/reports/monthly?month=2026-08&format=json → the same figures for your own reportingFull reference: /docs#evidence · OpenAPI 3.1