A booking business has a payment problem that a shop does not: the money arrives before the service exists. A slot is reserved, a deposit is taken, and between that moment and the appointment sits everything that can go wrong — a cancellation, a no-show, a reschedule, a customer who forgot they booked at all.
None of that makes bookings hard to bank. A merchant account for booking is a vertical where the payment design matters more than the rate, and where the businesses that get approved quickly are the ones who can describe what happens when a client does not turn up.
Contents
- What the model does to your payments
- Deposit, full prepayment or pay on arrival
- What the application asks
- What it costs
- Connecting the booking system
- Cutting disputes in a diary-driven business
- Seasonality and capacity
- In short
What the model does to your payments
- The charge precedes the service. Short by travel standards — days or weeks — but long enough for a dispute to arrive before you have done anything.
- Cancellations are routine. They are part of the product, not an exception, and every one of them runs back through acceptance.
- No-shows are a payment question, not a scheduling one. Whether you keep the deposit, and whether the customer agreed to that in writing, decides how the dispute ends.
- Reschedules break the paper trail. A payment made in March for an appointment moved to June is a charge the customer no longer recognises.
Which band a business lands in overall is set out in our piece on what high-risk, middle-risk and low-risk payments are.
Deposit, full prepayment or pay on arrival
A deposit is the usual answer: enough to make the slot real, small enough that a dispute is not a disaster. It converts better than full prepayment and it removes most no-shows on its own.
Full prepayment fits fixed-price, short-notice services and anything where your cost is committed the moment the booking is made. It also raises the dispute exposure, so it belongs with a clear, accepted cancellation policy.
Pay on arrival with a card on file is the most convenient for the customer and the most demanding technically: the consent has to be explicit and stored, and the later charge has to be recognisable. Recurring mechanics of that kind are unpacked in our piece on merchant accounts for subscription businesses.
What the application asks
The company set is standard — registration, articles, beneficiaries, licences where the activity requires them. The vertical part is short and decisive.
- What exactly the customer buys, and how long after payment they receive it.
- Your cancellation and no-show policy, visible on the site and matching what the checkout says.
- Who performs the service — you, employees, or independent practitioners you settle with.
- What happens when you cancel. Illness, closure, overbooking: the answer belongs in writing before it is needed.
The full document list is in our merchant approval checklist.
What it costs
MDR runs 3%–5% depending on the type of business, plus 0,50 EUR per transaction — and on small deposits that fixed fee is the line that matters, not the percentage. Settlement in EUR over SEPA is 0,20%, the term is T+7, the rolling reserve is 10% for 180 days. A refund costs 50,00 EUR, a chargeback 100,00 EUR on top of the returned amount. The exact figure is set per merchant and we consider individual solutions for your business.
Two consequences for a booking business. A twenty-euro deposit carries the fixed fee as a visible share, so very small deposits taken very often are worth modelling before launching. And because refunds are frequent by design, the refund line belongs in the pricing conversation from the start. All published lines sit on the pricing page.
Connecting the booking system
Ready plugins cover WordPress and OpenCart; a booking calendar that is not a shop usually connects through the API, and a payment link covers everything taken by phone or in a message. What sits behind all of them is described under payment processing.
The money settles into an account in the company’s name, described under business IBAN.
Cutting disputes in a diary-driven business
- Get the policy accepted, not just published. A tick box at booking with the cancellation terms beside it is the evidence that decides a no-show dispute.
- Put the service and the date in the descriptor. «Clinic name, 14 March» is recognisable months later; a holding company is not.
- Remind before the appointment. The reminder that reduces no-shows is the same message that prevents the dispute.
- Re-confirm after a reschedule. A moved appointment needs a fresh confirmation naming the original payment.
- Refund fast when you cancel. Fifty euros beats a hundred, and a refund does not count against the dispute ratio.
Seasonality and capacity
Bookings are not flat: a season, a campaign or a single busy weekend can multiply volume, and unannounced spikes get reviewed. Say in advance when your peaks are and how large they get. A declared peak is planning; an undeclared one is an anomaly.
In short
Bookings are banked on the strength of the cancellation story. Choose the model deliberately — deposit, prepayment or card on file — get the policy accepted rather than merely published, keep the descriptor recognisable, remind before the appointment and re-confirm after a move. Then the merchant account behind the calendar is an ordinary product on ordinary terms.

