As with other redirect payment methods, you can use our Redirect Component to handle the redirect to a Trustly-hosted payment page.
When making an Trustly payment, you need additionally need to include Trustly in the list of available payment methods.
Before you begin
This page assumes you have already:
Show Trustly in your payment form
Include Trustly in the list of available payment methods. You don't need to collect any information from the shopper in your payment form.
- Specify in your /paymentMethods request:
The response contains
We provide logos for Trustly which you can use on your payment form. For more information, refer to Downloading logos.
Make a payment
When the shopper pays:
From your server, make a POST /payments request, specifying:
paymentMethod.type: Set this to trustly.
returnUrl: URL to where the shopper should be redirected back to after they complete the payment. Get this URL from the Component in the
The /payments response contains an
actionobject with the information needed to redirect the shopper.
- Pass the
actionobject to your client app.
Handle the redirect
- Use the Redirect Component to redirect the shopper to a Trustly-hosted payment page.
- After the shopper returns to your app, make a POST /payments/details request from your server, providing:
actionComponentData.detailsobject from the Redirect Component.
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
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
|The shopper has completed the payment but the final result is not yet known.||Inform the shopper that you've 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.|
|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 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 token
To create a token, include in your /payments request:
- shopperReference: Your unique identifier for the shopper.
- shopperEmail: The shopper's email address.
When the payment has been settled, you receive a webhook containing:
pspReferenceof 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:
pspReferencefrom the RECURRING_CONTRACT.
You can also get this value by using the /listRecurringDetails endpoint.
shopperReference: The unique shopper identifier that you specified when creating the token.
recurringProcessingModel: Subscription or UnscheduledCardOnFile.
For more information about the
recurringProcessingModel fields, refer to Recurring transaction types.
In rare scenarios (around 0.2% of all cases), it is possible that you do not receive the funds even after receiving a successful AUTHORISATION webhook. The successful AUTHORISATION webhook means that the payment has passed the verifications that the issuer and Trustly run on the shopper account, and that the bank transfer was initiated successfully. However, the payment can still fail for the following reasons:
- The shopper cancelled the transaction. Banks in some countries (including Germany) allow shoppers to cancel bank transfers until midnight of the day of the transaction.
- Some banks process transactions with a delay and do not block the funds for an authorized Trustly payment. For example, if the shopper completes a Trustly payment on a Saturday, the bank might only process it on Monday. If the shopper has withdrawn sufficient funds in the meantime, the payment will fail.
In these cases, Adyen is not informed that the transaction failed. We also don't know whether the bank might still process it later.
On our side, the status of the payment is SentForSettle until we receive the funds. You can check the status of the payment in your Customer Area.
If we have not received the funds after 8 calendar days, the status of the payment becomes Settled, then Chargeback, and you receive a CHARGEBACK webhook.
You cannot defend Trustly chargebacks.
In case we receive the money after this point, you receive a CHARGEBACK_REVERSED webhook.
Test and go live
Use the test credentials provided by Trustly. When prompted for a one-time passcode, copy the one-time passcode provided in the form. You can then 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.