SEPA payments in travel agencies: how to secure and streamline them
In short
To secure SEPA payments in a travel agency, start by knowing that they are usually direct debits. The debit is confirmed only after at least six business days, and the traveller can get it refunded by their bank, with no reason given, for eight weeks. Good practice: collect the balance early, keep cards for deposits and last-minute payments, warn the traveller before the debit, and track every payment on its booking.
A traveller pays their €6,000 balance by SEPA, ten days before departure. The payment page says the payment is in progress. At best, the debit is confirmed six business days later, a few days before departure. Even once confirmed, it can still be reversed for eight weeks, with no reason given. By then the traveller is long back home.
This is how SEPA Direct Debit normally works. An agency that knows it can plan its collections around it.
SEPA credit transfer or SEPA direct debit: what is the difference?
Both carry the SEPA name, but they work in opposite directions.
SEPA Direct Debit
A euro payment started by the creditor, here the agency, on the payer's account. The payer authorises it once by accepting a mandate. They keep the right to ask their bank for a refund.
| SEPA credit transfer | SEPA Direct Debit | |
|---|---|---|
| Who starts the payment | The traveller, from their bank | The agency, under the traveller's mandate |
| Amount and reference | Typed by the traveller | Set by the agency |
| Dispute | No equivalent procedure | No reason needed for 8 weeks |
When an online payment solution offers to "pay by SEPA", it is almost always a direct debit. The traveller enters their IBAN on the payment page and the agency triggers the debit. A classic bank transfer is still possible, but it happens outside the payment page, and reconciling it is manual work.
How long does a SEPA Direct Debit take to confirm?
At least six business days. According to Stripe's SEPA Direct Debit documentation, a successful payment is confirmed at T+6 business days after submission. A payment created on a non-business day, or after the processing cut-off, goes out on the next business day.
Most failures happen within those six days. Stripe therefore advises not to treat a direct debit as successful before then. In rare cases a failure arrives later, in the form of a dispute.
For an agency the rule is simple: a SEPA payment in progress is not money collected. Don't confirm a non-refundable service or send travel documents until the debit is confirmed.
Can a traveller reverse a SEPA Direct Debit?
Yes. Under the SEPA rules, as Stripe summarises them, the payer can get an authorised direct debit refunded by their bank with no reason for eight weeks after the debit. Without a valid mandate, the debit counts as unauthorised and can be disputed for thirteen months.
Three things make this right harder to handle than a card chargeback:
- The bank refunds automatically any claim made within eight weeks.
- There is no defence. Stripe lets you neither submit evidence nor appeal: the dispute is final.
- Getting the money back goes through the traveller. If you reach an agreement, they have to make a new payment.
The dispute cancels the payment, not the contract. If the traveller did travel, the money is still owed, and the signed contract is the basis for claiming it.
Card dispute deadlines, which run much longer for a trip, are covered in our article on chargebacks for travel agencies.
Why do SEPA Direct Debits fail?
Stripe lists about a dozen failure reasons. The ones an agency meets most often:
| Reason | What to do |
|---|---|
| Insufficient funds | Ask the traveller to top up their account, then send the request again |
| Invalid IBAN or closed account | Collect new bank details |
| Direct debits blocked on the account | Ask the traveller to lift the block with their bank |
| Wrong account holder name | Redo the payment with the exact account holder name |
| Mandate revoked | Have a new mandate accepted |
A failure costs more than time. It shows up several days after the request, which eats into the margin before departure.
How to secure SEPA payments in a travel agency
Before accepting a SEPA payment
- Set the balance due date early enough to absorb six business days, and a possible second attempt.
- Keep cards for deposits and last-minute payments: they confirm in seconds.
- Warn the traveller about the upcoming debit, with the amount and date. An unexpected debit is a classic reason for a dispute.
- Have your cancellation terms accepted before payment, and keep the signed contract.
- Wait for the debit to be confirmed before committing non-refundable costs.
- Above €10,000, split the amount or offer card payment.
The first point pays off the most. If your balance is due 30 days before departure, a failed debit still leaves three weeks to recover. Five days before departure, it leaves none. Our article on how much deposit to ask for and when the balance is due covers these dates.
The limit comes from Stripe: €10,000 per direct debit. A new account is also limited to €10,000 per week, a cap that rises with the volume processed.
How to streamline SEPA payments
Send a link, not bank details. With a payment link, the amount and reference are already set. The traveller enters their IBAN and accepts the mandate on the same page, with no paper form. The payment arrives attached to the right booking. Our guide to payment links explains how.
Let the traveller choose. Offer card and direct debit on the same request. A traveller in a hurry pays by card, one settling a large balance picks SEPA. Our card vs SEPA comparison works out the fee gap by amount.
Track statuses, not the bank statement. A direct debit goes through three states: in progress, succeeded or failed. Seeing them on the booking saves watching the bank account for a week.
Plan one link per instalment. On a payment plan, the direct debit does not run by itself on each date: the traveller pays each instalment from a link. Only cards can be charged automatically. See our article on travel payment plans.
How does SEPA Direct Debit work in Ezus Pay?
- On each link, if the agency wants it. A link offers card payment by default. The agency ticks SEPA Direct Debit if it wants to. It is only available for a booking in euros.
- The mandate on the payment page. The traveller enters their IBAN, reads the mandate text and confirms. There is nothing to print or sign separately.
- A payment in progress status. The traveller sees that the payment is being processed. On a payment plan, the instalment switches to payment in progress and the form is no longer offered to the traveller, to avoid paying twice.
- A failure that blocks nothing. The payment shows as failed in the transactions, and the link stays active so the traveller can try again. An instalment goes back to pending.
- Flat fees. SEPA Direct Debit costs 0.3% plus €0.30 per transaction, excluding VAT. On a €6,000 balance, that is €18.30 excluding VAT.
- Refunds possible. An agency administrator can refund all or part of a direct debit from Ezus Pay. Stripe accepts the refund up to 180 days after the payment.
Disputes are received by the Ezus Pay team, who notify the agency. To compare direct debit with other ways of collecting payment, see our comparison of payment solutions for travel agencies.
Ezus Pay is the payment solution built for travel agencies, DMCs and tour operators. It lets you collect by card or SEPA Direct Debit and track every payment on the right booking, with or without Ezus.