WHITE PAPER VERIFICATION
Prove the session was live. Not recorded. Not replicated.
Daksam Analytics White Paper Verification generates a unique 6-digit number for every session. The customer writes it on paper and takes a selfie holding it. The number did not exist before the session started. No pre-recorded video or deepfake can include it.
Standard liveness checks confirm that a real person is in front of the camera. They do not confirm the session was live at the moment it claims to have happened. A sufficiently sophisticated deepfake or a pre-recorded video can pass a liveness check without the person being present in real time. White Paper Verification closes that gap. The 6-digit number is generated fresh for the session by Daksam Analytics. It is unique. It is unpredictable. It could not have appeared in any recording made before the session began. The selfie holding it proves the person and the number were in the same place at the same time.
THE CHALLENGE
A Liveness Check Confirms a Face. It Does Not Confirm a Moment.
Standard liveness detection is strong against basic fraud. Against sophisticated attacks using pre-recorded video or AI-generated faces, the gap between confirming a face and confirming a live session matters significantly.
HOW IT WORKS
A Number That Could Not Have Existed Before the Session Started.
White Paper Verification adds a session-specific layer on top of liveness detection. The number is generated fresh for every session. The customer cannot know it in advance. No recording made before the session could include it.
Liveness Check
The customer completes a liveness check confirming they are physically present and genuine before the White Paper Verification step begins.
Number Generated
Daksam Analytics generates a unique 6-digit number for the session the moment the White Paper step begins. The number is specific to this session and cannot be predicted in advance.
Number Written on Paper
The customer writes the 6-digit number on a blank piece of paper. The number is unique to this session. It could not have appeared in any recording made before the session started.
Selfie Taken Holding the Paper
The customer takes a selfie holding the paper with the written number clearly visible. The system captures both the face and the number in a single image.
Number and Face Verified
The system reads the number from the paper and confirms it matches the session-generated number. The face in the selfie is matched against the liveness capture. Both must pass for verification to complete.
CAPABILITIES
Session-Specific Proof That a Recording Cannot Replicate.
Every capability below contributes to a verification that confirms the session was live, the person was present, and the face in the selfie matches the liveness capture.
Liveness Detection
Confirms the customer is physically present before the White Paper step begins. Runs as the first layer of the verification before the number is generated or shown.
Session-Specific Number Generation
A unique 6-digit number generated by Daksam Analytics for every session. Cannot be predicted, reused, or known by the customer before the session begins.
Number Recognition
The system reads the number written on the paper in the selfie and confirms it matches the number generated for that specific session. Mismatches are flagged immediately.
Face Match
The face in the selfie holding the paper is matched against the face from the liveness check. Both must confirm the same person for the verification to pass.
White-Label Presentation
The full verification flow carries your institution’s branding. Customers see your name, your colours, and your interface throughout with no Daksam Analytics branding visible at any point.
SDK Integration
The full verification flow carries your institution’s branding. Customers see your name, your colours, and your interface throughout with no Daksam Analytics branding visible at any point.
WHY CHOOSE US
Session proven live. Face confirmed present. Recording ruled out.
Four reasons organisations choose Daksam Analytics White Paper Verification when standard liveness is not enough.
Defeats Pre-Recorded Attacks
The 6-digit number is generated fresh for every session by Daksam Analytics at the moment the White Paper step begins. The customer cannot know it before the session starts. No recording made before the session could include it. A pre-recorded video of the customer cannot pass White Paper Verification because the number that needs to appear on the paper did not exist when the recording was made.
- Number generated fresh at the start of every individual session
- Cannot be predicted or known by the customer before the session begins
- No pre-recorded video can include a number that did not exist when it was made.
Defeats Deepfake Attacks
A deepfake face is generated from existing images or video. It cannot respond to a number it has never seen. White Paper Verification requires the person in the selfie to be holding a paper showing the session-specific number. A deepfake cannot produce that paper. The face match then confirms the person holding the paper is the same person who completed the liveness check at the start of the session.
- Deepfake faces cannot produce the session-specific paper the selfie requires
- Face match confirms the person holding the paper matches the liveness capture
- Two-layer check that an AI-generated face cannot pass simultaneously.
Verified User Participation
Before White Paper Verification begins, the applicant provides consent through the standard consent flow. The session-specific verification then confirms that the same applicant actively participated in the verification, providing an additional layer of assurance beyond the initial consent.
- Confirms active participation after consent is provided
- Verifies the applicant completed the verification personally
- Supports stronger audit trails for regulated workflows
White-Label by Default
The White Paper Verification flow carries your institution’s branding throughout. Your customers see your name, your colours, and your interface at every step from the liveness check through to the final confirmation. No Daksam Analytics branding appears at any point. Organisations maintain complete brand consistency through the most robust verification step in their journey.
- Full white-label presentation across every screen in the verification flow
- Your brand, colours, and interface visible at every step
- No Daksam Analytics branding visible to the customer at any point.
SDK Integration
White Paper Verification integrates via SDK into your existing app or website. Trigger it at the point in the customer journey where the strongest proof of a live session is needed, before signup, after signup, or at a specific high-value action deep inside the flow. No rebuilding required. The SDK handles the liveness check, number generation, selfie capture, number recognition, and face match.
- SDK integrates into any point in your app or website without rebuilding
- Trigger before signup, after signup, or at any high-stakes moment
- Works alongside other Daksam Analytics products in the same flow.
FAQ
What compliance and risk teams ask about White Paper Verification.
White Paper Verification proves three things. First, that a real person was physically present during the session, confirmed by the liveness check. Second, that the session was live at the moment it occurred, proved by the presence of a session-specific number that did not exist before the session started and therefore could not appear in any pre-recorded video. Third, that the person holding the paper with the number is the same person who completed the liveness check, confirmed by the face match between the selfie and the liveness capture.
Daksam Analytics generates the number fresh at the moment the White Paper step begins in the session. The customer cannot know the number before the session starts. It is unique to that session and cannot be reused or predicted. Once the session is complete the number is no longer valid for any other session.
A pre-recorded video is made before the session begins. The session-specific number generated by Daksam Analytics did not exist before the session started. There is no way for a recording made in advance to include a number that had not yet been generated. When the system requires the customer to hold a paper showing that number, a pre-recorded video cannot pass the check.
Via SDK. The check integrates into any point in your existing app or website without requiring you to rebuild your flow around it. Your product team decides when the verification triggers. The SDK handles the liveness check, the number generation, the selfie capture, the number recognition, and the face match. The result is returned to your system the moment verification completes.
The session was live. The face was present. The recording cannot replicate it. Book 30 minutes and we will show you the full White Paper Verification flow running, how the SDK integrates into your app or website, and what the white-label verification screen looks like for your customers.