iDenfy and NuxGame: Identity Verification Inside the Casino Platform

Verification is a daily operational task rather than a launch-day checkbox for a licensed operator. Weak checks lead to blocked payments, penalty exposure, and fraud losses that surface months later. The AML and KYC module carries document analysis, face matching, and ongoing screening through one configuration layer.

This page covers what the partnership gives operators rather than a product tour. It sets out where checks sit inside a turnkey casino build, what the technical scope is, and which market rules it answers to. Announcement details are in the NuxGame partnership statement.

What Is iDenfy?

iDenfy is an identity verification and fraud prevention company founded in Kaunas in 2017. Its AI-powered identity verification runs alongside an in-house team that reviews every result, not only flagged cases. The company helps businesses comply with regulations and directives across fintech, crypto, e-commerce, and the gaming sector. Manual review at that volume is unusual among vendors of this size.

Pricing runs per approved check rather than per attempt, so rejected submissions carry no charge. iDenfy reports savings of up to 75% against per-attempt billing, though results vary by traffic mix. Where user onboarding spans emerging markets and document quality varies, that changes the cost model rather than only the audit posture. A verification solution priced this way rewards clean traffic instead of penalizing it.

What the Integration Covers

Scope covers the whole onboarding path rather than a single document check. A new player submits identity documents, clears a biometric check, and passes screening before the account opens. Each stage of the verification process returns a status the platform can act on. Operators decide which stages apply in which market.

Screening does not stop once a player is onboarded. Watchlist checks run on a continuing basis, so a status change after signup surfaces in real-time. Risk profiles built during registration stay attached to the player record, which helps prevent fraudulent accounts from being funded at all. Support and risk staff read the same history without exporting data elsewhere.

Identity Verification Flow Inside the NuxGame Platform: API, Webhooks, and Player Status

The online ID verification flow starts at registration and ends with a status written to the player record. NuxGame calls the iDenfy API, receives a session token, then hands the player to a hosted or embedded screen. SDKs and plugins are fully white-labeled, so the journey carries operator branding rather than vendor branding. Results return by webhook in real-time rather than by polling.

Status handling is where integration quality shows, because AI clears most submissions and the queue exists for the rest. A pending result should not block actions local rules still permit, and a rejection should route to review rather than a hard account close. The platform maps each outcome to a player state, a permitted action set, and a back-office queue. Support agents then see the reason code without opening a second system.

Data Residency, ISO 27001 Scope, and eIDAS Conformity

All processing and storage stays inside the EU, which matters for operators answering to European regulators. The ISO/IEC 27001:2022 certificate covers development and provision of the software itself, not only corporate IT. iDenfy has held it continuously since 2020, and the most recent surveillance audit closed without non-conformities. SOC 2 Type II adds an independently audited twelve-month view of the same controls.

Conformity under eIDAS is the part most vendors cannot show. The declaration covers remote authentication by image identification, assessed against Regulation (EU) 910/2014, ETSI TS 119 461, and ISO/IEC 30107-3:2023. That last standard governs presentation attack detection, which is how liveness detection technology gets tested. An auditor therefore gets a documented answer rather than a vendor claim.

Verification Spec Table

Compliance Coverage by Market

Regulatory compliance is not one standard but a set of local variations. UK licensees must establish a customer’s identity before that customer is permitted to gamble, under License Condition 17.1.1. Name, address, and date of birth are the stated minimum, and a withdrawal request cannot trigger checks the operator could reasonably have run earlier. Malta applies a risk-based approach with similar intent and more operator discretion.

The EU picture consolidates in 2027. The EU AML Regulation applies directly from 10 July 2027 and sets one due diligence standard across all 27 member states, replacing national variation in money laundering rules. US states each run their own supplier and player requirements, while Brazil and the UAE add further variation. Compliance requirements should be configured per market, which is how operators stay compliant as they add licenses.

How Operators Enable iDenfy With NuxGame

Enablement runs as a configuration task rather than a development project, because the connection already exists. Commercial scope gets agreed first, then the customer onboarding process is mapped per market and player segment. Sandbox work follows, covering approval, rejection, and resubmission paths. Production release comes after back-office queues and reason codes are checked.

1. Scope agreement covering identity checks, screening, and business verification where needed
2. Sandbox access and test flows for approval, rejection, and resubmission
3. Verification checks configured per market, currency, and player segment
4. Webhook and player-status mapping into the platform
5. Back-office queue, reason codes, and support access
6. Age-gate and responsible gaming settings aligned to local rules
7. Production release with monitoring on pass rates and drop-off

Most of the work sits in decisions rather than code. Teams choose when the check fires, which markets need an active check, what a pending status permits, and who handles escalations. Those settings drive both conversion and audit outcomes. Product and risk leads should agree them together before go-live rather than after.

Put the Checks Where the Player Data Already Lives

The question for an operator is not whether identity checks are possible. It is whether they run as a separate project with its own vendor, contract, audit trail, and dashboard. Inside the NuxGame casino platform, the rules and the results sit next to the player record they act on. That placement is what makes the layer prevent fraud rather than only document it.

The team at NuxGame can map rules against your target markets and confirm what runs on day one. That review covers document coverage, active versus passive checking, pending-status behavior, and back-office queue design. Bring the person who answers the audit, because most of these decisions are theirs.