By Prove

Prove Unified Authentication

Persistent device-based cryptographic authentication for returning users, with risk-triggered additional checks.

The offering

What Prove Unified Authentication does

Prove Unified Authentication recognises returning users through cryptographic keys tied to their devices. The supplier describes passive verification across sessions and channels, with step-up when risk signals require it. It also addresses lifecycle events such as device or phone-number changes. The current iGaming page names the offer alongside Pre-Fill in a BetMGM declaration.

Define which actions can use a recognised-device result and which require stronger evidence. Test account recovery, a new device, changed phone details and sensitive payment settings. Agree the fallback and challenge behaviour when trust cannot be established. Bind the result to your session and account controls, and retain the evidence needed to explain a permitted or rejected action.

Who should explore it?

Operators and platform teams adding persistent identity authentication to returning-player journeys.

  • Authenticate a returning player during account access
  • Request another check for a higher-risk account action

Documented capabilities

  • Device-bound cryptographic keys
  • Persistent session/channel recognition
  • Risk-based step-up
  • Device and phone lifecycle handling

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

Product details

Authentication role
Recognise returning users and orchestrate authentication through the account lifecycle.Source
Authentication method
Device-based cryptographic key binding and passive verification, with risk-triggered step-up.Source
Lifecycle scope
Sessions, devices and channels, including device or phone-number changes; confirm implemented flows.Source
Identity lifecycle
Returning-user authentication is marketed alongside Pre-Fill onboarding in the iGaming offer; scope the two journeys separately.Source

Delivery & commercial details

Delivery & integration
Connect device enrolment, recognition and step-up to the operator’s account/session flows; agree supported channels, lifecycle events and fallback.
Pricing
Request a proposal covering authentication volume, device lifecycle, step-up, recovery and support. No performance or cost-saving claim is treated as a contractual outcome.

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

Buyer questions, answered

When does it request a further check?

The product describes passive device-based verification as the default and step-up when risk signals require it. Define those conditions for each operator action.

Source
Does it address a changed device or phone number?

The supplier describes persistent recognition through device and number changes. Confirm enrolment, recovery and fallback behaviour for the selected implementation.

Source