Document verification
Read and check an ID document and its NFC chip.
Missing a country or a custom check? Tell us what you need.Book a 15-min call
Your backend creates a session, the person verifies on a hosted page or in an embedded frame, and the result comes back by webhook and as a signed result.
The full API reference is public at app.secuveri.com/docs.
curl -X POST https://api.secuveri.com/v1/sessions \
-H "x-api-key: $SECUVERI_API_KEY" \
-H "content-type: application/json" \
-H "Idempotency-Key: signup-1042" \
-d '{
"workflow_id": "wf_kyc_standard",
"vendor_data": "customer-1042"
}'201Response
{
"verification_id": "VRF-7KQ2M9XA",
"status": "CREATED",
"url": "https://verify.secuveri.com/verification/VRF-7KQ2M9XA?t=…"
}Quick start
In Settings, API keys. sk_test_ runs the sandbox, sk_live_ production. Keys stay on your server.
POST /v1/sessions returns a link. Redirect, show a QR code, or let us send it by email or SMS.
A signed webhook tells you it's done. Read the signed result for the outcome and every check.
Standalone APIs
Every check is also sold as its own API, outside a verification flow. Each is marked with its real status.
Read and check an ID document and its NFC chip.
Compare two face images.
Check that a selfie shows a live person.
Estimate age from a face image.
Screen a person against sanctions and PEP lists with POST /v1/aml/screen.
Read a utility bill or statement for your review.
Validate the Content Credentials in an image with the secuveri C2PA Validator.
Check a company in the Swiss commercial register.
Results you can trust
The webhook tells you something happened. The signed result tells you what, in a form anyone with our public keys can verify.
Your backend
POST /v1/sessions
Hosted flow
Document, liveness, face match
Webhook
secuveri-signature: HMAC-SHA256
Signed result
ES256 JWS, verified with /.well-known/jwks.json
Building blocks
Everything you need to run verification from your own backend.
Create a session and get a link and token. Idempotency keys, one open session per customer, and we can send the link by email or SMS.
Events when a verification finishes or is reviewed, HMAC-signed and retried for about 21 hours.
Each result as an ES256 JWS without personal data, verifiable with our public keys.
Open the flow in a modal or inline frame with one script tag, with a QR handoff to the phone.
Test keys and free scenarios that finish a session with the outcome you choose.
Confirm a returning customer with a selfie and liveness, matched against their earlier verification.
After a full verification, people can save a secuveri Verified ID in the swiyu app and share it next time, bound to the holder. swiyu Beta-IDs are accepted too. Works on swiyu's public beta.
Block or allow emails, phone numbers, IP ranges, devices, your user IDs or document countries, by API or in the dashboard.
SDKs
secuveri.js opens the hosted flow in a modal or inline frame and reports its progress.
Plain HTTPS and JSON from any language, with an OpenAPI description.
A typed browser package for the embed and its events.
A Node.js client for sessions, results and webhook signature checks.
Native capture and NFC chip reading inside your iPhone app.
Native capture and NFC chip reading inside your Android app.
Resources
Sessions, webhooks, signed results, AML, lists and errors. Public, no sign-in needed.
Use secuveri from Claude, ChatGPT, Cursor and other MCP clients at mcp.secuveri.com. Sign in with Connect with secuveri, no API keys to paste.
Open-source sample apps: an age-check shop, bank onboarding, a webhook receiver and the swiyu playground.
A shop that checks age before checkout. Try it live.
An account opening flow with KYC and AML. Try it live.
Get a secuveri credential, present it from the swiyu app and see what was checked and shared. Try it live.
Tell us what you’re trying to verify. We’ll show you how secuveri can fit your workflow.