Onboard in minutes.
Stay compliant for years.
Document verification, biometric liveness, and real-time sanctions screening that deploy now, on an identity layer that keeps your compliance provable as the rules, the fraud, and the cryptography change.
What compliance teams are up against
Three shifts that moved faster than the vendor stack most institutions bought into.
Fraud is now synthetic
Deepfaked selfies and AI-generated documents pass checks that were tuned for photocopies. Verification that cannot tell a live person from a replay is a liability, not a control.
Regulators want the trail, not the checkbox
AML examiners ask how a decision was made, who reviewed it, and whether it would hold up years later. A pass/fail result in a vendor dashboard does not answer that.
Your KYC vendor is a dead end
The identity you paid to verify lives in someone else's database, cannot be reused for authentication or signing, and is protected by cryptography that government migration guidance already treats as end-of-life.
What goes live
The modules you can turn on in the current product, without a platform migration first.
Identity Verification
Passports, driver's licenses, national IDs, and a broad set of additional document types; OCR and MRZ parsing; double-sided capture; global coverage with per-country document and field rules.
Biometric liveness
Live selfie capture, active anti-spoofing against photos, masks, and deepfakes; face-match scoring with configurable thresholds for auto-approve, auto-reject, and manual review.
Sanctions & PEP screening
Real-time checks against open, continuously updated watchlists on every verification, with matched datasets and confidence scores returned.
Jurisdiction & age controls
Restricted-jurisdiction enforcement, IP-based geo-blocking, and configurable age rules per flow.
Integration
No-code flow builder, Web SDK, REST API, webhooks, QR handoff to mobile; separate production and sandbox environments; GDPR deletion endpoints; encrypted at rest.
The same deployment, on the trust layer
Every verification mints an identity-bound key pair and a W3C Verifiable Credential the customer holds. That single step gives you:
Re-usable KYC
Re-verify for a new product, a higher limit, or a step-up without re-collecting documents: the customer presents the credential, you verify the signature.
Authentication from the same identity
Login, transaction signing, and account recovery run on the key derived at onboarding, not on a password or an SMS code.
A defensible audit trail
Each decision is cryptographically signed and timestamped; the proof survives vendor changes and key rotations.
Post-quantum readiness already in place
Keys and signatures use the NIST post-quantum standards today, so the identities you issue now are not the ones you re-issue later.
Where teams start
Each one runs on the modules above — pick the one that matches the quarter you are in.
- Digital account opening for retail and SME customers worldwide from one flow
- Perpetual KYC: re-screen and re-attest on a schedule without a new document capture
- Step-up authentication for high-value transfers using the onboarding key
- Travel Rule and counterparty attestation for payment platforms (FATF-aligned)
- Eligibility proofs (age, residency, accreditation) shared as credentials, not as copies of documents
What we build on, and what we claim
Open specifications, named without the version churn. Every status below is a different promise.
W3C Verifiable Credentials
NIST post-quantum standards
FIDO/WebAuthn
OpenID Connect
eIDAS
FATF Travel Rule
Canadian-owned; headquartered in British Columbia.
Compliance that keeps pacewith product.
Start with verification. Keep the identity. Request a demo of the dashboard, or get sandbox credentials and run your first verification today.