Getting started
Introduction
What ScreenKaptain does, who it is for and the two API versions.
ScreenKaptain is a compliance platform for fintechs, crypto firms, marketplaces and payment companies. One account gives you identity verification, business verification, AML screening, transaction monitoring and wallet screening, all through the same API, console and price list.
#Who uses it
- Neobanks and EMIs onboarding customers and monitoring payments.
- Crypto exchanges and on-ramps that need KYC, wallet screening and the Travel Rule.
- Marketplaces verifying sellers and the businesses behind them.
- Payment firms checking merchants and payers.
#Two API styles
| API | Base path | Best for |
|---|---|---|
| v3 Sessions API | /v3/ | New integrations and teams moving from Didit. Workflows, sessions, decisions and all extra modules. |
| v1 API | /v1/ | Server-pushed data, KYB, transaction monitoring, crypto KYT, customer risk. |
Both use the same API keys and the same data. You can mix them: create sessions with v3 and send transactions to v1.
#Environments
Every account has a sandbox (sk_test_ keys, free, never billed) and live (sk_live_ keys). Data never crosses between them. See Sandbox and testing.
#Where things are
| URL | For |
|---|---|
/dashboard/ | Your team: review queue, workflows, rules, keys, webhooks, billing |
/verify/?token=… | Your users: the hosted verification flow |
/sdk/kyc.js | Your website: the embeddable web SDK |
/docs/ | Developers: this documentation |