Booking System With Online Payments: How Pay-at-Booking Actually Works

BookrHub Research · Published 5 September 2026 · Sources: Baymard Institute, Israel Journal of Health Policy Research, SchedulingKit, Zenoti, Small Business Trends · Product behaviour verified against the BookrHub application source

"Can I take payment online?" is the wrong question to ask a booking system, because every one of them says yes. The question that actually separates them is what happens in the ninety seconds between a customer choosing a time and their card clearing — whether the slot is held or still open to someone else, what happens if they abandon the page, who the money belongs to when it arrives, and what you can do about it afterwards. Those details determine whether online payment quietly protects your calendar or quietly loses you bookings. This page answers them for BookrHub specifically, including the parts that are deliberately not built.

The three models people mean by "online payments"

Three genuinely different mechanisms hide behind the same phrase, and buying the wrong one is the most common source of disappointment after migrating.

BookrHub implements the first model. The full price of the service is charged at booking time, and the appointment is not confirmed until that payment succeeds. If you are shopping specifically for a percentage deposit or a stored card for no-show fees, that is worth knowing on this page rather than three weeks into a migration — the limits section below is explicit about it.

How payment at booking works in BookrHub

Payment is not a global switch that makes every booking cost money. BookrHub asks for payment only when all three of the following are true:

1. You are on the Business plan. The free Independent and Team tiers never request payment, regardless of settings. This is deliberate: a business that once ran payments and later downgraded will not keep charging customers by accident.
2. A payment provider is connected and active. If no provider is configured, bookings simply confirm as they always did.
3. The service has a price above zero. A service priced at 0 is confirmed instantly with no payment step, so free consultations, taster sessions and trial classes coexist with paid services on the same booking page.

When those conditions are met, the customer's booking is created with the status payment required rather than confirmed, and a deadline is stamped on it ten minutes into the future. The customer lands on a payment page showing the appointment, the amount, and a countdown to that deadline. The moment the payment succeeds, the booking becomes confirmed, its payment status becomes paid, and the confirmation emails go out to the customer and to you.

What the customer sees

The payment page is part of the booking flow, not a bounce to a third-party invoice. It shows the business name, the booking summary, the amount, and a countdown timer that ticks down in real time. If more than one provider is available for that currency, the customer picks between them; if only one is, it is preselected and there is nothing to choose. With Stripe, the card form is embedded directly on the page. With Mercado Pago, the customer continues to Mercado Pago's own Checkout Pro screen and comes back automatically once approved. If the countdown reaches zero while the page is still open, the form is replaced by a clear expiry notice and a link back to the booking page to start again — rather than a card form that silently fails on submit.

The ten-minute hold, and why the timer is the interesting part

Every booking system that takes payment has to answer an uncomfortable question: is the slot taken while the customer is typing their card number?

Answer "no" and you can sell the same 3pm twice, which is worse than a no-show because now you have two people expecting a service and one of them will be turned away after paying. Answer "yes, forever" and any abandoned checkout permanently poisons a slot — a browser tab closed at 11pm on Tuesday quietly removes Saturday at 3pm from sale, and nobody notices until the week is over.

BookrHub answers "yes, for ten minutes." Concretely:

• The booking exists immediately, so nobody else can take the slot. It occupies the calendar as a payment-required booking, visible in your admin.
• A deadline is recorded on the booking itself, and the customer sees it counting down.
• A background job sweeps for unpaid bookings past their deadline, cancels them, cancels the associated pending payment record, and emails the customer to say the hold expired.
• The slot returns to your availability automatically. No manual tidying, no stale holds accumulating in the calendar.

The part worth respecting is the race condition, because this is where naive implementations lose money. A customer's payment can confirm at the exact moment the expiry sweep is running. BookrHub handles this by locking the booking during payment confirmation and by making the cancellation a conditional update — it only cancels rows that are still unpaid, still payment-required, and still past their deadline. It also re-checks for a successful payment before touching anything. A booking that got paid while the job was mid-flight is never cancelled. The customer who paid at 9:59 keeps their appointment.

Stripe, Mercado Pago, and why currency decides

Two providers are live in BookrHub today, and which one a customer is offered is decided by the currency of the booking rather than by a preference setting.

Because Stripe is configured with automatic payment methods, whatever you have enabled inside your own Stripe dashboard shows up in the embedded form without any additional work in BookrHub — cards, Apple Pay, Google Pay, and the local methods Stripe supports in your country. You configure payment methods where they belong, in your processor, and the booking page reflects it.

Mercado Pago matters for a reason that is easy to miss from Europe or North America: in much of Latin America it is not an alternative to cards, it is the default way people pay online. Digital wallets hold roughly a 30% share of Argentina's payments market, the highest in the region, and Mercado Pago is the largest driver of that. A booking page for a Buenos Aires or Montevideo business that only offers an international card form is asking a meaningful share of its customers to pay in a way they do not normally use. Baymard's abandonment data lists "insufficient payment methods" as a reason 9% of abandoners give — a small number globally, and a much larger one when the missing method is the one everybody in your city uses.

One practical consequence of currency-based routing: BookrHub only offers a provider that supports the booking's currency, so a business whose currency is not covered by the provider they connected will not see a working payment step. Check your currency against the table above before switching payments on.

Where the money actually goes

This is the difference that compounds, and it is structural rather than promotional.

You connect your own Stripe or Mercado Pago account by entering your own API credentials. When a customer pays, the charge is created directly against that account. The money settles into your bank on your processor's normal schedule. BookrHub is not in the flow of funds at any point, does not hold a balance on your behalf, and adds no application fee or platform commission to the transaction. You pay your processor's published rate, and nothing else.

That has three consequences worth stating plainly:

• 0% commission on bookings. Whether you take ten appointments a month or a thousand, the payment path costs the same: your processor's fee. There is no per-booking cut and no separate rate for customers a marketplace decides are "theirs".
• The customer relationship is yours. The charge appears on their statement under your business, via your account. You are not renting access to your own clients.
• You own the exceptions. Refunds, partial refunds, disputes and goodwill gestures happen in your dashboard, on your terms. The flip side, covered below, is that they happen in your dashboard rather than in BookrHub.

Credentials are stored encrypted, and a Stripe secret key is validated with a real authenticated API call when you save it, so a mistyped key is rejected during setup instead of discovered by a customer at checkout. Keys beginning sk_test_ are recognised as test mode, so you can run the entire flow end to end — hold, countdown, expiry email and all — before a single real card is charged.

What BookrHub does not do

Being specific about the boundary is more useful than implying coverage. As of September 2026, BookrHub's payment feature does not include:

• Partial or percentage deposits. The full service price is charged. There is no "20% deposit" setting. The workaround is to sell a low-priced booking-fee service and settle the balance in person, which is a workaround, not a feature.
• Card on file and automatic no-show fees. No card details are stored for later charging, so a cancellation policy is enforced by conversation, not by an automatic charge.
• Refunds from inside BookrHub. Refunded and partially-refunded states are recorded against a booking, but the refund itself is issued in your Stripe or Mercado Pago dashboard.
• PayPal, Afterpay, buy-now-pay-later or bank-transfer providers. Records exist for PayPal, Afterpay and POLi, but none of them can currently process a payment.
• Tips, gift cards, packages, memberships or retail products. The payment is for the booked service, at its listed price.
• In-person card terminals. BookrHub handles the online payment attached to a booking, not point-of-sale in the chair.
• Payments on the free plans. Payment at booking is a Business-plan capability.

If a percentage deposit or automatic no-show charging is genuinely non-negotiable for your business, this is the honest place to find that out.

What the evidence says about prepayment

Prepayment is usually sold with a single confident number attached. The published evidence is more interesting, and more mixed, than the marketing.

The most rigorous data comes from healthcare, where no-shows have been studied for decades. A 2023 policy review in the Israel Journal of Health Policy Research examined proposed legislation to charge non-refundable co-payments at booking, and surveyed what the existing research actually shows. The results do not point one way. A mental-health clinic study found a $30 fine cut no-shows among high-risk patients from 20.1% to 9.27%. A Danish orthopaedic study covering 6,746 patients found no difference at all between the fee and no-fee groups, both sitting around 5%. The authors' own conclusion was that the proposed charge would likely have minimal effect on attendance, and that improving access mattered more than penalising absence.

The reasonable reading is that a financial commitment changes behaviour when it is large enough to feel like a loss, and does nothing when it is a token. That fits the intuition of anyone who has run a service business: a $5 deposit is a rounding error to someone who has decided not to come.

A note on sourcing: the deposit-adoption figures above come from SchedulingKit's 2026 roundup, which aggregates vendor and survey data rather than conducting primary research. They are directionally useful for market context and should not be read as peer-reviewed findings. The healthcare and abandonment figures are from the primary sources named.

The cost of asking for money upfront

Requiring payment does not only filter out the customers who were never going to show. It also filters out some who would have. Baymard's aggregate abandonment rate of 70.22% is an e-commerce figure and a booking page is a friendlier context, but the reasons transfer intact: 19% of abandoners cite card security concerns, 17% a checkout that felt too long or complicated, and 9% the absence of the payment method they wanted. A first-time customer who has never met you, on a phone, at 11pm, is precisely the person those numbers describe.

So the case for pay-at-booking is not "you will get more bookings". It is a trade: fewer bookings, each worth more, with less of your week spent on people who do not arrive. Whether that trade is good depends almost entirely on whether your constraint is demand or capacity.

Turning prepayment on without losing bookings

• Start with your most expensive service, not all of them. Because payment is triggered per service by its price, you can require payment on a four-hour colour correction while a thirty-minute trim stays pay-in-person. The service most damaged by a no-show is the one that should be protected first.
• Keep free services free. A service priced at zero skips the payment step entirely. Consultations, patch tests and trial classes should stay frictionless — they are how new customers meet you.
• Say the amount before the payment page. Baymard's most-cited abandonment reason is unexpected cost. If your booking page states the price plainly next to the service, the payment page confirms an expectation rather than springing a surprise.
• Run it in test mode first. A Stripe key starting sk_test_ puts the provider in test mode. Book a real appointment against yourself, let the timer run out on purpose, and read the expiry email your customer would get. Ten minutes of rehearsal is cheaper than one confused customer.
• Set your cancellation window before you set your prices. BookrHub defaults to 24 hours' notice for cancellations and 2 hours for reschedules. Decide what you will refund outside and inside that window, write it where customers can see it, then apply it consistently — the money is in your account, so the policy is genuinely yours.
• Watch the pending-payment total on your dashboard. The Business-plan dashboard reports the value of bookings awaiting payment alongside revenue, average booking value and cancellation rate. A pending figure that keeps climbing is telling you the payment step is losing people, not that business is booming.
• Do not treat payment as a substitute for reminders. The evidence for prepayment is mixed; the evidence for reminders is not. Do both. Our guide to reducing no-shows covers the reminder side in depth.

Who should require payment — and who should not

The businesses that get the most out of pay-at-booking share one trait: their scarce resource is time they cannot resell. A tattoo artist holding a full day, a physiotherapist with a single treatment room, a colourist whose four-hour appointment cannot be backfilled at short notice, a class instructor whose room has twelve places — for all of them an empty slot is permanently lost revenue, and a smaller number of certain bookings beats a larger number of uncertain ones.

The businesses that should be careful are the ones still building demand. A new barbershop with gaps in the diary does not need a filter on the top of its funnel; it needs bookings. The same is true where the cultural default is to pay in person, or where the service is cheap enough that ten minutes of card-entry friction costs more than the occasional no-show.

Most businesses are somewhere in between, which is the real argument for per-service pricing rather than an all-or-nothing switch: protect what is expensive and hard to refill, keep everything else easy to book.

Related reading: how to take payments for appointments online, handling cancellations, client management, and staff management.

References

1. Leibner, G., Brammli-Greenberg, S., Mendlovic, J., & Israeli, A. (2023). To charge or not to charge: reducing patient no-show. Israel Journal of Health Policy Research, 12, 27.
2. Baymard Institute. (2026). Cart Abandonment Rate Statistics. (aggregate of 50 studies, 2006–2025)
3. SchedulingKit. (2026). Appointment Deposit Statistics. (aggregating Square Appointments, Salon Today, GetApp, Capterra and vendor platform data)
4. Zenoti. (2026). Survey Data: Key Salon and Spa Consumer Trends Shaping Appointment Management.
5. Small Business Trends. (2026). Zoho Bookings Survey Shows Small Businesses Still Struggle with Scheduling.
6. EBANX. (2026). What is Mercado Pago? The Latin American digital wallet.