---
title: "SEPA Direct Debit"
description: "Payment Page 1.5.3 exposes EUR-only SEPA Direct Debit through Stripe and marks it recurring-capable, subject to release verification and provider eligibility."
url: "https://docs.paymentpageplugin.com/payment-gateways/stripe/sepa-direct-debit/"
---
## Released behavior

Payment Page 1.5.3 exposes SEPA Direct Debit under the internal method slug `sepa`. The front-end mounts Stripe's IBAN field, creates a `sepa_debit` payment method, and renders the plugin's mandate text using the configured business name.

## How to enable it

1.  Connect Stripe in the mode you intend to use. See [Quick Setup](/getting-started/setting-up-payment-page/).
2.  In **Payment Page > Payment Gateways**, expand Stripe and enable **SEPA Direct Debit** globally.
3.  Include SEPA Direct Debit in the individual payment form's Payment Methods settings.
4.  Use EUR pricing and confirm that SEPA Direct Debit is enabled and eligible for the connected account in [Stripe payment-method settings](https://dashboard.stripe.com/settings/payment_methods).
5.  Configure the mode-specific success events described in [Stripe Webhook Configuration](/payment-gateways/stripe/stripe-webhook-configuration/).

The released method definition restricts SEPA Direct Debit to **EUR**. Provider eligibility also depends on the connected account, customer location, mandate, and transaction.

## Recurring and asynchronous behavior

The released method definition marks SEPA Direct Debit as recurring-capable. Payment Page uses SetupIntent outcomes, paid and failed invoices, and created, updated, and deleted subscription events for its released recurring paths. Stripe still controls mandate eligibility, settlement timing, retries, and account state.

SEPA Direct Debit is asynchronous. The automatically created Payment Page endpoint uses the exact 12-event contract in [Stripe Webhook Configuration](/payment-gateways/stripe/stripe-webhook-configuration/), including processing/failure, invoice, and subscription events. Do not treat an initiated debit or a browser return as settled; verify the accepted signed provider event and corresponding Payment Page record.

Consult the European Payments Council's current [list of SEPA scheme countries](https://www.europeanpaymentscouncil.eu/document-library/other/epc-list-sepa-scheme-countries) and Stripe's [SEPA documentation](https://stripe.com/docs/payments/sepa-debit) for current provider requirements.

End-to-end verification of the final Payment Page 1.5.3 release archive is still pending for SEPA one-time, recurring, asynchronous, failure, renewal, cancellation, duplicate-delivery, and downstream-action behavior.