For a Brazilian gaming operator with approximately 5,000 monthly active players, checking a person during onboarding was only part of the requirement. The compliance team also needed to be able to retrieve a clear record showing that the checks were completed before the player started playing.
The operator uses Checklynx during every player onboarding. The process brings together screening, an identity-verification integration supplied by Checklynx and an integration with the Brazilian government's SIGAP system. Each control answers a different question, while the resulting record shows when the checks took place in relation to access.
The customer asked us not to publish its name, but agreed that we could describe this onboarding process.
The proof problem behind a player check
A completed check has limited value during regulatory scrutiny if the operator cannot later connect it to the right player and the right point in the onboarding journey. A result in one system, an identity response somewhere else and an undocumented eligibility query leave the team with a reconstruction exercise: it may know that work took place, but still need to establish whether it happened before play began.
That timing is central to this customer's implementation. The operator wanted the checks to form part of player onboarding itself and to retain a time-stamped, retrievable record of their completion. The evidence therefore supports two operational needs at once: handling the onboarding decision at the relevant moment and explaining the sequence later if the regulatory body asks.
Three distinct controls in one onboarding flow
The Checklynx implementation combines three controls without treating them as interchangeable.
Identity verification establishes that the person entering the onboarding process is the person they claim to be. Checklynx supplied the identity-verification integration used in this workflow.
Screening applies the operator's configured checks to the player. Its role is to produce information for the operator's review and onboarding process.
The SIGAP check addresses a separate governmental eligibility question. SIGAP is Brazil's Sistema de Gestão de Apostas, operated within the Ministry of Finance framework for regulated fixed-odds betting. Its Módulo de Impedidos supports checks of relevant restrictions on participation using the person's CPF, Brazil's individual taxpayer identifier.
Identity verification confirms who is applying. Screening supports the operator's configured risk checks. The Módulo de Impedidos response shows whether that CPF is subject to a relevant government restriction. Together, they give the operator a record of the controls completed before access.
The Ministry of Finance's Módulo de Impedidos page explains the module within SIGAP, while the official SIGAP technical documentation describes the government system and its integration resources.
Evidence created before the player starts playing
For this operator, the most important outcome is not the number of checks completed. It is the ability to retrieve evidence that connects the player onboarding with the checks and their timing.
The workflow records completion before the player is permitted to start playing. If the operator later needs to explain the onboarding, its compliance team can return to a time-stamped record rather than relying on a recollection of the process. The record supports the sequence the operator needs to demonstrate: the player entered onboarding, the relevant controls were completed and access followed afterwards.
This also gives compliance and operational teams a shared reference point. The onboarding process can use the completed checks at the time access is considered, while the same record remains available for later review. The value is practical even without a claimed time or cost saving: evidence is created as part of the control instead of being assembled only when someone requests it.
Brazil's Ministry of Finance guidance on SIGAP impediment checks connects the check with onboarding and calls for consultation records suitable for audit. That lets the operator keep the government check alongside its other onboarding evidence.
A clearer operational handoff
The completed record creates a clearer handoff between the systems involved in player onboarding and the people responsible for compliance. Instead of treating identity verification, screening and the government eligibility query as unrelated technical responses, the operator can view them as separate controls attached to one onboarding event.
That distinction also avoids overreading any single result. Identity verification establishes identity, the SIGAP response addresses the relevant governmental eligibility restriction and screening applies the operator's configured checks. The operator brings the three results into its own decision process and retains the evidence behind that process.
At this scale, the operator wanted a consistent route through onboarding: every player follows the same checks, and the resulting evidence can be retrieved later.
The Checklynx solution for iGaming and gambling operators shows how player screening, review and evidence can fit into the wider operation.
Make onboarding evidence part of the control
For gaming operators, the useful design question is not only whether an integration can return a result. It is whether the onboarding process can preserve a record showing which checks were completed, for which player and before access was granted.
Talk to Checklynx about player onboarding to discuss screening, identity-verification integration, SIGAP checks and the evidence your team needs to retain.
This story describes one operator's workflow. It is not a regulatory approval, compliance guarantee or promise of a particular operational result.