Withdraw

Before you start

• Make sure that you have completed Sign up and received a Trustly test account.

Withdrawal flow

A typical withdrawal flow is:

1. Player enters the amount to withdraw in the gaming cashier.
2. Your system sends an API call to Withdraw.
3. Trustly responds with a checkout URL and orderID.
4. You should redirect the player to the Trustly checkout where the player will confirm the withdrawal request to the specified bank.
5. The player should be redirected back to the cashier according to the SuccessURL or FailURL, depending on the outcome of checkout.
6. Trustly does nothing with the withdrawal request until it has been approved or denied by the merchant with ApproveWithdrawal or DenyWithdrawal.

• When the merchant sends DenyWithdrawal, the withdrawal is aborted on the Trustly side and a cancel and credit notification is sent to the merchant.
• When the merchant sends ApproveWithdrawal, the withdrawal is approved, and Trustly will process the withdrawal.
• It is also possible to approve/deny withdrawal using Trustly Backoffice.

7. Trustly may send the following notifications:
   1. Debit notification when the player's gaming balance should be decreased.
   2. Credit notification when the withdrawal has failed or been denied by the merchant.
   3. Account notification gives you information about the bank account that is selected by the player.
   4. Payout confirmation sent to the merchant's system in order to confirm that a payout has been sent.
   5. Cancel notification when the withdrawal has been canceled or failed.

Step 1: Integrate your system with Trustly

Develop business logic according to the payout flow.

1. Make sure that your integration follows security requirements. See Security.
2. When a player withdraws money, your system calls withdraw. See Withdraw.
3. When Trustly responds with a Trustly URL, your app presents the URL to the player to select a bank for making the withdrawal.
4. Make sure that your integration logs and handles error codes that are returned from API calls. See Error handling.
5. If you have a native app implementation, integrate Trustly SDKs. See Trustly SDKs.

Step 2: Design service presentation

When your integration presents a Trustly URL to players, the presentation must follow Trustly checkout guidelines.

Step 3: Inform Trustly to do acceptance testing

Prior to going live, the Trustly Integration Specialist will be performing a series of acceptance testing cases according to Trustly standards, including:

• Check Withdraw API calls parameters and attributes
• Run built-in test cases (W1 & G1-G3) which are available in the Trustly test checkout
• Verify that all API notifications are sent with valid responses and in a timely manner
• Verify user experience of merchant's service presentation

Step 4: Go live

Follow the instructions to go live.