Getting started

ScreenKaptain documentation

One API for identity, business and transaction checks. Verify users, onboard businesses, monitor payments and screen crypto wallets.

#Start here

Quick startCreate a workflow, start a session and read the decision in about five minutes.API referenceEvery endpoint with parameters, examples and responses.WorkflowsBuild a verification flow in the visual builder, then publish it.WebhooksGet signed events when a session or transaction changes.Migrating from DiditKeep your v3 integration. Change the base URL and the API key.MCP serverLet Claude Code or Cursor wire up the integration for you.

#Products

User verification (KYC)ID document, liveness, face match, AML, proof of address, database checks.Business verification (KYB)Registry lookups, officers and owners, director KYC links.Transaction monitoringReal-time allow, review or block with 16 configurable rules.Wallet screening (KYT)Risk and exposure for BTC, ETH, EVM chains and TRON addresses.Travel RuleSend IVMS101 originator and beneficiary data to the counterparty VASP.Ongoing AMLRe-screen approved users every day and after each sanctions update.

#How it fits together

  1. Workflow. In the console you choose the checks a user goes through, and the rules that decide the outcome.
  2. Session. Your backend creates a session for one user and gets back a URL.
  3. Capture. The user completes the hosted flow on web or mobile, or you embed it with the web SDK.
  4. Decision. ScreenKaptain runs the checks, scores the risk and returns Approved, Declined or In Review.
  5. Webhook. Your server is told about every status change, and fetches the full decision when it needs it.

Base URL for every API call: https://{{HOST}}