Identity collection model
- Customer
- Identity documents
- Personal information
- Business systems
- Storage + retention + access controls
Enterprise verification infrastructure
Deploy Checkify across customer journeys, applications and physical locations with configurable proofs, APIs and rollout support — designed to give your systems the verification result they need without unnecessary identity-data collection.
ISO 27001: Stage 1 complete. Stage 2 in progress. Not yet certified.
A different verification model
Traditional verification architectures can leave businesses collecting more identity information than the decision actually requires. Checkify is designed around requesting the proof needed for the transaction and returning a limited result.
Over 18 ✓
The result the workflow needs — without automatically handing the underlying identity documents to the relying business.
Enterprise outcomes
Use the proof level that matches risk — across digital journeys and supported physical locations.
Request age-threshold proofs for regulated customer journeys.
Add human proof to forms, accounts and supported automated-abuse controls.
Request stronger identity assurance where the workflow genuinely requires it.
Use proof-based checks across digital and supported physical access flows.
Access control overviewVerify organisations and business relationships where supported.
Business verification explainedWhere enabled, request specific approved data or assertions rather than entire documents. Currently behind a feature flag and not general availability.
Organisation and item signing is coming soon. It is not available as a mature production capability for enterprise procurement yet.
Choose the assurance you need
Checkify’s verification ladder lets teams choose the level appropriate to risk, rather than demanding maximum identity information for every interaction.
Human verification helps confirm a real person is present for forms, account creation and supported abuse controls — without collecting an identity vault by default.
Age proofs such as age_over_13, age_over_16, age_over_18 and age_over_25 return a threshold result for regulated journeys.
Identity assurance uses product levels including basic, verified and verified_plus — so workflows can request stronger checks only when needed.
highAssurance supports higher-risk flows with stronger supported evidence paths. Exact evidence options depend on device, jurisdiction and configured policy.
The business chooses the level appropriate to the risk. Checkify does not invent external certifications for these levels.
Policy becomes infrastructure
A Checkify Pass defines the proof requested by a particular workflow. Different sites, applications and business processes can request different proofs.
Sites, Passes and proof requests are separate layers — so one business can run many verification points without copying identity documents into each system.
Built beyond one website
Enterprise teams can structure verification around multiple supported sites and workflows. Digital sites and physical locations are configured separately under Manage sites.
Each supported site can use Checkify Passes and return proof results to the systems that need them. We do not claim a separate enterprise org-hierarchy product beyond current business/site/pass management.
Fit Checkify into your stack
Use the integration path that matches your stack — without inventing connectors that are not live.
For custom applications and enterprise workflows that need server-side verification.
For web experiences, forms, checkout and custom embeds.
For supported commerce and content implementations with Pass ID based setup.
For supported in-person workflows at counters, venues and access points.
For Checkify app and device flows where customers complete verification on their phone.
Architecture at a glance
A simple path from business systems to limited proof results.
Reduce unnecessary data exposure
Checkify is designed around data minimisation: request the proof the workflow needs and avoid unnecessary identity-data handover where the service supports it.
Security built into the conversation
Public status only — no invented certifications.
Stage 1 complete. Stage 2 in progress. Not yet certified.
Designed around data minimisation and limited proof results, with privacy-minimising processing where supported.
Traffic encrypted in transit (TLS) for app, API and dashboard flows. We do not claim universal end-to-end encryption.
Signed and time-limited requests and verification references where supported, with audit-friendly operational logging.
Enterprise teams can request security and integration information as part of evaluation.
Start small. Expand deliberately.
Enterprise rollout is designed to feel deployable — not theoretical.
Identify the verification decision and required assurance.
Integrate one workflow or site.
Measure completion, customer experience and operational behaviour.
Roll out to additional sites, products or locations.
Adjust assurance and workflows based on actual requirements.
What enterprise includes
Enterprise conversations cover rollout and technical fit. We do not invent dedicated 24/7, named TAM, uptime SLA, private cloud or on-premise offerings here.
Map workflows, assurance and phased expansion.
Guidance for plugins, SDK and server API paths.
Discuss credit volume matched to expected demand.
Structure verification across supported sites and locations.
Choose human, age and identity levels appropriate to risk.
Help security and compliance teams evaluate Checkify.
Where teams start
Age assurance around protected purchases.
Human, business or eligibility checks around marketplace interactions where supported.
Use the appropriate proof level for the onboarding risk.
Digital and supported physical proof-based access.
Request stronger verification where policy or risk requires it.
Use Checkify APIs and Passes across multiple verification points.
Designed for an ecosystem
Where supported, Checkify can work with external issuers, credential providers, wallets and data sources while presenting the relying business with the proof or result required by its workflow.
Reusable proofs
Where supported, an existing credential or verification evidence can help a user satisfy another Checkify request without unnecessarily repeating the original collection process.
Each business or workflow receives only the proof or information requested and approved for that interaction. We do not claim verify-once-use-everywhere.
The customer is part of the architecture
Infrastructure still has to feel clear to the person completing the check.
A workflow requests a proof.
The request is visible and understandable.
The person consents to the check.
Verification runs through Checkify.
A limited proof returns to the system.
The journey continues.
Enterprise pricing
No fake enterprise price. Same Enterprise plan content as /pricing.
Custom
For custom volume, support or rollout needs.
Starting smaller? Checkify’s standard plans let teams prove the workflow before moving to a wider rollout.
Start with the workflow
We’ll help map the proof, assurance level and integration path — whether you’re starting with one customer journey or planning verification across multiple sites and systems.