GateMonitor — re-screening and list freshness
Past counterparties re-checked against lists re-synced every 6 hours; SLA breaches and staleness surfaced.
On this page
What it does
Onboarding-time screening is a snapshot. GateMonitor keeps asking the question afterwards: did any address you previously screened — and did not block — get listed since? Sanctions lists are re-synced at least every 6 hours, each sync stored as a content-hashed snapshot, and every subject screened in the last 90 days is checked against the newest one.
Registered wallets get more: every active wallet in your registry is re-observed for sanctions listings and USDT/USDC issuer freezes after every list change and every 6 hours, and a wallet.state_changed webhook plus a case timeline entry go out only when something actually changed — a listing, a delisting, a freeze or an unfreeze.
The same module watches your own operation: cases held longer than your SLA fire a case.sla_breached webhook, and a stale list snapshot is reported on the status page and in the coverage matrix rather than quietly tolerated.
Why a broker needs it
A wallet you accepted last month can be listed today, and the customers you already accepted are the ones at risk. Supervisors expect ongoing monitoring, not a one-time check; OFAC's own guidance describes the lookback. A record that shows the re-screen happened — and what it found — is what makes "we monitor" a control rather than a sentence.
How it works
After each list sync a re-screening job compares the distinct subjects of the last 90 days against the current sanctions cache, exactly as the live check does (normalised address, exact match). A new match writes a screening with trigger rescreen, produces a signed receipt and opens a case automatically; the original decision and its receipt stay intact for the day you decided.
SLA checks run hourly against each tenant's own limit; a breach is recorded once on the case timeline and pushed as a webhook. In shadow mode breaches are recorded but not announced. Snapshot age per list and the live queue are visible on /status.
Try it without an account: Free wallet sanctions check (shows the snapshot used).
What it does not do
GateMonitor re-checks sanctions listings and issuer freezes; it does not watch the blockchain for new transactions from a counterparty, and it does not re-run behaviour rules or third-party providers. A re-screen finding opens a case for a human — it never reverses a credited deposit by itself.
API
GET /api/v1/cases?status=open // includes cases opened by re-screening: screening.trigger = "rescreen" // webhook when a case exceeds your SLA: X-KYTGate-Event: case.sla_breached
Full reference: /docs#webhooks · OpenAPI 3.1