No momento, esta página não está disponível em português
Payment-method icon

Trustly Drop-in integration

Add Trustly to anexisting iOS Drop-in integration.

On this page, you can find additional configuration for adding Trustly to your Drop-in integration.

Before you begin

This page assumes you have already:

API reference

You don't need to send additional fields for Trustly. To see optional fields that you can send for all payment methods, choose the endpoint you integrated:

Drop-in configuration

There is no required Trustly-specific integration for Drop-in.

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:

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

Create a token

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

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.

  • shopperInteractionContAuth.

  • recurringProcessingModel: Subscription or UnscheduledCardOnFile.

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

Chargebacks

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/regions (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

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.

See also