How to get started with Trustly Deposit for Gaming
Trustly's gaming integrations allow you to cover the following scenarios:
Regular deposit checkout.
Open or Closed loop payouts.
Pay and play without registration.
API methods and notifications to implement in your gaming cashier and merchant system are shown in the following table:
| API method/notification | Function | Purpose |
|---|---|---|
| Deposit | Pay-in | Players deposit money using Trustly checkout |
| AccountPayout | Pay-out | Players request payouts without Trustly checkout interaction (closed loop payouts) |
| Refund | Refund | Gaming operators refund deposits |
| RegisterAccount SelectAccount | Bank account tokenisation | Used together with Account Payout to enable open loop payouts |
| GetWithdrawals | Reporting | Returns a detailed status of a payout |
| AccountLedger Balance | Reporting | Check the balance of your Trustly account |
| Pending notification | Notification | You’re notified when the checkout flow is completed successfully |
| Cancel notification | Notification | You’re notified when the checkout flow has been interrupted |
| Credit notification | Notification | You’re notified when the player’s gaming balance should be increased |
| Debit notification | Notification | You’re notified when the player’s gaming balance should be decreased |
| Account notification | Notification | Trustly sends information about the account used in this order |
| Payout confirmation | Notification | Trustly sends to the merchant’s system to confirm a payout has been sent |
Deposit
Make sure that you have completed Sign up and received a Trustly test account.
)
In a typical Deposit flow:
Your player enters the amount to deposit in your gaming cashier.
Your system sends an API call to
Deposit.Trustly responds with a checkout URL and
OrderID.Your system redirects the player to the Trustly checkout where they log in to their bank and authorise the payment.
The player is redirected from the Trustly checkout to the
SuccessURLspecified in the deposit API call.Depending on the outcome, Trustly may send these notifications:
Pending notification when the player has completed the checkout process.
Credit notification when the player's gaming balance should be credited.
Account notification gives you information about the bank account that is selected by the player.
Debit notification if the deposit transaction fails after the credit is sent.
Cancel notification if the checkout process is interrupted.
You must respond to all notifications immediately.
Note: Account, Pending, Credit notifications can arrive in any order. The Account notification is not enabled by default. Contact Trustly Integration Support, if you need it.
Develop business logic according to the deposit flow.
Make sure that your integration follows security requirements. See Security.
When players Deposit money, your system calls
deposit.Integrate Trustly Express API.
When Trustly responds with a Trustly URL, your app presents the URL to the player to select a bank for making the deposit.
Make sure that your integration logs and handles error codes that are returned from API calls. See Error handling.
If you have a native app implementation, integrate Trustly SDKs.
When your integration presents a Trustly URL to players, the presentation must follow Trustly checkout guidelines.
Prior to going live, the Trustly Integration Specialist will perform a series of acceptance testing cases according to Trustly standards, including:
Check Deposit API calls parameters and attributes
Run built-in test cases (D1-D5 & G1-G3) which are available in the Trustly test checkout
Verify that all API notifications are sent with valid responses.
Verify user experience of merchant's service presentation
Follow the instructions to go live.
AccountPayout
Make sure that you have completed Sign up and received a Trustly test account.
The AccountPayout method is used by merchants to transfer money to their customer's bank accounts. The merchant specifies the receiving bank account in the AccountPayout call by using the AccountID parameter, which is a unique identifier generated by Trustly. The merchant can get the AccountID from the account notification which is sent after a SelectAccount or a Deposit order has been completed.
Alternatively, the RegisterAccount method can be used to get the AccountID, if the merchant already has the bank account details and want to register them in Trustly's system.
A typical payout flow is:
The player enters the amount and requests a payout from your gaming cashier.
You should verify the payout request and send out the AccountPayout API call which should include the AccountID.
If the player already deposited with Trustly before you should have the AccountID saved in your system.
If the player never deposited with Trustly you should obtain the AccountID by calling SelectAccount or RegisterAccount APIs.
If the payout will be denied, then you should not send any API calls to Trustly.
Trustly returns a synchronous response to let you know that the AccountPayout request has been received and the payout is being processed.
Trustly may send the following notifications:
Cancel notification when the payout is canceled.
Credit notification when the payout fails.
Payout confirmation when the money is successfully transferred from the player account in your system to their bank account.
Your system must respond to the received notifications in a timely manner.
Develop business logic according to the payout flow.
Make sure that your integration follows security requirements. See Security.
When a player requests a payout, your system calls
AccountPayout. See AccountPayout.Make sure that your integration logs and handles error codes that are returned from API calls. See Error handling.
You should implement the SelectAccount or RegisterAccount for open-loop payouts depending on the market and commercial agreement.
Since there is no Trustly checkout interaction, the merchant should create the UX for the players that include Trustly as the payout option.
Prior to going live, the Trustly Integration Specialist will be performing a series of acceptance testing cases according to Trustly standards, including:
Check
AccountPayoutAPI call parameters and attributesRun various test cases according to Trustly standard
Verify that all API notifications are sent with valid responses in a timely manner
Verify user experience of merchant's service presentation
Follow the instructions to go live.
SelectAccount
)
A typical SelectAccount flow is:
Since the player never deposited with Trustly in your gaming cashier, a new account must be added to your system to initiate any future payout requests.
The player enters the amount to payout and chooses Trustly as a payout method.
You send an API call to SelectAccount and redirect the end-user to the URL.
The player selects their bank and completes the identification process.
The end-user is redirected back to the merchant at the SuccessURL, note that the account might not be verified yet at this point.
When the account is verified, Trustly sends an Account notification to the merchant's system with information about the selected account.
Trustly will send the Cancel notification if the player aborts the checkout process.
Once the accountID is stored in your system, send the AccountPayout API call for Trustly to process.
Develop business logic according to the payout flow.
Make sure that your integration follows security requirements. See Security.
Implement the SelectAccount API according to the Trustly specification. See SelectAccount.
Implement the redirection to Trustly checkout URL, which will allow the player to select a bank account.
Make sure that your integration logs and handles error codes that are returned from API calls. See Error handling.
If you have a native app implementation, integrate Trustly SDKs. See Trustly SDKs.
When the merchant presents a Trustly URL to players, the presentation must follow Trustly checkout guidelines.
Prior to going live, the Trustly Integration Specialist will be performing a series of acceptance testing cases according to Trustly standards.
This will include:
Check
SelectAccountAPI calls parameters and attributesRun built-in test cases (G1-G3) which are available in the Trustly test checkout
Verify that all API notifications are sent with valid responses
Verify user experience of your service presentation
Follow the instructions to go live.
RegisterAccount
)
A typical RegisterAccount + AcountPayout flow is:
Since the player never deposited with Trustly in your gaming cashier, a new account must be added to your system to initiate any future payout requests.
The player enters the amount to payout and the bank account number (according to the market).
You send an API call to RegisterAccount.
Trustly will respond with a designated accountID for the bank account.
Once the accountID is stored in your system, send the AccountPayout API call for Trustly to process.
The player should have the saved bank account displayed in the cashier as an option for future payouts.
Develop business logic according to the payout flow.
Make sure that your integration follows security requirements. See Security.
Implement the SelectAccount API according to the Trustly specification. See RegisterAccount
Make sure that your integration logs and handles error codes that are returned from API calls. See Error handling.
Since there is no Trustly checkout interaction, the merchant should create the Instant bank payout form that would include the Bank account fields according to the market and the integration is done.
Prior to going live, the Trustly Integration Specialist will be performing a series of acceptance testing cases according to Trustly standards.
This will include:
Checking
RegisterAccountAPI calls parameters and attributesRun various user acceptance testing scenarios as per Trustly procedure
Verify user experience of merchant's service presentation
Follow the instructions to go live.
Pay N Play
Pay N Play creates a frictionless player experience through a simplified registration and login process. Pay N Play can be implemented in two different models, depending on your business and technical needs.
Combines deposit and registration into one step
Verify players before the deposit is completed
Utilise bank-verified KYC data and 3rd party information
Closed-loop withdrawals with one API call to Trustly
Pay N Play is available in Sweden, Finland, Estonia and the Netherlands.
)
This model enables you to:
Provide Trustly as the only payment method for players to make a deposit/payout
Let players log in without making a deposit
Your system will use Trustly for registration, login, deposits, payouts, and KYC information. It will be able to process compliant data provided by Trustly during a deposit transaction.
This model enables you to:
Provide Trustly among other payment methods for players to make a deposit/payout
Let players log in along with making a deposit
Your system will be able to provide an option for players to register in a traditional sign-up form alongside Pay N Play flow.
The following table shows which API methods and notifications are available to implement in the gaming cashier and merchant system for a Pay N Play integration.
| API method/notification | Purpose | Pure Pay N Play | Hybrid Pay N Play |
|---|---|---|---|
| Deposit | Allows players to deposit money and provides KYC data for registration/login purposes using Trustly checkout | Required | Required |
| AccountPayout | Allows players to request payouts without Trustly checkout interaction (closed loop payouts) | Required | Not applicable |
| Refund | Allows you to refund deposits | Optional | Optional |
| KYC notification | Trustly sends KYC data for Pay N Play orders | Required | Required |
| Account notification | Trustly sends information about the account used in this order | Required | Required |
| Pending notification | Trustly sends to the merchant’s system in order to confirm that a payout has been sent | Required | Required |
| Cancel notification | You are notified when the checkout flow has been interrupted | Required | Required |
| Credit notification | You are notified when the player’s gaming balance should be increased | Required | Required |
| Debit notification | You are notified when the player’s gaming balance should be decreased | Required | Required |