This page explains how to add SEPA Direct Debit to your existing Web Components integration.
Requirements
Select which endpoint you are using:
Import resources for v6
If you are using Web Components v6, import the Component that you need for SEPA Direct Debit:
import { AdyenCheckout, SepaDirectDebit } from '@adyen/adyen-web'
API reference
You do not 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
v6.0.0 or later
Create an instance of the Component, passing:
- Your instance of
AdyenCheckout
.
const sepa = new SepaDirectDebit(checkout).mount('#sepadirectdebit-container');
v5.x.x or earlier
Use the create
method of your AdyenCheckout
instance, in this case checkout
, to create the Component:
const sepaComponent = checkout.create('sepadirectdebit').mount('#sepadirectdebit-container');
Capture the payment
If you do not use automatic capture, you must capture the payment in one of the following ways:
- Use delayed automatic capture. This means that the payment is captured automatically after a delay that you can set yourself.
- Manually capture the payment by making a /payments/{paymentPspReference}/captures request.
SEPA Direct Debit authorizations do not expire, so you can capture a payment any time after it is authorized.
Contact our Support Team to enable multiple partial captures for SEPA Direct Debit.
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
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 charged amount reduces the risk of chargebacks.
To create a token, include in your /payments request:
- amount: The transaction must have a minimum value of EUR 0.01.
- storePaymentMethod: true
- shopperReference: your unique identifier for the shopper (minimum length three characters). Do not include personally identifiable information (PII), such as name or email address.
- recurringProcessingModel: Subscription or UnscheduledCardOnFile
From Checkout v70,
recurringProcessingModel
is a required parameter when creating or using a token.
When the payment is settled, you receive a RECURRING_CONTRACT webhook containing:
eventCode
: RECURRING_CONTRACToriginalReference
: ThepspReference
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 to the /payments endpoint, specifying:
- paymentMethod.type: sepadirectdebit
- paymentMethod.storedPaymentMethodId: The
pspReference
from the RECURRING_CONTRACT webhook. You can also get this value using the /listRecurringDetails endpoint. - shopperReference: The shopper ID you provided when you created the shopper token.
- shopperInteraction: ContAuth.
-
recurringProcessingModel: Subscription or UnscheduledCardOnFile.
From Checkout v70,
recurringProcessingModel
is a required parameter when creating or using a token.
For more information about the shopperInteraction
and recurringProcessingModel
fields, refer to Tokenization.
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.
Test and go live
Before making live SEPA payments, use the following Account Names and IBANs to test your integration.
Account Name | IBAN | Country/region |
---|---|---|
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.
Before you can accept live SEPA Direct Debit payments, you need to submit a request for SEPA Direct Debit in your live Customer Area.