SEPA Direct Debit Component

On this page, you can find additional configuration for adding SEPA Direct Debit to your Components integration.

Before you begin

This page assumes you have already built a Components integration.

Before you start integrating SEPA Direct Debit, contact our Support Team, and ask them to add SEPA Direct Debit to your account.

API reference

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

• /sessions: This is the default with Components v5.0.0 or later.
• /payments: If you implemented an additional use case.

Component configuration

Step 1: Create a DOM element

Create a DOM element on your checkout page, placing it where you want the payment method form to be rendered:

 <div id="sepadirectdebit-container"></div>

Step 2: Create an instance of the Component

Use the create method of your AdyenCheckout instance, in this case checkout, to create the Component:

const sepaComponent = checkout.create('sepadirectdebit').mount('#sepadirectdebit-container');

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.

Create shopper token

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

• amount: The transaction must have a minimum value of EUR 0.01.
• recurringProcessingModel: Subscription or UnscheduledCardOnFile
• storePaymentMethod: true
• shopperReference: Your unique identifier for the shopper (minimum length three characters).

When the payment is settled, you receive a RECURRING_CONTRACT 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 recurring payment

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

• storedPaymentMethodId: The pspReference from the RECURRING_CONTRACT webhook.

  You can also get this value by using the /listRecurringDetails endpoint.

• shopperReference: The shopper ID you provided when created the shopper token.
• shopperInteraction: ContAuth.
• recurringProcessingModel: Subscription or UnscheduledCardOnFile.

For more information about the shopperInteraction and recurringProcessingModel fields, refer to Recurring transaction types.

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 webhooks.

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.

A SEPA chargeback notification can indicate that:

• The shopper disputed the charge.
• There were insufficient funds in the shopper's bank account.
• The bank account was inactive.
• Direct debit is blocked on this bank account, either in general or for this creditor specifically.
• There was a technical error.

For a list of detailed SEPA chargeback reasons and reason codes, see Dispute reason codes.

A chargeback webhook 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 webhook that indicates a SEPA chargeback because there were insufficient funds in the shopper's bank account.

{
   "live":"false",
   "notificationItems":[
      {
         "NotificationRequestItem":{
            "additionalData":{
               "chargebackReasonCode":"AM04",
               "modificationMerchantReferences":"",
               "chargebackSchemeCode":"sepadirectdebit",
               "defensePeriodEndsAt":"2021-05-06T22:09:50+02:00",
               "defendable":"false",
               "disputeStatus":"Lost"
            },
            "amount":{
               "currency":"EUR",
               "value":1000
            },
            "eventCode":"CHARGEBACK",
            "eventDate":"2021-05-06T22:09:50+02:00",
            "merchantAccountCode":"YOUR_MERCHANT_ACCOUNT",
            "merchantReference":"YOUR_REFERENCE",
            "originalReference":"9913333333333333",
            "paymentMethod":"sepadirectdebit",
            "pspReference":"9915555555555555",
            "reason":"AM04:InsufficientFunds",
            "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.

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

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

See also