Deposits and no-shows
In buildAttach a cost to not turning up.
Deposit and card-hold policies for owned-channel bookings. Policy resolution runs today; no live charge, refund or payout path is available yet.
Stripe approval, legal review, capture, refunds, reconciliation and commercial pricing are launch gates.
The payment architecture is still a gate.
The intended design creates a charge against a merchant-owned connected account rather than pooling customer funds in a Bookesto balance. That intent still needs Stripe approval and UAE legal review. The platform fee is not fixed, and this page will not turn an open commercial decision into a permanent promise.

Charging a deposit is one of four levers, not the whole answer.
A deposit works when the counterparty is a customer. When the counterparty is a prospect, asking for money inverts the relationship — so commitment has to come from somewhere else. Bookesto treats no-show handling as a sequence rather than a single charge.
The fourth lever is the one nobody ships. Reminders exist everywhere and payment exists in several products, but no vendor in our survey feeds attendance outcomes back into who gets the next lead.
Policies
We are not going to quote you a no-show statistic.
Every number circulating on this topic traces back to secondary aggregations of a report we could not open as a primary document. We have no customers, so we have no data of our own either. What we will give you instead is measurement: a show-rate figure with and without a deposit policy, on your own account, so the answer comes from your business rather than from a vendor’s blog post.
Where deposits work today
| Region | Deposit rail | Status |
|---|---|---|
| United Arab Emirates | Stripe Connect (Custom) | Planned — pending Stripe platform approval |
| Everywhere Stripe operates outside the UAE | Your own Stripe account via a restricted key | Planned |
| Saudi Arabia | Stripe is not available; a second rail is an open decision | Gated |
| United States | Not a market we sell into | — |
Payment methods are cards and wallets, including Apple Pay and Google Pay. Direct-debit rails are not supported.
Questions about deposits
- Do you take any percentage of the deposit?
- The Bookesto platform fee is not decided or published. Processor fees and any Bookesto fee will be stated before the payment beta opens.
- Who is the merchant of record?
- The intended UAE design keeps the business as merchant of record and settles to its connected account. Stripe approval and legal review must confirm that flow before launch.
- What if I already use Stripe?
- The connection flow is not live yet. Eligibility and account requirements will be published after Stripe approves the platform setup.
- Can I refund from inside Bookesto?
- That is what the capture and refund path is being built for. Until it ships, refunds happen in your Stripe dashboard, where they always would have.
Get the build log and first access
The booking core is live and merchant access is invite-only. Get the changelog as it happens and an invitation when the private beta is ready for your business.
No card. Merchant access is invite-only — you get the build log and first access.