Test environment


Test environment

JSON RPC target: https://test.trustly.com/api/1
Backoffice: https://test.trustly.com/backoffice


You need to request a test account, which will have a different password than the production account.

Using the Trustly test system

The Trustly test system is here to allow you to develop and test the integration with Trustly. The test environment works the same way as the production environment except no real money or banks are used when performing payments.

In the test environment, all payments are done using a simplified bank that will be the same regardless of the bank selected in the payment flow. As we are using the same bank backend for all payments, the end-user experience when paying will be the same for all banks. This is different from the production system where the flow for the end user will vary slightly depending on the bank. During the payment process, you will be prompted to log in to the bank. This is typically either a national person identifier or a bank username and will vary per bank and country. When prompted, any login identifier (that conforms with the asked-for criteria) can be used in the test environment. The first time any log-in details are used in a bank a new randomized person identity will be created. Any national id provided does not have to be valid, but it has to be in the correct format.

Triggering test cases

For Deposits, Withdrawals, and SelectAccount with mandate registration (Trustly Direct Debit) it is possible to trigger various test cases in the Trustly checkout after selecting the bank. This step will only be displayed in our test environment, not in production. You can trigger the test cases by selecting "Set order options".

You will find more information about the test cases on our Acceptance Testing page.

Notification test page

Here you will find our notification test page. On this page, you can view the notifications that Trustly has sent for a particular order by entering your processing account username (username used in the API calls) and an OrderID. If a notification has not been delivered successfully, you will see the error message for the failed notification here as well.

You will also find a cURL command here for every notification so that you can send the notification yourself. You will also be able to submit notification responses on this page, but to do this you will have to add an additional attribute "HoldNotifications" : "1" to the Deposit/SelectAccount/Withdraw call for which you want to submit the notification responses. This will be helpful if your development server is not reachable from the internet.