INTEGRATIONS · KYC
KYC. Sumsub and Jumio shipped. Any other, in hours.
The two vendors that cover most broker use cases today, live in the stack. The vendor you already trust, added in hours. Per-jurisdiction routing. One form, any provider.
KYC is the one integration a broker usually cares about by name. They've chosen a vendor, negotiated a rate, trained their compliance team, and built operational muscle around a specific tool. Slate's KYC integration was built so that loyalty is rewarded — not punished. Sumsub and Jumio are shipped for the majority of use cases. Anything else is hours of work, not weeks.
Sumsub and Jumio, shipped
The two vendors that cover most broker use cases today, live in Slate.
Sumsub and Jumio are the shipped KYC vendors. Both are production-integrated: unified document submission, per-country rules, webhook-driven status updates, confidence scores captured, failures routed to the manual review queue. You plug in your key and the integration is done — same day. Per-jurisdiction routing decides which vendor handles a submission based on the trader's country, the broker's preference, and the regulatory rule for the jurisdiction.
But what if your vendor isn't one of them?
Veriff, Onfido, IDology, or any local ID bureau — added in hours.
If your vendor is different, the integration layer adds it. Veriff, Onfido, IDology, a regional ID bureau, a specialized document verification service, a national identity number lookup — Slate's KYC interface is generic enough that any provider with an API can be wired in within an afternoon. The broker keeps the vendor they trust. The platform catches up to them, not the other way around.
One form, any provider
The trader sees a single, branded KYC form. The router picks the vendor.
Traders fill out one form regardless of which vendor is running behind it. The form is branded to the broker, rendered in the trader's language, and instrumented with progressive disclosure so weak pass rates don't get blamed on the front end. The router picks the vendor per submission. The audit log always records which vendor handled which trader.
When verification fails
A manual review queue with the full case file, not the vendor's generic dashboard.
Failed KYC doesn't get lost inside the vendor's own dashboard. It lands in Slate's manual review queue with the full document evidence, the vendor's confidence score, the trader's transaction history if any, and the compliance notes. The compliance officer approves or rejects with one click; the action flows through a second approver; the audit ledger records the decision. No tab-switching between Slate and the vendor's console.
Sumsub shipped · Jumio shipped · Any other KYC provider in hours · Per-jurisdiction routing · One branded form, any vendor · Manual review queue · Two-person sign-off on approvals · Full KYC audit trail
Use this to solve
Keep the KYC vendor you trust. Add anything else in hours.
Book a demo and we'll show you the per-jurisdiction router in action with a live trader submission.