Trustly Drop-in integration

Add Trustly to an existing Drop-in integration.

If you are using Android Drop-in v5.0.0 or later:

This payment method requires no additional configuration.

Our Android Drop-in renders Trustly in your payment form, and redirects the shopper to the Trustly app or website where they can complete the payment.

Requirements

Requirement	Description
Integration type	Make sure that you have an existing Advanced flow Android Drop-in integration.
Setup steps	Before you begin, add Trustly in your Customer Area.

Show Trustly in your payment form

Drop-in uses the countryCode and the amount.currency from your /paymentMethods request to show the available payment methods to your shopper.

To have Drop-in render Trustly in your payment form, specify in your /paymentMethods request:

countryCode: Any supported country/region. For example, SE
amount.currency: Any supported currency. For example, SEK.
amount.value: The value of the payment, in minor units.

When the shopper proceeds to pay, Drop-in returns the paymentComponentData.paymentMethod. Pass this to your server.

Make a payment

From your server, make a POST /payments request, specifying:
- paymentMethod: The paymentComponentData.paymentMethod from your client app.
- returnUrl: URL to where the shopper should be redirected back to after they complete the payment. Get this URL from the Component in the RedirectComponent.getReturnUrl(context).

In the /payments response, note the action object. This contains the information needed to redirect the shopper.

If your integration is set up correctly, the action object is passed from your server to the client.

Check the payment result

Drop-in redirects the shopper to complete the payment. When the shopper returns back to your app, Drop-in provides the actionComponentData object.

From your server, make a POST /payments/details request providing:

details: The actionComponentData.details object from Drop-in.

You receive a response containing:

resultCode: Use this to present the payment result to your shopper.
pspReference: Our unique identifier for the transaction.

Present the payment result

Use the resultCode that you received in the /payments/details response to present the payment result to your shopper.

The resultCode values you can receive for Trustly are:

resultCode	Description	Action to take
Authorised	The payment was successful.	Inform the shopper that the payment has been successful. You will receive the funds in 3 days.
Cancelled	The shopper canceled the payment while they were on the Trustly-hosted payment page.	Ask the shopper whether they want to continue with the order, or ask them to select a different payment method.
Error	There was an error when the payment was being processed.	Inform the shopper that there was an error processing their payment. The response contains a `refusalReason`, indicating the cause of the error.
Pending or Received	The shopper has completed the payment but the final result is not yet known.	Inform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.
Refused	The payment was refused by the shopper's bank.	Ask the shopper to try the payment again using a different payment method.

If the shopper failed to return to your website or app, wait for webhooks to know the outcome of the payment. The webhooks you can receive for Trustly are:

eventCode	success field	Description	Action to take
AUTHORISATION	false	The transaction failed.	Cancel the order and inform the shopper that the payment failed.
AUTHORISATION	true	The shopper successfully completed the payment.	Inform the shopper that the payment has been successful and proceed with the order.
OFFER_CLOSED	true	The shopper did not complete the payment.	Cancel the order and inform the shopper that the payment timed out.

Recurring payments

Recurring payments using Trustly can only be processed in Sweden and requires additional configuration. Contact Support Team team to enable this.

We support recurring transactions for Trustly. To make recurring payments, you need to:

Create a shopper token.
Use the token to make future payments for the shopper.

Create a token

To create a token, include in your /payments request:

storePaymentMethod: true
shopperReference: Your unique identifier for the shopper.
shopperEmail: The shopper's email address.

When the payment has been settled, you receive a webhook containing:

eventCode: RECURRING_CONTRACT
originalReference: The pspReference of the initial payment.
pspReference: This is the token that you need to make recurring payments for this shopper.

Make sure that your server is able to receive RECURRING_CONTRACT as part of your standard webhooks. You can enable the RECURRING_CONTRACT event code in the webhook settings page.

Make a payment with a token

To make a payment with the token, include in your /payments request:

paymentMethod.storedPaymentMethodId: The pspReference from the RECURRING_CONTRACT.

You can also get this value using the /listRecurringDetails endpoint.
shopperReference: The unique shopper identifier that you specified when creating the token.
shopperInteraction: ContAuth.
recurringProcessingModel: Subscription or UnscheduledCardOnFile.

For more information about the shopperInteraction and recurringProcessingModel fields, refer to Tokenization.

Test and go live

Trustly provides a simulated bank environment to complete your testing end to end. Follow the instructions provided in their documentation. You can check the status of Trustly test payments in your Customer Area > Transactions > Payments.

Before you can accept live Trustly payments, you need to submit a request for Trustly in your live Customer Area.