Common Compliance Situations

Article Title

Common Compliance Situations

Category
Fraud / Compliance Handling

General Information

There are several common compliance-related scenarios that may place restrictions on a player’s account. These situations typically involve security reviews, payment disputes, or verification requirements.

Agents must:

• Review account notes carefully
• Follow Compliance instructions when available
• Provide clear, neutral, and non-accusatory communication

Purpose / Objective

To guide agents in identifying and handling common compliance situations, including escalation requirements and proper player communication.

Scenario / Use Case

A player contacts support because:

• Their account is restricted
• They cannot deposit or log in
• They were contacted about suspicious activity or payment issues

Common Compliance Cases

1. High Depositor Review

Trigger:

• Multiple deposits OR high-value deposits

Action:

1. Verify the player
2. Confirm recent deposits with the player

Outcomes:

• ✅ Player confirms deposits

  • Add notes to existing case
  • Return case to Compliance

• ❌ Player denies deposits

  • Follow Unauthorized Activity protocol

Key Messaging:

• Emphasize security purpose of the review

2. Payment Disputes (Chargebacks)

Definition:

• Player disputes a transaction with their bank
• Funds are reversed from lottery account

If Player is Aware of Dispute

• Advise:
  • Contact bank to cancel/reverse dispute
• Requirements for reinstatement:
  • Government ID
  • Proof of ownership for each payment method

If Player is NOT Aware

• Advise:
  • Contact their bank for details
• Then follow reinstatement steps above

If Player Cannot Reverse Dispute

• Advise:
  • Submit documents anyway
  • Investigation may take up to 6 months

Important Notes

• DO NOT argue with the player
• NEVER guarantee account reinstatement
• Minimum review time: ~6 months
• Decision is made solely by Compliance/Accounting

Case Logging (Payment Disputes)

• Owner: Compliance
• Category: Fraud
• Subcategory: Chargeback
• Subject: Chargeback
• Resolved: Yes

3. Player Has Charges but No Account

Scenario:

• Player reports charges but claims no account exists

Action:

• Direct player to:
  • Their bank
  • Local law enforcement

4. Payment Method Issues (PMNM / CCNM / Sharing)

• PMNM/CCNM:

  • Follow Payment Method Name Mismatch protocol

• Payment Method Sharing:

  • Follow Error Code 909 protocol

5. Suspicious Behavior Flag

Action:

1. Check Compliance notes

• If notes exist:

  • Follow instructions
  • Update case

• If no notes:

  • Player must provide:
    • Verification form
    • Payment method ownership documents

Case Logging (Suspicious Behavior)

• Owner: Support
• Category: Fraud
• Subcategory: CC Name Mismatch
• Subject: Payment Method NM
• Resolved: Yes

6. Pending Investigation Flag

Action:

1. Check Compliance notes

• If notes exist:

  • Follow instructions

• If no notes:

  • Request verification form
  • Resend System ID email (if needed)

Key Messaging

• Emphasize:
  • Security review process
  • Documents required for verification

Case Logging (Pending Investigation)

• Owner: Compliance
• Category: Fraud
• Subcategory: Other (Mandatory Description)
• Subject: Account Restricted
• Resolved: Yes

7. Unknown Fraud Flag

• Refer to:
  • Error Code 909 protocol

8. Address Mismatch Flag

Impact:

• Player cannot deposit or play
• Account remains active

Action:

1. Check Compliance notes

• If notes exist:

  • Follow instructions

• If no notes:

  • Request verification form
  • Resend System ID email

Key Messaging

• Explain mismatch is likely due to:
  • Out-of-state address
  • Verification inconsistency

Case Logging (Address Mismatch)

• Owner: Support
• Category: Fraud
• Subcategory: Other (Mandatory Description)
• Subject: Address Mismatch
• Resolved: Yes

Key Rules Across All Compliance Cases

• Always check existing Compliance notes first
• Do not provide internal fraud details
• Use neutral, security-focused language
• Never promise outcomes (especially reinstatement)
• Escalate only when appropriate

Additional Information / Tips

• Most compliance holds are security-related, not punitive
• Proper documentation speeds up resolution
• Set clear expectations on timelines

Variations / Related Questions

• “Why is my account restricted?”
• “Why can’t I deposit?”
• “What documents do I need?”
• “When will my account be reopened?”

Common Issues / Troubleshooting

• Issue: Player upset about review

  • Emphasize security purpose

• Issue: Player denies activity

  • Follow Unauthorized Activity protocol

• Issue: No notes available

  • Request verification documents

Suggested Case Logging Notes

• Player contacted about account restriction → reviewed and followed Compliance notes
• Player confirmed high deposits → updated case and routed to Compliance
• Player disputed transactions → advised next steps for reversal and documentation
• Player flagged for verification → advised document submission process