KYC flows are code.
Edit them like it.
flowchart TD start([applicant]) start --> doc[document check] doc --> live[liveness] live --> sanc[sanctions + PEP] sanc --> risk{risk score?} risk -->|low| tier2[approve · tier 2] risk -->|high| review[manual review] tier2 --> issue[cards.issue ✨]EDIT THE CHART → THE FLOW REDEPLOYS · VERSIONED · A/B TESTABLE PER MARKET
Sumsub-grade verification,
zero integration work.
The checks live inside the issuing platform — pass KYC, get a card, in one flow. No webhooks between vendors, no state machines to keep in sync, no data leaving the stack.
Documents · 220+ countries
Passports, IDs, licences, proof of address — forgery detection and MRZ/NFC validation in ~2 seconds.
Liveness & face match
Passive liveness with deepfake and injection-attack detection — no "turn your head" gymnastics for the user.
Sanctions, PEP & adverse media
Screened at onboarding and continuously after — a hit on an existing holder opens a case automatically.
KYB for business programmes
Registry lookups, UBO graphs and director verification for corporate card programmes.
Ongoing AML monitoring
Transaction patterns feed back into holder risk — KYC isn't a gate, it's a loop with Fraud AI.
Case management included
Manual review queues with SLAs, four-eyes approval and full audit trails — in the same dashboard, same SSO.
If you can chart it,
you can ship it.
Flows are Mermaid files in your repo — reviewed in PRs, deployed via API, rendered live in the dashboard for your compliance team. Ops can tweak thresholds in the UI; the chart is always the truth. Branch per market, A/B versions, roll back instantly. Everything is possible.
Chart your onboarding in the demo.
Bring your current KYC flow — we'll rebuild it as a live Mermaid chart during the call.