SEPA Direct Debit payments

The Single Euro Payments Area (SEPA) is an initiative of the European Union to simplify payments within and across member countries. They established and enforced banking standards to allow for the direct debiting of every EUR-denominated bank account within the SEPA region. Stripe currently supports the SEPA Direct Debit Core scheme and not the SEPA Direct Debit B2B scheme. The Core scheme supports both business and personal bank accounts.

To debit an account, businesses must collect their customer’s name and bank account number in IBAN format. During the payment flow, customers must accept a mandate that gives the business an authorization to debit the account. Stripe is able to generate this mandate for businesses to present to their customers. Locate the ID of the mandate used for this payment on the Charge under the payment_method_details.sepa_debit.mandate property. Then, use the mandate ID to retrieve the Mandate.

SEPA Direct Debit is a reusable, delayed notification payment method.

SEPA Direct Debit transactions have a limit of 10,000 EUR each. For new users, there’s an additional weekly limit of 10,000 EUR, which quickly increases as you process more SEPA direct debit payments. If you need higher limits, contact support.

Verification Requirements

Using SEPA Direct Debit requires you to complete additional identity verification steps. We prompt you to complete these steps after you request access from the Payment methods settings. If you require further assistance, please contact support.

Payment flow

Get started

You don’t have to integrate SEPA Direct Debit and other payment methods individually. If you use our front-end products, Stripe automatically determines the most relevant payment methods to display. Go to the Stripe Dashboard and enable SEPA Direct Debit. To get started with one of our hosted UIs, follow a quickstart:

• Checkout: Our prebuilt, hosted checkout page.
• Elements: Our drop-in UI components.

Other payment products

The following Stripe products also let you add SEPA Direct Debit from the Dashboard:

• Invoicing
• Payment Links
• Subscriptions

If you prefer to manually list payment methods or want to save SEPA Direct Debit details for future payments, see the following guides:

• Manually configure SEPA Direct Debit as a payment
• Save SEPA Direct Debit details for future payments

Timing

With SEPA Direct Debit, it can take several business days for funds to become available in your Stripe balance. The number of business days it takes for funds to become available is called the settlement timing. Payments are generally submitted on the same day that they’re created, but are processed on the following business day if they’re created on a non-business day or after the cutoff time.

You can access the expected_debit_date for SEPA Direct Debit under payment_method_details for Charges. This is an estimated date of when the funds might be debited. This estimate isn’t guaranteed and the actual date might vary. This information is available in API responses and in charge.updated, charge.succeeded, and charge.failed webhook events when the debit date can be determined.

The following table describes the settlement timings for SEPA Direct Debit payments that Stripe offers. T+x refers to x business days after submission, which might differ from the payment creation date.

Faster Settlement Private preview

Faster Settlement lets eligible users of SEPA Direct Debit make funds available for payout in two business days before the payment succeeds. Payments can still fail after funds become available. If that happens, Stripe immediately removes the funds from your balance.

Debit notification emails

The SEPA Direct Debit rulebook requires that you notify your customer each time you debit their account. For this case, by default, Stripe automatically sends the customer an email.

If you decide to send your customer a custom notification:

• Turn off Stripe emails in the Stripe Dashboard email settings. However, if you use the Sources API, you can only control emails using mandate.notification_method (for more information, see notifying customers of recurring payments).
• Use the payment_intent.processing event to trigger debit initiation emails.
• The email must include:
  • The last 4 digits of the debtor’s bank account
  • The mandate reference (sepa_debit[reference] on the Mandate)
  • The amount to be debited
  • Your SEPA creditor identifier
  • Your contact information
• It’s standard to send notifications at least 14 calendar days before you create a payment. However, SEPA rules let you send notifications closer to the payment date—just make sure your mandate clearly states when customers can expect to receive a notification. The mandate provided by Stripe specifies this can happen up to two calendar days in advance of future payments, allowing you to send notifications at payment creation. For recurring payments of the same amount (for example, a subscription of a fixed amount), you may indicate multiple upcoming debits with corresponding dates in a single notice.

Connect

To use SEPA Direct Debits in a Connect integration, you must enable SEPA Direct Debit on your platform and request the sepa_debit_payments capability for your connected accounts.

Creditor Identifiers (Creditor ID)

A SEPA Creditor Identifier (Creditor ID) is an ID associated with each SEPA Direct Debit payment that identifies the company requesting the payment. While companies may have multiple creditor identifiers, each creditor identifier is unique and allows your customers to easily identify the debits on their account.

By default, your Stripe account is configured to use a Stripe Creditor ID when collecting SEPA Direct Debit Payments. The Creditor Name that appears on bank statements is determined by the following order of priority:

1. Your business name or legal entity name. For Connect, Stripe defaults to using the connected account’s business name if available. If not, Stripe uses the platform account’s business name.
2. Your Stripe account’s custom statement descriptor. For Connect accounts, Stripe defaults to the connected account’s statement descriptor if available. If not, Stripe uses the platform account’s descriptor.
3. A default Stripe name (for example, “Stripe Technologies Europe Ltd”)

We recommend:

• Configuring a recognizable statement descriptor to help customers identify payments and reduce the risk of disputes.
• If you’re based in the EU, use your own Creditor ID to both reduce dispute rates and improve your customer experience. You can configure your own Creditor ID on the Payment Method Settings page in the Dashboard.
• If you’re using the Stripe Creditor ID, use Stripe Checkout to collect mandates from your customers for SEPA Direct Debits.

Creditor identifiers and Connect

The charge type of Connect payments changes the creditor identifier and name which appear on the customer’s bank statement.

Mandates

Before you can create a SEPA Direct Debit payment, businesses must collect a mandate that authorizes Stripe to debit the account on their behalf. Instructions for collecting mandate acceptance can be found on the Accept a payment page.

Customers can request the cancellation of a mandate at any time. To cancel a mandate, a customer must either reach out to the party they established the mandate with, or to their bank. Canceling a mandate invalidates any future debit requests that you issue using this mandate. If you want to accept additional payments from your customer, you need to establish a new mandate with them. Stripe only learns about a canceled SEPA mandate when a payment attempt fails, after which Stripe sets the mandate as inactive and sends a mandate.updated webhook event.

Mandate cancellation

Mandate cancellation makes sure that no further debit requests can be made using the canceled mandate. When a customer requests cancellation through the party they established it with or directly through their bank, it renders any future debit requests associated with that mandate invalid. You can also cancel active mandates by detaching the payment methods and sources associated with them. You can detach a payment method by deleting it from the Customer view in the Stripe Dashboard or by using the API.

Failed payments

SEPA Direct Debit payments can fail for various reasons, such as insufficient funds, closed accounts, or missing authorization.

Payment timing and failures

SEPA Direct Debit payment failures can occur up to 6 business days after the payment is initiated. Review the following payment failure timeline:

Submission phase (1-2 business days)

• Your payment is submitted to the customer’s bank.
• Payments created before the daily cutoff time (10:30 CET) are submitted the same day.
• Payments made after the cutoff are submitted the following business day.

Refusal window (5 business days)

• After submission, there is a 5-business-day period (the “refusal window”) during which the customer’s bank can reject the payment. This is when most failures occur.
• The bank can return the payment during this period.

Final settlement

• After the 5-day refusal window, the payment is considered final.
• Failures can still occur after this point.

Understand failure information

When a payment fails, Stripe provides detailed information to help you understand the issue. The failure_code field on the Charge indicates the specific reason for the failure, and the failure_message field provides a more detailed description of why the payment failed. Stripe immediately removes funds from your Stripe balance after failures.

The following table lists the possible SEPA Direct Debit failure codes with recommended next steps.

Disputes

SEPA Direct Debit provides a dispute process for customers to dispute payments.

Customers can dispute a payment through their bank on a “no questions asked” basis up to eight weeks after their account is debited. Any disputes within this period are automatically honored.

After eight weeks and up to 13 months, a customer can only dispute a payment with their bank if the debit is considered unauthorized. If this occurs, we provide the bank with the mandate that the customer approved upon request. This doesn’t guarantee cancellation of the dispute. The bank can still decide that the debit was unauthorized and the customer is entitled to a refund.

When a dispute is created, Stripe sends a charge.dispute.created webhook event, and deducts the dispute amount and fee from your Stripe balance. The dispute fee varies based on your account’s default settlement currency.

Unlike credit card disputes, SEPA Direct Debit disputes are final and there is no process for appeal. If a customer successfully disputes a payment, you must contact them if you want to resolve the situation. If you come to an arrangement and your customer is willing to return the funds to you, they must make a new payment.

In general, each dispute includes the reason for its creation, but this varies from country to country. For example, disputed payments in Germany don’t provide additional information for privacy reasons.

If a payment is disputed, and that payment is associated with a multi-use mandate, that mandate could be deactivated. Make sure to check the status of such mandates after a dispute. You have to re-collect mandate acceptance from your customers if their previous mandate is deactivated.

Refunds

You can refund SEPA Direct Debit payments for up to 180 days after the original payment. You can refund part of the original payment or the entire amount of the original payment. Refunds are free of charge but the processing fees for the original payment are non-refundable.

Refund timing and processing

• Refunds typically take 3-4 business days to process, and funds arrive in the customer’s account within 5 business days.
• Refunds must be submitted within 180 days of the original payment.
• SEPA refunds appear as credits in the customer’s bank account with a reference to the original payment’s statement descriptor, rather than being explicitly labeled as refunds.

Important considerations

Customers can dispute a payment with their bank even after you’ve issued a refund, potentially resulting in two credits for the same payment. This happens because SEPA’s longer processing times can create confusion between you, your customer, their bank, and Stripe.

New accounts attempting refunds may have refunds temporarily disabled while Stripe reviews the account for fraud prevention. This review typically takes up to 2 business days.

When to issue refunds

Stripe recommends issuing SEPA Direct Debit refunds only when:

• The customer is trusted and verified
• You’ve confirmed with the customer that you’re processing the refund
• At least 7 business days have passed since the original payment

Customer communication

Always inform customers immediately when issuing a refund, explaining that it may take up to 5 business days to appear in their account.

If you accidentally debit a customer, contact them immediately to prevent disputes.

If you need assistance processing a refund, contact Stripe support.

Fraud Protection for SEPA with Radar

Stripe Radar provides fraud protection capabilities for SEPA Direct Debits without any additional development time, performing real-time evaluation using machine learning algorithms to help identify and block high-risk transactions. Our machine learning trains specifically for SEPA, so it’s effective at detecting fraud that might be unique to SEPA Direct Debit payments.

For Radar users, Radar might default to on for all supported payment methods.

Billing Retries Private preview

With Direct Debit retries, Stripe can automatically retry failed Direct Debit payments caused by insufficient funds. You can turn on retries for recurring subscription invoices, one-off invoices, or both.