Map account and payment roles
Use the known legal identity behind the player account. Keep its reference with the chosen-source check.
Sanctions screening for gaming and casino teams
Run sanctions checks for patrons and business partners. Review possible matches and save your team’s reasons. Keep each result with the account or payout it belongs to.
Paid plans start at $59/month for 5,000 checks each month. API and review dashboard included. See pricing.
Customer onboarding
Identity verification and transaction monitoring remain separate.
Built around your work
A patron can share a name with a listed person. A score alone cannot resolve that question. The team needs the known facts, a reviewer, and a clear record before making its separate account or payout decision.
Use the known legal identity behind the player account. Keep its reference with the chosen-source check.
Compare dates and IDs at the level of detail the source provides. Missing days or months are unknown, not mismatches.
Save the review and required approvals. Keep age, identity, self-exclusion, fraud and payout checks in their own steps.
Put it into practice
A payout checkpoint reveals a similar name and a source with only part of a birth date. Staff need to know what to compare and who should follow up.
The review explains the match evidence. Your team still decides who can play and who can be paid. Responsible gaming checks remain separate.
Choose the parties and checkpoints required by your gaming policy. Collect the known details needed for each subject.
Run the selected-source checks and assign possible matches. Keep technical or source failures distinct from no-match.
Save what the review found. Finish the other required checks before your team decides on the account or payout.
In this invented example, an operator screens a patron at a checkpoint set by its policy. A source record has a similar name. The reviewer compares the player’s known details with the fields actually present in the record.
The source gives an incomplete birth date. An absent day or month is not a mismatch. The analyst requests useful evidence and explains the finding. The operator continues age, identity, payout, and responsible-gaming checks through its separate processes.
Scroll horizontally to compare every column.
| Work item | Screening evidence | Boundary |
|---|---|---|
| Patron identity | Person subject with known facts. | Screening does not authenticate identification documents. |
| Candidate | Source identity fields, conflicts, and missing facts. | A similarity score does not settle the case. |
| Payout checkpoint | Retained screening and required review approvals. | Eligibility, behavioral monitoring, and payout decisions remain separate. |
Start free with 250 live screenings. Use them in the API or dashboard. Your first workspace gets this allowance once, with no monthly reset. No credit card is needed.
Try a patron check with facts your team may share. Include a common name or partial birth date. Ask the reviewer to show what evidence could resolve a possible match.
The optional demo uses made-up records for a quick tour. Use the sandbox to test errors without using live checks.
Count checks at the stages your policy requires, including repeat checks and distinct payment parties. Compare the expected workload with plans and confirm the lists in coverage. The demo shows the workflow, not a production customer result.
A new recipient may need a separate check from the person who holds the player account. Record the subject’s role and the relevant account or payout reference. The older result must remain tied to the person it actually checked.
The AML screening guide explains the scope of list screening. SanctionsKit is not a full casino AML system. It does not provide age verification, self-exclusion checks, responsible-gaming checks, or payment-pattern analysis.
TRY IT WITH YOUR TEAM
Check your sources, try a free live check and estimate your monthly cost.
Find your required sources, what they cover and when they were refreshed.
Explore coverageUse your free live checks to find possible matches. Compare the evidence and save a decision.
Start with 250 free checksCount new checks, rows in uploaded lists and repeat checks from monitoring.
See workload examples
Evaluate the fit
No. It helps with sanctions and watchlist screening and match review. Your team still needs to check identity and age, monitor transactions and file reports as part of its wider program.
No. It compares submitted facts with selected sources. Your separate process must verify the player and any required documents or age facts.
These are not advertised capabilities. A general watchlist label does not imply access to those databases. Confirm the exact source needed for each control and use the appropriate separate service.
Read the full source record and compare known dates and IDs. Missing detail is not a conflict. Gather useful evidence and keep the case unresolved if the facts do not support a conclusion.
Yes. Use the company subject type and compatible sources for the supplier. Keep its role and reference distinct from patron checks. Your policy determines which business partners need review.
See SanctionsKit in action
Start with 250 free live checks. Use the API or dashboard to review matches and save decisions. Choose a paid plan when you need more checks.