SEPA through Adyen integration guide

SEPA through AdyenSEPA through Adyen The SEPA (Single Euro Payments Area) through Adyen is a pan-European network that allows consumers to send and receive payments in euros (€) between two cross-border bank accounts in the eurozone. With SEPA, sending money within the eurozone is as easy as making your usual domestic bank transfers.

A SEPA credit transfer is a single transfer of euros from one person or organization to another. For example, this could be to pay the deposit for a holiday rental or to settle an invoice. A SEPA direct debit is a recurring payment. For example, to pay monthly rent or for a service like a mobile phone contract.

Services and compatibility

Payment method gateway nameAdyen
Supported transaction types
Note: SEPA through Adyen does not support chargebacks.
Supported integration methods
Supported processing currenciesEUR
Webhook event types
  • TRANSACTION_AUTHORIZED
  • TRANSACTION_REFUNDED
  • TRANSACTION_SETTLED

Configuration

Apart from working with Integrations Support to add SEPA as a payment method, you do not need to do any other configuration steps.

Required fields

The following table shows the required and conditional fields for SEPA transactions in the Create APM one-time-use token request.

FieldRequired?Description
isAuthOnlyNSet to true to run an auth only transaction.
data.amountYThe transaction amount.
data.currencyYThe three-character ISO currency code for the transaction. Note: Nexio only supports EUR with SEPA.
data.paymentMethodYThe desired alternative payment method. This value must be adyenSepa.
data.dueDateNThe date by which the customer must complete the payment.
data.descriptionNA description of the transaction.
data.customer.orderNumberYThe order number.
data.customer.firstNameYThe customer's first name, as it appears on the card.
data.customer.lastNameYThe customer's last name, as it appears on the card.
data.customer.emailYThe customer's email address.
data.customer.billToAddressOneNThe customer's billing street address.
data.customer.billToAddressTwoNAdditional street address information, if required.
data.customer.cityNThe customer's billing city.
data.customer.billToCountryYThe two-character (Alpha-2) ISO country code.
data.customer.billToPhoneNThe billing phone number.
data.customer.billToPostalNThe customer's billing postal code.
data.customer.billToStateNThe state or province on file with the credit card provider.
data.customer.customerRefNCustomer identifier. You can use this field to pass a customer ID to the gateway or APM or to manage user subscriptions.
data.customer.shipToAddressOneNThe shipping address, if different from the billing address.
data.customer.shipToAddressTwoNAdditional shipping address information, if required.
data.customer.shipToCityNThe shipping city.
data.customer.shipToCountryNThe two-character (Alpha-2) ISO country code.
data.customer.shipToPhoneNThe shipping phone number.
data.customer.shipToPostalNThe shipping postal code.
data.customer.shipToStateNThe shipping state or province.
processingOptions.paymentOptionTagNA custom value used to route transactions to a specific gateway or merchant account.
processingOptions.merchantIdNThe merchant ID (MID).
data.paymentMethodOptionalThe identifier for the alternative payment method. Use this parameter when you want to only return the SEPA iframe button URL (rather than data for all payment methods associated with the account).

The value to use is adyenSepa.

Transaction types and implementation methods

Regardless of the implementation workflow you implement, consumers will be redirected to SEPA to complete their transactions.

Nexio supports the following transaction types for SEPA:

Testing data

Adyen has an extensive list of test accounts. For more information, see SEPA Direct Debit on Adyen's site.

Response handling

In the one-time-use token request, SEPA gets returned in the paymentMethod parameter as adyenSepa.

Nexio responds with transaction results in one of the following ways, depending on your integration workflow:

  • Event messages: This applies to integrations that do not pass a customerRedirectUrl in the request.
  • Response fields in the URL: This applies to integrations that do provide a customerRedirectUrl in the request.

In addition to one of the above, if your merchant account is configured to receive webhooks, Nexio provides responses to the webhook URLs that have been registered. For further explanation of the webhook event types, see the webhook Event types table.

  • Webhook notification: For SEPA, these are the possible webhook event types:
    • TRANSACTION_AUTHORIZED
    • TRANSACTION_CAPTURED
    • TRANSACTION_REFUNDED
    • TRANSACTION_SETTLED

For information about how to run each of the integration workflows, see Transaction types above.

Status workflows

The status of a successful transaction with SEPA varies, depending on the options you choose.

Sale

When isAuthOnly is false, successful sale transactions will have the following statuses:

  • pending (called "authorized" when querying transactions and in Nexio Dashboard)
  • settled

When isAuthOnly is true, successful sale transactions will have the following status:

  • authOnly

Capture

Successful capture transactions will have the following status:

  • settled

Next steps

Now, you are ready to get started with running transactions:

If you have any additional questions or feedback, see Contact us.


Did this page help you?