Search

Are you looking for test card numbers?

Would you like to contact support?

Payment-method icon

SEPA Direct Debit Drop-in integration

Add SEPA Direct Debit to an existing Drop-in integration.

Our iOS Drop-in renders SEPA Direct Debit in your payment form, where shoppers provide their account holder name and IBAN, and then review and confirm the payment.

Before you begin

This page explains how to add SEPA Direct Debit to your existing iOS Drop-in integration. The iOS Drop-in integration works the same way for all payment methods. If you haven't done this integration yet, refer to our Drop-in integration guide.

Before starting your SEPA Direct Debit integration:

  1. Make sure that you have set up your back end implementation, and added Drop-in to your payment form.
  2. Add SEPA Direct Debit in your test Customer Area.

Show SEPA Direct Debit 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 show SEPA Direct Debit in your payment form, you need to specify in your /paymentMethods request:

After the shopper selects a payment method and provides payment details, Drop-in invokes the didSubmit method which contains data.paymentMethod. Pass data.paymentMethod to your server and make a payment request.

Make a payment

When the shopper proceeds to pay, Drop-in invokes the didSubmit method which contains data.paymentMethod.

  1. Pass data.paymentMethod to your server.
  2. From your server, make a /payments request, specifying:
    • paymentMethod: The data.paymentMethod from the didSubmit event from your client app.

{
  "merchantAccount":"YOUR_MERCHANT_ACCOUNT",
  "reference":"YOUR_UNIQUE_REFERENCE",
  "amount":{
    "currency":"EUR",
    "value":"1000"
  },
  "paymentMethod":{
    "type":"sepadirectdebit",
    "sepa.ownerName":"A. Schneider",
    "sepa.ibanNumber":"DE87123456781234567890"
  }
}

The /payments response contains:

  • resultCode: Received.
  • pspReference: Adyen's unique reference number for the payment.

{
    "pspReference": "881572960484022G",
    "resultCode": "Received",
    "merchantReference": "sepa test"
}

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 SEPA Direct Debit are:

resultCode Description Action to take
Received The payment was successfully received. You will receive a AUTHORISATION notification when the status of the payment has been updated. If successful, you will receive the funds in 2 days.
Authorised The payment was successfully completed. Inform the shopper that the payment was successful.

Recurring payments

If you have a recurring or subscription business model we recommend tokenizing the shopper's payment details. When you create a shopper token from a SEPA payment, we store their payment details with the token. The token can be used to make recurring payments for the shopper.

You can create a shopper token and then make subsequent recurring payments with the token using the /payments endpoint.

We strongly recommend that you request explicit permission from the shopper if you intend to make recurring SEPA payments. Being transparent about the payment schedule and the amount they will be charged will reduce the risk of chargebacks.

Create shopper token

Tokenize the shopper's payment details when you make the initial SEPA payment.

  1. When you call /payments to make a payment, additionally include:
    • shopperReference: Your unique ID for this shopper.
    • paymentMethod.storePaymentMethodtrue
  2. When you receive the response (or the notification) that the payment was authorised, note the recurringDetailReference. This is the token you will need to make recurring payments for this shopper.

Make recurring payment

For each recurring payment for this shopper, make a SEPA payment with a /payments call, and additionally include:

  • recurringDetailReference: Token you received back in the initial payment.
  • shopperReference: The shopper ID you provided when created the shopper token.
  • shopperInteractionContAuth.
{
   "amount":{
       "value":1000,
       "currency":"EUR"
   },
   "paymentMethod":{
       "type":"sepadirectdebit",
       "recurringDetailReference":"7219687191761347"
   },
   "reference":"Your Reference Here",
   "merchantAccount":"TestMerchant",
   "shopperReference":"YOUR_UNIQUE_SHOPPER_ID_IOfW3k9G2PvXFu2j",
   "shopperInteraction":"ContAuth"
}

If the payment was successfully received the response will contain a Received resultCode and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using notifications.

Chargebacks

If a shopper for some reason wants the funds from a payment returned, they can ask their bank for a refund. This is referred to as a chargeback.
For SEPA, the chargeback process gives significant consumer rights to the shopper. They have:

  • Eight weeks to dispute a SEPA payment without providing a reason.
  • Thirteen months to dispute an unauthorised or incorrect SEPA payment when they provide evidence to their bank.
You cannot defend against SEPA chargebacks. These will always result in the shopper receiving a refund.

A SEPA chargeback notification can indicate that:

  • The shopper disputed the charge.
  • There were insufficient funds in the shopper's bank account.

A chargeback notification contains:

  • pspReference: Adyen's unique reference associated with the payment request.
  • eventCode: CHARGEBACK.
  • reason: Reason for the chargeback.
  • success: true.

Here is an example of a notification that indicates a SEPA chargeback because there were insufficient funds in the shopper's bank account.

{
  "live":"false",
  "notificationItems":[
    {
      "NotificationRequestItem":{
        "amount":{
          "value":1000,
          "currency":"EUR"
        },

        "pspReference":"931354792477061C",
        "eventCode":"CHARGEBACK",
        "eventDate":"2020-01-01T01:02:01.111+02:00",
        "merchantAccountCode":"YourMerchantAccount",
        "merchantReference":"YourMerchantReference",
        "paymentMethod":"sepadirectdebit",
        "reason":"Insufficient funds",
        "success":true
      }
    }
  ]
}

For more information on the chargeback process, refer to Dispute management.

Test and go live

Before making live SEPA payments, use the following Account Names and IBANs to test your integration.

Account Name IBAN Country
A. Klaassen NL13TEST0123456789 NL
B. Klaassen NL36TEST0236169114 NL
C. Klaassen NL26TEST0336169116 NL
D. Klaassen NL16TEST0436169118 NL
E. Klaassen NL81TEST0536169128 NL
F. Klaassen NL27TEST0636169146 NL
G. Klaassen NL39TEST0736169237 NL
H. Klaassen NL82TEST0836169255 NL
I. Klaassen NL72TEST0936169257 NL
J. Klaassen NL46TEST0136169112 NL
K. Klaassen NL70TEST0736160337 NL
L. Klaassen NL18TEST0736162437 NL
M. Klaassen NL92TEST0736163433 NL
A. Schneider DE87123456781234567890 DE
B. Schneider DE92123456789876543210 DE
C. Schneider DE14123456780023456789 DE
D. Schneider DE36444488881234567890 DE
E. Schneider DE41444488889876543210 DE
F. Schneider DE60444488880023456789 DE
G. Schneider DE89888888881234567890 DE
H. Schneider DE94888888889876543210 DE
I. Schneider DE16888888880023456789 DE
A. Pacini IT60X0542811101000000123456 IT
A. Grand FR1420041010050500013M02606 FR
A. Martin ES9121000418450200051332 ES
W. Hurth AT151234512345678901 AT
H. Gasser CH4912345123456789012 CH
R. Paulsen DK8612341234567890 DK
B. Dalby NO6012341234561 NO
A. Bak PL20123123411234567890123456 PL
A. Andersson SE9412312345678901234561 SE

You can check the status of SEPA test payments in your Customer Area > Transactions > Payments.

See also