top of page

SOP for Risk & Payment

Updated: Dec 2, 2025

New SOP: A. For those handling Risk WD, please note the following regarding requests for "manual withdrawals":


When you receive such a request, it indicates that a Player's Withdrawal has been disapproved. Your task is to investigate any discrepancies in the player's bank details that may have led to this disapproval.


To Do:


Use Ok2pay PG for Verification:


1. Navigate to Payment Management.

2. Click on Please Pay.

3. Enter the Bank Name and Bank Account Number.

4. The Account Name will be displayed automatically.

Check for Discrepancies:

Review the details against the player's request.


If you need assistance, please consult your ATL, especially if they are using the payment gateway.

B. UsernameThis player WD is currently on hold on our side. thanks Action: Check the Risk + Payment GC to find out the reason of the withdrawal being on hold. Possible Reason: A.Overcredit/Doublecredit B.Overpayment/Doublepayment


Old SOP: If you are handling manual withdrawal, it is important that the Risk Payment GC is open to be able to check withdrawal request that needs to be manually processed or, processed to a certain PG. A. Username Please process this member's withdrawal manually or other pg do not use IPay . Thanks team! Action: If you are not handling manual withdrawal, you may locked the withdrawal once verified and, let the assigned staff to unlocked it for processing.

To lock a withdrawal request, just simply click process as shown in the photo.

Your name will be displayed in executor column which gives cue to other staff processing pg wd if you left it locked, this gives cue to other staff processing and, the assigned staff, just have click process to take the withdrawal.

You may open a new window to continue to process other withdrawals.


 
 
 

Recent Posts

See All
Monitoring 101(VND)

Monitoring Pending Deposits/Withdrawals in BO -A deposit count exceeding 500 (can change) is generally considered high. -If a high number of pending deposits is encountered, check with PG to identify

 
 
 

Comments


© 2024 SOP Library for Payment Staffs

    Powered and Secured by SOP Library for Payment Staffs

    bottom of page