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.
  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.
  5. Configure the mode-specific success events described in Stripe Webhook Configuration.

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, 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 and Stripe's SEPA documentation for current provider requirements.