AU10TIX Identity Verification Suite
Document, biometric and identity-data checks in a configurable verification suite.
Supplier popularity25%By ID-Pal
ID-Pal Once
Biometric reverification of a stored identity for returning customers, using a liveness check and the earlier submission.
The offering
What ID-Pal Once does
ID-Pal Once reuses an earlier identity submission when the business needs to verify a returning customer. The documented sequence references the stored ID, asks the customer to complete liveness in the ID-Pal app and compares the live face with the stored submission. The supplier’s current explanation names iGaming, explicit consent and checks on the original document’s validity.
Define when the prior submission remains suitable and when a full new verification is required. Connect the stored identifier and result to the correct player account, and test changed or expired evidence as well as unsuccessful liveness. The published current scope is reuse between an individual and one business; a wider identity-sharing network is described as a future direction. Agree that boundary and the permitted account actions in the contract.
Who should explore it?
Operators needing a repeat identity check for an already-verified player within the same business.
- Reverify an existing player without repeating the initial document upload
- Apply a biometric check for an agreed sensitive account action
Documented capabilities
- Stored-submission reference
- App-based liveness check
- Live-face match to previous evidence
- Consent and validity-based reuse
Reported in the linked public sources. We have not independently tested these capabilities.
Product details
- Reverification role
- Repeat identity verification against a stored, earlier submission.Source
- Biometric process
- Liveness in the ID-Pal app followed by live-face matching to the stored submission.Source
- Request flow
- The business references the stored ID to initiate a customer recheck.Source
- Current reuse boundary
- Current reuse is between the individual and a single business; a wider consent-driven network is presented as future.Source
- Reuse controls
- Explicit consent, biometric binding and background checks such as original-document validity are described.Source
Delivery & commercial details
- Delivery & integration
- Business requests a recheck using the stored ID; the customer completes app liveness and the face is matched to the earlier submission. Define the returned status and failure route.Source
- Pricing
- Request the reusable-verification terms, initial-verification dependency, recheck volume, validity rules and support scope. Published speed comparisons are not procurement acceptance criteria.
Confirm market availability, rights, service levels and contractual terms for your implementation. API availability alone does not establish a named integration.
Buyer questions, answered
What does the returning customer provide?
The documented flow requests a liveness check and matches the live face to the stored identity submission, rather than repeating the initial document upload.
SourceCan the identity automatically be shared across unrelated operators?
The current explanation limits Once reuse to an individual and one business. A wider consent-driven network is described as future, so broader reuse needs separate confirmation.
Source