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

EPS Drop-in integration

Add EPS to an existing Drop-in integration.

This page explains how to add EPS to your existing Web Drop-in integration.

Requirements

Select the server-side flow that your integration uses:

Import resources for v6

If you are using Web Drop-in v6, import the resources you need for EPS:

import { AdyenCheckout, EPS} from '@adyen/adyen-web'

API reference

You do not need to send additional fields for EPS. To see optional fields that you can send for all payment methods, choose the endpoint you integrated:

Drop-in configuration

Optional configuration

You can add the following optional configuration:

Parameter name Description Default
issuer Set to an EPS issuer ID to preselect a specific bank. No bank is preselected.
highlightedIssuers Set to the EPS issuer IDs for banks you want to show on top of the dropdown menu. Added in v5.1.0 All issuers are shown in the dropdown.
placeholder The string you want to show as the dropdown menu text. Custom translation configuration overrides this value. Select your bank

If you want to add optional configuration, include this in a configuration object. The following example shows how to configure Drop-in to remove the bank logos, and preselect Dolomitenbank:

const epsConfiguration = {
  issuer: "d5d5b133-1c0d-4c08-b2be-3c9b116dc326" // Optional. Set this to an **id** of an EPS issuer to preselect it.
};

Include the epsConfiguration object when creating a configuration object for Drop-in:

Pass the Drop-in configuration object when creating your instance of AdyenCheckout:

const checkout = await AdyenCheckout(configuration);

List of issuer IDs

The available banks for EPS are different in the test and live environment:

Recurring payments

We support recurring transactions for EPS through SEPA Direct Debit. 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

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:

  • storePaymentMethod: true
  • shopperReference: Your unique identifier for the shopper (minimum length three characters).

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

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

  • shopperReference: The unique shopper identifier that you specified when creating the token (minimum length three characters).
  • shopperInteraction: ContAuth.
  • recurringProcessingModel: Subscription or UnscheduledCardOnFile.

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

Test and go live

Check the status of EPS test payments in your Customer Area > Transactions > Payments.

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

See also