| EveryMatrix8.8 | | Platform-orchestrated integrations The platform connects identity or risk services. Integration does not make the underlying engine proprietary. | | EveryMatrix Identity Verification suite plus integrated third-party partners The stack covers facial and document verification, 1,000+ sanctions lists and 3,000+ risk databases; the complete underlying vendor set remains unresolved. | | | Yes Bonus Guardian cross-references device data and fingerprints, IP patterns, registration velocity, and behavioral signals to detect multi-accounting and coordinated abuse. | Yes Bonus Guardian is the clearest shipped AI fraud capability; payment risk also includes rules-based monitoring. | | | | Yes Rules, alerts, role-based actions, manual review, and Bonus Guardian restrictions are supported. | |
|---|
| Playtech8.7 | | Platform-orchestrated integrations The platform connects identity or risk services. Integration does not make the underlying engine proprietary. | Yes Delivered through integrated partners rather than a Playtech-built engine. | LexisNexis, RiskNarrative, Jumio, GBG, SEON, Acuris Risk Intelligence, Checkin.com, TrueLayer Integrations available through Playtech Open Platform, not all live for every operator. | | | | | | | | Yes Real-time fraud detection runs through the Featurespace ARIC engine built into IMS, which flags deposits, withdrawals and account changes for review. | |
|---|
| SOFTSWISS8.3 | | Platform-orchestrated integrations The platform connects identity or risk services. Integration does not make the underlying engine proprietary. | | Configurable integrations KYC runs through configurable third-party integrations rather than one bundled vendor; no default provider is established. | Yes Covers AML and payment-system abuse through platform triggers and the anti-fraud team. Payment abuse and money laundering each made up roughly 10 percent of fraud the team stopped. | | | Yes Machine learning flags suspicious cases in near real time and sends them to the anti-fraud team, which makes the final call. Not a fully automated decision engine. | Yes Bonus abuse is the biggest category the anti-fraud team handles, around 70 percent of fraud it stops. | Yes Covers duplicate-account blocking and collusion investigation. | | Yes Integrated anti-fraud system with automated triggers. Deeper case investigation is largely handled through the optional Managed Services anti-fraud team. | |
|---|
| Pragmatic Solutions8.2 | | Mixed platform and integrated controls A platform workflow is established alongside external identity or risk services; ownership is resolved field by field. | Yes Platform has a built-in KYC, AML and fraud control module. Rule-based KYC, device fingerprinting, and AML workflows aligned to EU 5AMLD and Brazil's 2025 decree, plus integrations with third-party ID verification providers. | Signicat; ComplyAdvantage; GBG; IDnow; HooYu; iDenfy; other integrated providers | Yes AML transaction monitoring aligned to EU 5AMLD and Brazil's 2025 decree. | Yes Required regulated flows can use external identity providers; exact native workflow depth remains unresolved. | Yes Available through selected external fraud and identity integrations; universal native coverage was not established. | Yes AI depth comes from selected external risk tools; the native fraud module's model stack remains unresolved. | Yes Bonus rules and integrated fraud tools can detect abuse; no native model specification was established. | Unresolved No specific native multi-account detection control was established. | Partial Core KYC controls and integrations are present; native case-management depth remains unresolved. | Partial Core fraud rules and integrations are present; native case-management depth remains unresolved. | Yes Historical data, dictionary and lineage support operational and regulatory audits. |
|---|
| Aristocrat Interactive8.1 | | Platform-orchestrated integrations The platform connects identity or risk services. Integration does not make the underlying engine proprietary. | Yes Yes — integrated KYC and AML plus optional managed operations. | Unresolved The PAM integrates third-party KYC services; the provider roster is project-specific. | | | Unresolved No current named device-intelligence capability or supplier is established. | Unresolved Fraud monitoring is available, but AI-specific detection is not established in the retained PAM. | Yes Managed risk and fraud operations support bonus-abuse controls; the rules and product boundary remain unresolved. | Yes Managed fraud operations and regulated PAM controls support multi-account detection; exact methods remain unresolved. | Partial KYC integrations and managed compliance support case handling, but the tooling may be third-party and varies by deployment. | Partial Managed fraud operations support case handling, but the tooling may be third-party and varies by deployment. | Yes Regulated PAM and lottery operations support auditable event records; exact operator-visible coverage remains unresolved. |
|---|
| Altenar8.0 | | Platform-orchestrated integrations The platform connects identity or risk services. Integration does not make the underlying engine proprietary. | | | Yes The PAM includes ongoing fraud and transaction monitoring. | Yes Sumsub document and liveness verification supports age verification; the exact age-check workflow remains unresolved. | Unresolved Shared-IP and account-event monitoring do not establish device fingerprinting. | Yes AI fraud-prevention, match-fixing and automated-AML applications operate alongside behavioural fraud controls. The exact production models and decision boundaries remain unresolved. | Yes The native bonus engine includes automated abuse detection and behavioural analysis that identifies suspicious patterns and blocks fraud. Detection precision and false-positive rates remain unresolved. | Yes Shared-IP, failed-payment and sensitive-account-change monitoring provide defensible cross-account detection signals; exact matching logic remains unresolved. | | | Yes The current retail stack includes full audit tracking for settlements, reprints, adjustments and voids, and jurisdictional reporting maintains clean data trails. Retention and tamper-protection specifications remain unresolved. |
|---|
| Kambi8.0 | | Platform-orchestrated integrations The platform connects identity or risk services. Integration does not make the underlying engine proprietary. | Yes The optional Kambi PAM explicitly includes KYC and identity verification; wagering-side profiling, fraud and integrity monitoring complement payment AML controls. | Experian, GBG, GeoComply, Hooyu, IDComply, Iovation, Shufti Pro, Sumsub, Trulioo and others The inherited integration estate includes 17 KYC providers. Operators choose the relevant stack by market. | Yes Kambi profiles betting activity and risk in real time, while the PAM and integrated payments layer cover account and transaction controls. | Yes Identity verification is part of the optional Kambi PAM; external-PAM operators retain their own age-verification workflow. | Yes Kambi processes unique device identifiers, operating system, browser, language, timezone, broad location and interaction history for access, risk and fraud purposes. | Yes AI-assisted detection of arbitrage, bonus abuse and suspicious betting patterns. | Yes AI trading and risk flag bonus abuse and arbitrage before/around bet acceptance. | Yes Part of player-profiling and risk on the betting side; player-identity dedup ultimately ties to the operator's PAM. | Yes KYC and identity verification are explicit PAM functions, with vendor integrations selected by the operator. | Yes Core sportsbook controls include liability management, stake acceptance, player profiling and 24/7 integrity monitoring; the optional PAM adds account, KYC and payment-case context. | Unresolved Retained audit-log fields, access model and retention term remain unresolved. |
|---|
| Light & Wonder7.7 | No named module established | Platform-orchestrated integrations The platform connects identity or risk services. Integration does not make the underlying engine proprietary. | Yes Yes through third-party integrations and OPS workflows. | Multiple market-specific providers | Yes Supported through payments/risk integrations. | Yes Yes through KYC integrations. | Yes Available through fraud/geolocation integrations. | Yes Third-party integration; no native L&W AI model is established. | Yes Through operator/risk integrations. | Yes Through KYC/fraud integrations. | Partial Via integrated KYC providers and OPS workflows. | Partial Via third-party risk integrations and OPS tooling. | |
|---|
| Pariplay7.5 | No named module established | Operator/PAM-side Identity, AML and player-fraud controls sit outside this supplier's established product scope. | No No — operator/PAM responsibility. | Unresolved No KYC product. | No No operator AML/payment monitoring. | No No — operator/PAM responsibility. | No No native player-fraud product. | | No No — operator risk stack responsibility. | No No — operator KYC/fraud stack responsibility. | Unresolved Operator/PAM responsibility. | Unresolved Operator/risk-stack responsibility. | Yes Yes for regulated administrative and game-system operations. |
|---|
| Digitain7.1 | No named module established | Mixed platform and integrated controls A platform workflow is established alongside external identity or risk services; ownership is resolved field by field. | | Digitain native KYC workflow plus configurable third-party integrations; provider selection varies by project Built-in identity and document handling works with third-party compliance integrations; the KYC provider and market-by-market matrix remain unresolved. | | Yes Built-in KYC/AML and regulated-market onboarding include age checks; exact provider and coverage are deployment-specific. | Yes Device and payment-method checks use prior fraud and abuse history; the fingerprinting vendor remains unavailable. | No Fraud controls use advanced algorithms and real-time pattern detection, but an AI classification is not established. | Yes The casino stack includes real-time bonus-fraud detection. | | | | |
|---|
| White Hat Gaming7.1 | - Managed Operations & Compliance
| Platform-orchestrated integrations The platform connects identity or risk services. Integration does not make the underlying engine proprietary. | Yes Electronic identity verification, AML controls and managed compliance are part of the platform/service. | Shufti plus White Hat eIDV/AML workflows The Shufti relationship was extended in December 2025; White Hat remains responsible for orchestration and licensed-operator controls. | | Yes Required across White Hat's licensed and supplier-approved regulated deployments. | Unresolved Document and face verification are established, but device fingerprinting in the deployed PAM stack is unresolved. | Yes AI-assisted fraud prevention is available through the integrated Shufti identity and biometric stack. It is partner-delivered rather than White Hat-native. | Yes The bonus engine, withdrawal rules and risk monitoring support abuse controls; the exact rule set remains unresolved. | Yes White Hat maintains duplicate-identity controls, but 2021 name-matching defects contributed to operator settlements. | Yes Electronic ID verification, AML workflows, Shufti document/biometric checks and managed compliance are integrated. | Yes Real-time risk alerts and managed risk/fraud services support investigation workflows; detailed queues and rules remain unresolved. | Yes Regulated operations and end-to-end interaction traceability require durable records; exact admin-log coverage remains unresolved. |
|---|
| GR8 Tech7.0 | | Platform-orchestrated integrations The platform connects identity or risk services. Integration does not make the underlying engine proprietary. | | GR8 orchestration; underlying identity vendors unresolved | | | Yes Trusted-device, IP/phone-country and multi-account risk signals are available; the fingerprinting provider and exact signal set are contract-specific. | | | | Yes KYCAid and SumSub multiforms allow an individually rejected document to be resubmitted without restarting the complete verification flow. | | |
|---|
| GiG6.8 | | Platform-orchestrated integrations The platform connects identity or risk services. Integration does not make the underlying engine proprietary. | | Crucial Compliance, KYCP and market-specific identity/KYC partners through GiG Broker | | | | | | | Yes CoreX and ServiceX support KYC/EDD case handling and integrate automated risk scoring. | | |
|---|
| Bragg Gaming Group6.7 | No named module established | Platform-orchestrated integrations The platform connects identity or risk services. Integration does not make the underlying engine proprietary. | | Third-party KYC tools integrated; the standard provider set is contract-specific | Yes Yes — AML/payment monitoring. | Yes Yes as part of KYC/onboarding. | Yes Third-party risk tooling can be integrated; no named native device-fingerprint product. | No Rules and behavioural monitoring are current; AI-specific depth is not established. | Yes Fraud/risk rules can flag bonus abuse. | Yes KYC, account and fraud rules support duplicate-account detection. | Yes Yes — KYC tools and player-protection workflows are part of the PAM. | Yes Yes — fraud and risk rules operate in the PAM. | |
|---|
| Slotegrator6.3 | - Telegram Casino
- Platform engagement, BI and risk modules
| Platform-orchestrated integrations The platform connects identity or risk services. Integration does not make the underlying engine proprietary. | | Slotegrator workflow; external identity-verification vendor unresolved | | Yes Age requirements can be configured in KYC; the external verification provider remains unresolved. | Yes Device signals are used for duplicate and multi-account detection. | No The shipped AI assistant summarizes existing risk metrics; fraud detection itself remains rule-, behavior-, IP- and device-based. | | Yes Detection uses IP, personal and device signals. | Yes KYC case management includes configurable documents, risk requirements, ongoing monitoring and stored results. | Yes Risk categories, rules, alerts and player-level actions are supported; AI mainly summarizes existing signals. | Yes Histories and action notes exist; immutability and retention specifications are private. |
|---|
| BetConstruct6.0 | No named module established | Platform-orchestrated integrations The platform connects identity or risk services. Integration does not make the underlying engine proprietary. | | BetConstruct Umbrella; external identity vendor not named Umbrella provides the rules, risk scoring, case data and workflow. The document and biometric verification engine remains unresolved, so not every identity check can be treated as built in-house. | | Yes Comes through identity KYC at registration rather than a separately named age check. | Yes The Swarm API includes an AFEC device-fingerprint parameter in session data; Umbrella also detects linked and multiple accounts. | | | | | | |
|---|
| SoftGamings5.8 | No named module established | Platform-orchestrated integrations The platform connects identity or risk services. Integration does not make the underlying engine proprietary. | Yes KYC and fraud checks run through a Sumsub integration rather than a built-in engine. | | Yes Covered through Sumsub payment fraud prevention and player behavior monitoring. AML transaction monitoring is not named separately by the vendor. | Yes Handled as part of the Sumsub KYC identity checks. | Yes Partial through Sumsub and fraud partners. | Yes Comes from the Sumsub integration and the sportsbook AI risk engine, not a single in-house module. | | Yes Yes through identity checks and bonus-abuse controls. | Partial Staff can review player documents and set a KYC level, but SoftGamings leaves the actual KYC verification vendor to the operator. | Partial The payment layer includes fraud resistance; dedicated fraud case-management and investigation tooling is not established. | |
|---|
| Soft2Bet4.8 | | Platform-orchestrated integrations The platform connects identity or risk services. Integration does not make the underlying engine proprietary. | | Entrust/Onfido, SEON Entrust/Onfido handles document and facial identity verification; SEON handles digital-footprint, device, and fraud-risk signals. | | Yes Entrust/Onfido verifies government ID and selfie/face match. Consistent application across every linked brand remains disputed. | Yes SEON device intelligence is integrated into login and fraud workflows. | Yes SEON provides real-time risk scoring at registration, login and deposit. | Yes SEON detects multi-accounting and welcome-offer exploitation. | | | | |
|---|