
Inside a Modern Verification Stack
How document, biometric and signal checks fit together in a production verification pipeline.
5 min · October 2026
Read More: Inside a Modern Verification StackMissing a country or a custom check? Tell us what you need.Book a 15-min call
How to wire identity or age verification into a web app, from the first sandbox session to webhooks and signed results, and the mistakes that are easy to make on the way.
By secuveri teamPublished

The code for identity verification in a web app is small. Your server creates a session, the person goes through a hosted flow, and your server reads the result. Most integration bugs come from the decisions around that code: which signal you trust, what happens when a request is retried, and what the app does while a case waits for review.
This guide walks through the integration in the order you would build it, using secuveri's API and the open-source example apps. If you want to see the finished thing first, try the bank onboarding demo or the 18+ shop demo. Both run in the sandbox.
There are three parts:
The browser is only involved in step 2. That is deliberate, and it shapes the rest of the integration.
Create a sandbox API key in the dashboard under Settings, API keys. Sandbox keys start with sk_test_, production keys with sk_live_. Both belong on your server only.
Next, create and publish a sandbox workflow with the checks you need. If you embed the flow in your page, add your local origin, for example http://localhost:3030, under Settings, Branding, in the list of websites that may embed the flow.
The sandbox runs the real checks, so you can verify with your own document while you build. It also has free scenarios that finish a session immediately with the outcome you choose, approved, declined or sent to review, without a document. Use those to test your code paths. You will want to run the decline and review paths many more times than anyone wants to take a selfie.
A session is one API call: POST /v1/sessions with your API key in the x-api-key header, the workflow ID, and your own reference in vendor_data. The response contains a verification ID and the link to the flow. With the Node.js package @secuveri/node, the same call is createSession.
Two details save trouble later:
Return only the session link or token to the browser. The API key never leaves your server.
You can redirect the person to the link, show it as a QR code, or have secuveri send it by email or SMS. To keep people inside your app, use the browser package @secuveri/web and call Secuveri.start with the session URL. It opens the flow in a modal or inline frame and reports progress through callbacks such as onComplete, onCancel and onError.
onComplete means the person reached the end of the flow. It does not mean they passed, and anyone with the developer console can call it. Treat it as a hint to ask your own server for the outcome, never as the outcome itself.
The shop example shows this well. Its checkout only places an order once the server holds an approved result for that order. Calling onComplete by hand changes nothing, because the server still finds no approved result.
When a verification finishes or is reviewed, secuveri sends a webhook to the endpoint you set under Settings, Webhooks. The webhook receiver example does it in one file. The rules it follows:
The webhook endpoint has to be a public https URL. For local development, use a tunnel, or rely on the browser callback plus a server-side result check until you deploy.
Fetch the result with the verification ID (getResult in @secuveri/node). It comes as a signed result: an ES256 JWS that you verify with the public keys at /.well-known/jwks.json. It contains no personal data, so you can keep it as evidence of the decision without storing document images or dates of birth.
Before acting on it, check:
Run the same settlement logic from both the browser path and the webhook path, and make it safe to run twice. Whichever arrives first settles the case, and the second finds nothing left to do.
Before going live, make sure your app behaves sensibly when:
Sandbox scenarios cover the outcomes. The rest is ordinary testing of your own code.
Moving to production is a configuration change: an sk_live_ key, a published production workflow, your production origin in the embed list, and a webhook endpoint with its signing secret. The code stays the same.
The full API reference, including errors and AML screening, is in the dashboard at app.secuveri.com/docs. For an overview of what the API offers, see the developers page.
This article is general information, not legal or compliance advice. Your obligations depend on your sector, licence and markets.
Build a verification experience around your business.

How document, biometric and signal checks fit together in a production verification pipeline.
5 min · October 2026
Read More: Inside a Modern Verification Stack
What is stored on the chip in a passport or ID card, how a phone reads and checks it, and why it tells you more than any photo of the document.
6 min · November 2026
Read More: How NFC Chip Verification of Passports and ID Cards WorksTell us what you’re trying to verify. We’ll show you how secuveri can fit your workflow.