logo
Trustly Docs
BETA
Integration guide for Travel

Trustly's travel services integrations cover the following scenarios:

  • Customers pay all at once.

  • Accept recurring payments from customers with a Payment plan where a deposit is paid ‌for a travel product and the remainder is accepted in instalments.

Note: Currently, recurring payments can only be accepted in Sweden.

  • Provide a Refund.

API methods and notifications to implement in your travel service system are shown in the following table:

API method/notificationFunctionPurpose
DepositPay-inCustomers pay with Trustly at checkout
RefundRefundProvide refunds to customers
Charge

CancelCharge
Recurring paymentCustomers make recurring payments via Trustly.
Used together with Deposit or SelectAccount
SelectAccountBank account tokenisationRegisters customers
Pending notificationNotificationYou’re notified when the checkout flow is completed successfully
Cancel notificationNotificationYou’re notified when the checkout flow has been interrupted
Credit notificationNotificationYou’re notified when the checkout is completed successfully
Debit notificationNotificationYou’re notified when the checkout fails
Account notificationNotification (Optional)Trustly sends information about the account used in this order
  • Make sure that you have completed Sign up and received a Trustly test account.

  • If you have a native app implementation, integrate Trustly SDKs.

In a typical Deposit flow:

  1. Your customer enters the amount for payment in your checkout.

  2. Your system sends an API call to Deposit .

  3. Trustly responds with a checkout URL and OrderID.

  4. Your system redirects the customer to the Trustly checkout where they log in to their bank and authorise the payment.

  5. The customer will be redirected from the Trustly checkout to SuccessURL specified in the deposit API call.

  6. Depending on the outcome, Trustly may send these notifications:

  7. Your system responds to the received notifications.

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.

  1. Make sure that your integration follows security requirements. See Security.

  2. When a customer chooses Trustly in your checkout, your system calls Deposit.

  3. Integrate Trustly Express. See Trustly Express API.

  4. When Trustly responds with a Trustly URL, your system presents the URL to the customer to select a bank for making the deposit.

  5. Make sure that your integration logs and handles error codes that are returned from API calls. See Error handling.

  6. Make sure that your integration responds correctly to notifications that Trustly may send out.

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

Prior to going live, the Trustly Integration Specialist will perform Acceptance testing. Make sure your integration has passed all test cases, including:

  • Deposit API calls

  • Built-in test cases of acceptance testing: D1 to D5, and G1 to G3.

  • Verify that your app has correct responses to notifications. See Notification tool.

Follow the instructions to go live.

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

  • If you have a native app implementation, integrate Trustly SDKs.

In a typical Refund flow:

  1. Your system sends an API call to Refund.

  2. Trustly responds with "result" : "1" to acknowledge the call is received.

  3. Trustly checks whether the funds have been settled.

    • If the funds are not settled, Trustly will process the refund request when the funds are settled.

    • If the funds are settled, Trustly will process the refund request.

  4. Trustly sends a Payout confirmation when the funds are successfully sent from Trustly.

    Note: The Payout confirmation is not enabled by default. Contact Trustly Integration Support, if you need it.

  5. If the refund fails, Trustly will send a Credit notification.

  6. Your system responds to the received notifications.

Develop business logic according to the charge flow.

  1. Make sure that your integration follows security requirements. See Security.

  2. Make sure that you have sufficient funds in your Trustly account. You can schedule API call to Balance to ensure that your balance is sufficient.

  3. When a customer requests a refund, you system sends a call to Refund.

  4. Make sure that your integration logs and handles error codes that are returned from API calls. See Error handling.

  5. Make sure that your integration responds correctly to Trustly notifications.

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

Prior to going live, the Trustly Integration Specialist will perform Acceptance testing. Make sure your integration has passed all test cases, including:

  • Deposit API calls

  • Built-in test cases of acceptance testing: D1 to D5, and G1 to G3

  • Verify that your integration has correct responses to notifications. See Notification tool.

Follow the instructions to go live.