Children and students: verified in-person through participating educational institutions (no extra documentation required).
Adults: verified in-person through participating organisations such as banks and employers (no extra documentation required).
Online verification: conducted by government-recognised third-party verifiers approved as equivalent to in-person registration (documentation requirements determined by jurisdiction).
This ensures every DigiChek account begins with a trusted, human-verified enrolment, not self-declared information.
The verifier sends the user’s name, date and place of birth to DigiChek.
DigiChek generates a secure user profile and enables the user to create their own DigiChek Key.
The user sets a minimum of six security questions and a code word.
The DigiChek Key is unique, reusable, works on any device and with every participating organisation, yet is never shared outside DigiChek, ensuring the user retains full control.
The user enters their username on the organisation’s login screen.
The organisation retrieves the user’s name, date and place of birth associated with that username.
The organisation sends this information to DigiChek.
DigiChek checks whether a matching profile exists in its system and returns a simple Yes/No response.
No match: the organisation may redirect the user for verification and DigiChek Key creation.
Yes match: a DigiChek Key pop-up box is generated for the user to enter their DigiChek Key.
Organisations can choose to use less than all three of the data pieces on a user’s DigiChek profile, depending on their compliance obligations.
The user enters their DigiChek Key into the pop-up box which is sent only to DigiChek.
DigiChek compares the user information on the DigiChek Key profile against the information provided by the organisation.
DigiChek returns a simple ‘Yes/No’ response, confirming whether the user’s claimed age or identity is genuine.
No match: the organisation should decline the user access.
Yes match: the organisation can grant the user access.
This allows organisations to:
• Confirm exact age thresholds (e.g., 13+, 16+, 18+).
•Ensure only verified individuals can access their systems.
•Avoid duplicate and bot accounts.
•Maintain a frictionless, device-agnostic, and inclusive user experience.
The user enters Name, Date of Birth, Place of Birth and card information at the merchant’s checkout.
The merchant forwards user and card information to the payment gateway.
The payment gateway sends only user information (not card details) to DigiChek.
DigiChek checks for a matching user profile and returns Yes/No:
No match: the payment gateway proceeds with normal card processing via the issuer.
Yes match: a DigiChek Key popup is triggered.
The user enters their DigiChek Key Into the pop up which is sent only to DigiChek.
DigiChek compares the user information on the DigiChek Key profile with the user information from the payment gateway.
DigiChek sends Yes/No to the payment gateway:
Yes: the payment gateway forwards card information to the issuer for normal processing.
No: the payment gateway advises the merchant the transaction is declined and the card data never reaches the issuer.
• This ensures identity is confirmed before card processing, reducing fraud and chargebacks while exposing minimal personal or payment information.
• The merchant is unaware whether the transaction is declined by DigiChek or the issuer.
• Issuers and payment gateways can select all three or any two of the user’s data held by DigiChek in the confirmation process.