Context for review priorities.

Player risk intelligence and scoring, currently in development.

SIOR is in development. Not yet available.

74/ 100
Synthetic example of review priority. No live player data or scoring model runs in this illustration. A score is not evidence of fraud.

Structured signals.
Consistent review priorities.

The intended scoring approach is being developed. It is not a production-ready scoring service.

  1. Collect relevant signals

    Consider selected payment, wagering, gameplay and account information required by the intended model.

  2. Apply eligibility filters

    Define which players and activity enter the scoring process through supported operational filters.

  3. Structure the score

    Use a consistent Solvare-managed methodology to organise the available signals.

  4. Support the review

    Present the risk band and relevant signal categories for an operator to investigate.

A score needs
supporting context.

Relevant categories should help a reviewer understand what to investigate, without presenting a score as a definitive conclusion.

Payments

Relevant payment and transaction context.

Wagering

Selected sportsbook and wagering activity.

Gameplay

Relevant gameplay patterns and analysis context.

Account activity

Selected account attributes and activity signals.

Intended signal categories. No model weights or live scores shown.

Designed to support
operator judgement.

The methodology, supported controls and review experience may change during development.

Solvare-Managed Methodology

The intended core scoring formula is controlled and maintained by Solvare.

Supported Operator Controls

Selected operational filters, presentation choices and review criteria are intended to be adjustable by operators.

Investigation Support

The intended experience pairs review prioritisation with principal signal categories and operator oversight.

Tools with distinct roles.

Your workflow determines which tools and checks are relevant.

Each product can be considered independently. This is an illustrative relationship, not a required sequence. SIOR and AUTOW remain in development.

Discuss the direction
of SIOR.

Talk to us about review priorities and the context your team needs. SIOR is in development and not yet available.

Discuss SIOR