GateRemediate: customer information requests
One-time customer link from a case: ownership signature, exchange receipt, source-of-funds answers, documents.
Start free sandboxTalk to us50 screenings a month free, no card.
On this page
GateRemediate in simple terms
When a deposit needs explaining, the reviewer sends the customer a one-time link asking only for what is missing: proof they own the wallet, an exchange receipt, where the money came from.
The answers land in the case file on their own. Wallet ownership is checked on the blockchain on the spot; everything else waits for a person to read it.
IN EVERYDAY TERMSThink of a clinic sending you a form link before your appointment, instead of chasing you by phone and losing the paper.
What it does
From a case, a reviewer creates an information request: a checklist (wallet ownership signature, exchange withdrawal receipt, source-of-funds questions, free explanation, other document), an optional message and a due date. The customer receives a one-time link that shows only your company name and the checklist, never the case or the decision.
Answers and files land on the case timeline. Ownership signatures are verified on the spot. Tron and Bitcoin wallets cannot sign, so for them the page shows a micro-transfer challenge (send exactly 0.0537 USDT to your address) that is checked on-chain. An unanswered request expires on the due date and the case.sla_breached webhook fires, so you can follow up through your own channel.
Alongside the answers, the customer's 2027 AMLR data fields (LEI, entity type, residency, occasional-customer status, CDD level and review date, kept per customerRef via PUT /api/v1/customers/{ref}/profile and never a name or a document) sit on the case, so the reviewer sees which customer type the threshold was crossed for and the SAR draft carries it.
Why a broker needs it
Most REVIEW cases end with a question to the customer, and most brokers ask it by e-mail and file the answer by hand, or not at all. When the request is created from the case, answered through a link and filed on the same timeline, "we asked and they proved ownership" becomes part of the evidence pack.
How it works
POST /api/v1/cases/{id}/remediation (or the console) returns the link plus a ready-to-send subject and text. Default is link-only: you deliver it through your own e-mail, CRM or app, and the customer's address never reaches KYTGate. Optionally pass customerEmail and KYTGate sends it once as "<your company> via KYTGate" with your compliance inbox as reply-to; the address is used for that send and never stored. The case moves to docs_requested and back to open on response; webhooks case.docs_requested and case.remediation_submitted carry the details. Files are limited to 3 × 2 MB (PDF/PNG/JPG/WEBP), stored with the case and deleted with it under your retention.
What it does not do
GateRemediate collects and files answers. It does not assess them. A submitted document does not change the decision. A reviewer does, on the timeline, under four eyes for blocks. It does not verify exchange receipts or source-of-funds statements against any external source. Only wallet-ownership proofs (signature or micro-transfer) are checked against the chain.
API
POST /api/v1/cases/{id}/remediation
{
"items": ["ownership_signature", "exchange_receipt", "source_of_funds"], // + explanation | other_document
"message": "Please confirm the wallet used for this deposit.",
"dueDays": 7 // 1–60; add "customerEmail" only if KYTGate should send it
}
→ { "requestId": "…", "link": "https://kytgate.com/r/…", "dueAt": "…",
"suggestedSubject": "…", "suggestedText": "…", "mailedByKytgate": false }Full reference: /docs#remediate · OpenAPI 3.1