KYC, KYB and AML

Customer verification with results you can explain

verkyc checks documents, the NFC chip, faces, companies and sanctions lists. For every check you see exactly what was done: the source, the version, the time and the evidence. Your policy makes the decision, and the report is signed and verifiable by reference.

Case C-7K3M9Q2T

Individual, KZ passport

  • Machine readable zoneCheck digits match
    pass
  • Chip signatureChain to the CSCA, Master List
    pass
  • 1:1 face matchingChip portrait, policy threshold
    pass
  • Sanctions listsNo match established: UN, OFAC, UK
    pass
  • Residential addressA supporting document is needed
    inconclusive
Decision: document requested by policy v12Report signed with ES256
Example of a verification card

How it works

From creating a case to a signed report: one API contract and one console.

  1. Create a case

    Through the API or in the console: the applicant, the purpose, the country and the policy version.

  2. The applicant completes the steps

    Via a link, an embedded widget or your app. The server issues the steps and hints.

  3. The platform checks

    Every check returns an outcome with a reason; the policy combines them into a decision or manual review.

  4. You get the result

    A signed webhook, the case card in the console and a signed report verifiable by reference.

Why verkyc

For developers

A REST API with an OpenAPI contract, keys for the test and live environments, cursor pagination and errors in problem+json format.

  • A verification link in one request
  • Webhooks signed with HMAC-SHA256, with retries
  • iOS and Android SDK, web widget
  • A test environment without real data
Go to the documentation
Create a verification link
curl https://api.verkyc.com/v1/cases/$CASE_ID/hosted-links \
  -H "Authorization: Bearer $VERKYC_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{"locale": "en", "return_url": "https://example.com/onboarding/done"}'

Security by design

Personal data is encrypted with a separate key per applicant and case, keys are held in the regional KMS, files are scanned for malware and parsed in an isolated executor.

How security works
  • AES-256-GCM encryption
  • Isolated file processing
  • Audit log
  • Deletion with key destruction

Frequently asked questions

Which countries are supported?

The first wave: Russia, Belarus, Kazakhstan, Uzbekistan, Kyrgyzstan, Tajikistan, Armenia, Azerbaijan, Turkmenistan and Moldova. Capabilities for each country are on the coverage page.

Where is the data stored?

Processing and storage run in the platform region in Germany, and backups are kept there too. Encryption keys are held in the regional KMS.

How fast can we start?

A test API key and the test environment are issued after your request. Integration through a verification link takes one API request and webhook handling.

Can a report be verified without console access?

Yes. The report is signed, and its authenticity is verified by the reference in the report without sharing personal data. The public signing keys are published at a standard address.

How much does it cost?

You pay for the checks actually performed under a plan with a minimum payment. Usage in the test environment is not billed. A quote for your volume is available on request.

See it on your own scenarios

Tell us who you need to verify and where. We will prepare a demo, test API access and a price estimate.