Your user downloads the IdentiGate app and completes a one-time identity creation. The app automatically picks the best route based on their device and document β NFC chip where supported, document + face match everywhere else. After setup, every verification and signature happens through your platform via API.
User downloads the IdentiGate app (iOS/Android) and taps "Create IdentiGate." Works on any modern smartphone β NFC is used if available, document + face match otherwise.
NFC route (179 ICAO 9303 countries): the app reads the passport's NFC chip β cryptographically signed data from the issuing government. Document route (everywhere else, or pre-NFC documents): the app captures the document and runs FaceTec liveness + document authenticity checks.
A live selfie is matched against the document's biometric data. Liveness detection blocks replay and deepfake attacks. User sets a PIN. Dual Key credentials are generated β half on device, half in our FIPS 140-2 Level 3 HSM on the server side.
An X.509 certificate is issued binding identity β device β key. The identity is now active, reusable across all connected platforms for the lifetime of the underlying document. When the document is renewed, the identity refreshes seamlessly.
Your platform never touches passport data, biometrics, or cryptographic keys. You call our API and receive proof.
Simple REST API with clear documentation. SDK for iOS and Android. Sandbox environment for testing. No PKI expertise needed on your side.
Trigger identity verification, document signing, or authentication with a single API call. The user confirms on their device. You get the result.
You receive a cryptographic certificate confirming the user's verified identity. No passport images. No personal data on your servers. Ever.
Traditional identity verification is a dead end β one check, one service, start over. IdentiGate creates a permanent, reusable digital identity across every connected platform.
After verification, IdentiGate does not store passport data, biometric photos, or personal information. We hold cryptographic proof that the verification happened β not the identity itself.
Your platform receives a verified certificate β not a passport copy. GDPR compliance by architecture, not by policy.
One simple price range. Both routes β NFC and document β available through the same API, billed the same way. You choose the assurance level that fits each verification; we don't penalise the choice.
Exact pricing depends on monthly volume, integration scope, and compliance requirements. Contact sales for a custom quote.
Get Custom PricingSee NFC passport scan, face match, and identity creation on a real device. 20 minutes.
Book demo...REST API reference, SDKs, sandbox environment, and integration guide for developers.
Request access...Transaction-based pricing. No setup fees, no licenses. Pay per verification and signature.
Get pricing...Step-by-step technical integration guide. From sandbox to production in weeks.
Get started...20-minute demo: NFC scan, face match, identity creation β on a real device. We'll map it to your use case.