Client profile
Spin Palace Group, a Malta-based licensed casino and sportsbook with 310 staff.
Challenge and scope
A player screening hit takes 12 minutes to review in the baseline. The resulting queue delays withdrawals against a 48-hour service level.
A player can have a screening hit while a withdrawal is already pending. A team that closes the alert and updates the payment queue separately can leave the two statuses out of sync. This creates unnecessary follow-up and makes it harder for compliance to see which payment is waiting on which decision.
Delivery workflow
Triage 14,200 monthly hits using the operator’s screening rules across six markets. Record alert dispositions and escalate unresolved matches to the client’s compliance team before a restricted account or payment decision is made.
Apply the operator’s approved match criteria to available identifiers and document the evidence for the disposition. Link the screening record to the affected player and withdrawal where applicable. Route unclear or potentially genuine matches with the watchlist reference, identifiers compared, and reasons for escalation.
Maintain a review list of held withdrawals, active alerts, deadlines, and client decision owners. Sample low-risk dispositions by market and include a regular review of escalations that were returned for missing details. Log the operator’s decision reference so payments staff can see the status of the case in the approved system.
Delivery team
Poland, about 12 FTE. 1 compliance lead, 2 analysts and 9 screening associates.
Systems and tools
World-Check, internal player management system.
Client decision rights
The operator makes player-account and responsible-gambling decisions and owns suspicious activity reporting.
Early milestone
The week 3 record shows six minutes per screening hit.
Outcomes
Company-reported results, with the baseline, measurement window and supporting record described for each measure.
| Measure | Baseline | Result | Window | Supporting record |
|---|---|---|---|---|
| Screening time per hit | 12 min | 2.5 min | 4 months | Player system report |
| Withdrawals blocked by screening | 340 / month | 28 / month | 4 months | Payments report |
| Screening audit findings | 4 | 0 | 4 months | Internal audit record |
Interpreting the results
The drop from 340 to 28 withdrawals blocked per month needs the withdrawal and alert volumes for context. Review screening time, held-withdrawal aging, and audit sample findings together. A shorter review can coexist with a required hold, so capture the alert and payment event timelines independently.
Recommendations for new clients
For operators spanning several jurisdictions, agree the timing rules for a hit and a held withdrawal. Have compliance re-review a sample of cleared alerts for each market.
Sample ordinary name collisions, incomplete identity records, and alerts that require compliance review across the licensed markets in scope. Define the evidence that allows triage to close a case and who responds to a held payment. Have the compliance owner review both cleared and escalated examples before increasing coverage.