By Prove

Prove Pre-Fill

Phone/device-linked onboarding that returns verified identity attributes for customer review and application pre-fill.

The offering

What Prove Pre-Fill does

Prove Pre-Fill authenticates the phone relationship, resolves identity through Prove’s graph and returns attributes to populate an application. The documented flow supports a qualifying phone-only start, with a challenge path when more information is needed. The customer reviews the returned data and consents before completing the journey. Prove explicitly markets the offer for sports betting and iGaming registration.

Select the attributes and screening checks your onboarding requires. Test the phone/device match, changed data, fallback and unavailable coverage against your own account flow. Define how an exception reaches review and when the account may be activated. Verification output supports that decision; your operator policy and implementation determine the final account status.

Who should explore it?

Operators reducing manual identity-data entry while retaining a defined player-verification journey.

  • Populate identity fields during player registration
  • Escalate an onboarding flow when phone-only verification is unavailable

Documented capabilities

  • Phone/device relationship authentication
  • Identity-graph attribute resolution
  • Application pre-fill for review and consent
  • Challenge fallback

Reported in the linked public sources. We have not independently tested these capabilities.

Product details

Verification role
Authenticate a phone/device relationship and return trusted identity attributes for onboarding.Source
Verification methods
Prove Key, Mobile Auth or SMS fallback, followed by identity-graph resolution.Source
Returned data
Identity data is returned to pre-fill the application for customer review and consent.Source
Gaming application
Explicit sports betting and iGaming onboarding offer; confirm eligible countries and returned attributes.Source
Screening scope
Integrated sanctions/PEP screening is described; select the required checks and operator decision policy.Source

Delivery & commercial details

Delivery & integration
Integrate the phone and device authentication flow with the application, returned attributes, consent and fallback screens. Interface and market scope require a technical proposal.
Pricing
Request a quote for countries, check combinations, API volume, fallback and support. Separate optional screening from the base pre-fill flow.

Confirm market availability, rights, service levels and contractual terms for your implementation. API availability alone does not establish a named integration.

Buyer questions, answered

Does every user complete the phone-only flow?

No. The product describes a qualifying challengeless path and fallback to standard Pre-Fill with an additional identifier, such as date of birth, when needed.

Source
Does the user review the returned identity information?

Yes. The flow returns trusted identity data for application pre-fill, review and consent before completing onboarding.

Source