GateRemediate — asking the customer
One-time customer link from a case: ownership signature, exchange receipt, source-of-funds answers, documents.
On this page
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, and for Tron or Bitcoin wallets — which cannot sign — the page shows a micro-transfer challenge (send exactly 0.0537 USDT to your address) that is checked on-chain. Reminders and expiry are handled: an unanswered request expires on the due date, with a reminder two days before when an e-mail is known.
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. A request that is created from the case, answered through a link, and filed on the same timeline is what makes "we asked and they proved ownership" a fact in the evidence pack instead of a memory.
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 as "<your company> via KYTGate" with your compliance inbox as reply-to. 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; it does not judge. 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