SEPA Direct Debit

Server-Side Implementation

Important

Your integration may be impacted by upcoming certificate changes. Visit our best practices guide to learn more.

Note

Ruby 2.104.1 or higher is required to use SEPA Direct Debit.

Creating transactions

Creating a SEPA Direct debit transaction is the same as creating any other transaction with a nonce or a vaulted payment method. Be sure to pass the device data you collected on the client side when you create the transaction.

Optional fields

order_id - a merchant-generated ID associated with the transaction
descriptor_name - a descriptor that will show in the user's bank statement

Below includes an example call with relevant parameters:

Ruby

result = gateway.transaction.sale(
    :amount => "10.00",
    :payment_method_nonce => nonce_from_the_client,
    :merchant_account_id => "EUR-merchant-account",
    :order_id => "Order 1234",
    :descriptor_name => "Merchant ABC",
    :device_data => device_data,
    :options => {
        :submit_for_settlement => true,  # Required
    }
)
if result.success?
    "Success ID: #{result.transaction.id}"
else
    result.message
end

Currency support

SEPA Direct Debit only supports EUR currency.

SEPA Direct Debit webhooks

You can set up webhooks to notify you of changes in status to SEPA Direct Debit transactions.

See the webhooks guide for details on how to configure webhooks in general
See the Transaction webhooks reference for details on the specific notifications available for sales and refunds