Skip to content
edoobox Docs
Try for free Try it for 7 days, no obligation
Menu
Try for free Try it for 7 days, no obligation

Stripe - Integrate SEPA Direct Debit

Stripe SEPA Direct Debit processes eligible EUR payments by direct debit. Unlike a card payment, a direct debit may initially have processing status and later succeed or fail. This delay must fit your place reservation, MustPay, and internal checks.

Prerequisites

  • Stripe is connected through Stripe Connect and active.

  • The offer uses EUR; the current PaymentIntent logic excludes SEPA for other currencies.

  • SEPA Direct Debit is available in the Stripe account for your organization and transaction.

  • The mandate, payment deadline, returned direct debits, and communication have been clarified internally.

Check the Stripe Dashboard to see whether SEPA Direct Debit is available for your account. The current status of your Stripe account determines availability; do not infer approval solely from the number of previous card payments or an assumed waiting period.

Activate SEPA in Stripe V3

With Stripe V3, edoobox has no separate Enable SEPA direct debit switch. V3 enables automatic Payment Methods; Stripe decides whether SEPA may be offered for a EUR transaction. Activate the method in the Stripe Dashboard, then check a real internal EUR offer.

The separate SEPA switch is visible only in the older Stripe view. To switch to V3, follow Stripe – integrate credit cards and then check the payment methods offered during booking.

processing, succeeded, and payment_failed

For participant payments, edoobox webhook processing tracks in particular:

Stripe eventMeaning for the process
payment_intent.processingThe payment is being processed; final success is usually still pending.
payment_intent.succeededStripe confirms success; edoobox can definitively record the payment.
payment_intent.payment_failedThe payment failed and requires follow-up in the booking process.

“Mark SEPA as paid without validation” option

If this option is active, edoobox may record a Stripe SEPA payment at processing without waiting for the success webhook. The logic checks that the method is actually sepa_debit; cards are not marked as paid prematurely by this.

Increased payment failure risk: processing is not final payment success. The direct debit can later fail or be returned even though the booking has already been treated as paid. Activate this option only with a documented review process for subsequent errors and returned direct debits.

For scarce places or services provided immediately, assess this option particularly carefully. The safe default is to wait for succeeded.

Mandate and communication

Stripe collects the consent required for SEPA during payment. Your own booking and legal texts should clearly explain that a direct debit may be processed with a delay and how failures or returned direct debits are handled.

Check MustPay and countdown, the booking confirmation, and release of materials or access details. A processing status must not silently trigger services you intend to release only after final payment receipt.

Distinguish refunds from returned direct debits

A refund you initiate and a direct debit returned through the banking process are different transactions. V2 can refund a Stripe transaction with a remaining refundable amount through the normal refund process. A later provider error or returned direct debit, however, must be checked using the Stripe status and followed up in edoobox.

Test matrix

  • EUR offer with a visible SEPA method and correctly recorded mandate.

  • Non-EUR offer: SEPA is not offered.

  • Standard process: processing waits for succeeded.

  • Optional early process: recording at processing followed by checking a failure.

  • MustPay cancellation and a delayed webhook event.

  • Partial refund of a successfully recorded SEPA payment.

Stripe SEPA with connection status and validation option
AStripe Connect connectionBPayment system activatedCSEPA processing before the success webhook
Use case: Wait for final success

An organizer leaves the early option disabled. A SEPA payment remains pending during processing and is definitively recorded only at succeeded. Access details are also sent only after the final status.

Use case: A place is confirmed at processing

An organization reserves places immediately for long-standing members and activates the early option. A daily review process looks for subsequent payment_failed cases and returned direct debits. The possible loss is deliberately accepted and documented.

Use case: Non-EUR offer

A CHF offer shows no direct debit despite SEPA being enabled in the Stripe account. The team recognizes this as expected behavior of the edoobox PaymentIntent configuration and offers card or invoice instead.

Check the current connection and payment purpose

The Mark SEPA as paid without validation option is an early recording decision for an individual direct debit in the payment process. It sets up neither recurring collection for participant subscriptions nor company card billing for your edoobox account. For those, see Participant subscriptions: renewal and cancellation or Automatic payment with a saved credit card.

For every direct debit that fails later, compare the provider status with the payment already recorded in edoobox. A fee export uses the edoobox posting date, so it may relate to a different month than final bank processing: Export transaction fees as CSV.

Related guides