The mechanism underneath does not change by industry — a state’s signature on a passport chip, or a capture signed on the device as it was taken, and then no image kept. What changes is which moment it has to survive: a disputed purchase, a pickup at a stranger’s door, or a counter a citizen should not have to visit.
Chargebacks, account farms, and two age duties already in force
A player disputes a purchase, opens a second account, and buys again. The platform pays twice and loses the ban. Verification sits inside the purchase flow that already exists, and the account it clears is tied to one human.
One hosted URL inside the existing checkout. Live with a gaming ticket platform since 30 August 2026.
The courier at the door is not the courier you cleared
Onboarding a seller or a courier once is the easy half. The hard half is the pickup three months later, when someone else is holding the phone. Re-identification runs against a token, so nobody re-uploads a document and no image is stored to compare against.
Native SDK embedded in your own app, React Native or Flutter, with a signed webhook to your server.
No new biometric database, and no new infrastructure
A citizen identifies against the chip in the passport the state already issued, verified to that state's own root. There is no central face database to build, to budget for, to isolate, or to lose — because no face image and no face template is kept.
Verified fully offline. One agency's token cannot be matched against another's.
Nothing on these three pages is a different product. The integration is two server-to-server calls and one URL; the segment decides which assurance level your server demands and how few fields come back.
| Segment | The moment it has to survive | Typical level demanded |
|---|---|---|
| gaming | A purchase, a dispute, and the second account opened afterwards. | low to substantial |
| marketplaces | A pickup months after onboarding, with no document re-upload. | substantial |
| public sector | A citizen proving entitlement without a counter visit. | high, via the passport chip |
Levels are declared by your server and enforced by ours; a weaker capture is refused rather than accepted with a flag. The high level requires an attested native capture and an NFC chip read, which means a passport and a phone with NFC. A browser capture cannot reach it.
What a security officer should read instead of a badge row →Twenty minutes, a real passport, and the trust chain resolving offline in front of you. We will also show you what is not shipped.
Request a walkthrough