https://resoflow-prod.web.app/assets/what-guests-pay-DpY18A_K.js

1!function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{};e.SENTRY_RELEASE={id:"1.0.0"};var a=(new e.Error).stack;a&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[a]="3b11e478-adfc-4607-ad95-a874644d4915",e._sentryDebugIdIdentifier="sentry-dbid-3b11e478-adfc-4607-ad95-a874644d4915")}catch(o){}}();const e="__RESOFLOW_HELP_BODY__",a="**Settings → Payments and deposits → What guests pay** (/dashboard/settings/what-guests-pay) is the one page for everything a booking can be asked to pay — a deposit, the full price, a card to hold for a no-show fee, and money for dishes chosen while booking — and for when money comes back. It replaced the separate Deposits, Pay in full and No-show protection pages: old links and bookmarks open the right section here. Pre-orders keeps its own page for who is invited, the dishes and the kitchen screens; only its money is set here. Owners and Admins can open it, and any money taken goes straight to your own Stripe account ([connect Stripe](connect-stripe) first).\n\nThe page reads top to bottom in the order a payment is decided, with one save bar for all of it.\n\n## Which payment a booking is asked for\n\nOnly one payment is taken per booking. The first section, **Which payment a booking is asked for**, lists the order, each step with what it does for you right now:\n\n1. **Dishes paid for while booking** — pre-order money (*Available on Pro plan and above*).\n2. **Pay in full** (*Available on Pro plan and above*).\n3. **Deposit** (*Available on Plus plan and above*).\n4. **Card to hold** — a saved card for a no-show fee (*Available on Plus plan and above*).\n5. **Nothing to pay.**\n\nThe first of these that applies to a booking is what it's asked for, and everything below it is skipped. **Which wins:** \"Dishes paid for while booking beat pay in full; pay in full beats a deposit; a deposit beats a card to hold.\" So a booking that pays in full is never also asked for a deposit or a card, and a booking that pays a deposit is never asked to save a card. Within each one, \"A special date beats your day-and-time rules, which beat your everyday rules.\"\n\n**Where payments apply:** only online — your booking page and website widget ask for the payment. When a booking your team adds needs one, nothing is taken automatically: you're offered a payment link to send, and your team's bookings are never asked for a card. Walk-ins and the waitlist are never asked to pay.\n\n## What a booking pays\n\n**What a booking pays** is a live example. Pick a **Date**, a **Time**, a **Party size** and **Online** or **Your team**, and it says what that booking would be asked for, and why — for example \"This booking pays a £20.00 deposit when it's made.\" It uses the same reckoning as your booking page, and your settings as they are on the page, unsaved changes included, so you can see what a change would do before you save it. It also says when a special date has its own refund cut-

1off, when a booking would wait for your approval, and when a party is too big to book online (a group's request pays nothing).\n\nTo check every booking rule, not just the money, use **Try a booking** on Booking rules at a glance — see [How do I check which rules apply to a booking?](try-a-booking)\n\n## The four payments\n\nEach has its own section; switch on the ones you want. Deposits and full payments can be set **Per person** (the default — 4 guests × £5 = £20) or **Per booking** (one amount, whatever the party size); the no-show fee is **Per booking** (the default) or **Per guest**. Amounts you set before this choice existed keep their meaning. In **Tiered deposits by party size** and **Tiered amounts by party size**, the amount column is headed **Per person** or **Per booking** to match.\n\n- **Deposit** — **Require deposits**, the amount, a **Minimum party size** and **Tiered deposits by party size**. **Deposit: when you ask for one** narrows it to **Days and times** and lists **Event deposits** (a date's own deposit, set on Special dates). See [How do I take booking deposits?](deposits-setup) and [How do I take deposits only on busy days or special dates?](deposit-schedule)\n- **Pay in full** — **Require full payment**, the amount, a **Minimum party size** and **Tiered amounts by party size**, with its own day and time rules and dates. See [How do pay-in-full bookings work?](pay-in-full-bookings)\n- **Card to hold** — **Enable no-show protection**, **Card required to complete booking**, the **No-show fee**, a **Minimum party size** and the **Safety delay before charging**. Under **More options**, **Days and times** asks for a card only when you choose (say Friday and Saturday dinner), and **Special dates** can hold a card with their own fee — or hold none that day. The section's own **Which wins:** line: \"Pay in full beats a deposit; a deposit beats a card to hold.\" See [How do I charge no-show fees?](no-show-protection)\n- **Pre-order money** — **How is a pre-order paid?**: **Paid at the venue**, **The pre-order total is the payment**, or **Deposit, then pay for the food online**. Who is invited, and until when, stays on Pre-orders. See [How does pre-ordering work for large bookings?](pre-orders-large-bookings)\n\nA date with its own deposit, full payment or pre-orders is set on **Settings → Bookings → Special dates**, with everything else about that date; the lists on this page show what's set, with a link there. A special date's own payment applies on its date even when that payment's switch is off. See [What's different about Christmas Day? (Special dates)](special-dates)\n\n## Cancellations and refunds\n\nOne set of rules covers every payment taken at booking — deposits, full payments, pre-order money and paid extras. The **Cancellations and refunds** section shows what happens when a customer cancels, as three steps: until when they can cancel or change online, what they get back, and what happens after that. Its rows:\n\n- **Cancelling and changing online** — your cancellation deadline, shown here with a **Change** link to its home on When people can book.\n- **Cancellation policy** — **No refunds**, **Full refund** or **Partial refund**, with the **Refund percentage** for a partial one.\n- **Refund cut-off** — how long before the booking a customer must cancel to get money back (default 24 hours; 0 = right up to the booking time).\n- **Your customer cancellation terms** — the sentences customers agree to, rebuilt from these settings.\n- **Also charge for late cancellations** — the no-show fee for a customer with a saved card who cancels inside your cancellation deadline.\n\nA special date can have its own refund cut-

1off (its **Money back if they cancel**, on Special dates), and bookings made for that date keep it. After a paid booking is moved, the refund deadline counts back from whichever is earlier — the booking time that was paid for or the new time — so a move can never stretch the deadline (moving a booking later leaves it where it was; moving it earlier brings it forward). The one exception to the policy: when a party paying in full per person gets smaller, the difference is always refunded. Confirmation and reminder emails only promise a free cancellation when a cancellation really is free. See [When do customers get their deposit back?](deposit-refunds)\n\n**Where the money goes** closes the page: your Stripe connection, and refunds, which always happen in ResoFlow on the booking itself.\n\n## If your plan changes\n\nA payment your plan doesn't include isn't charged to customers — its section waits under **More options** with a padlock. One left switched on after a plan change stays at the top of its section with a working **Switch off**, and rules you already have stay listed so you can remove them; they work again if you upgrade. Switching a payment off always works, on every plan.\n\nRelated: [Where are my booking rules? (Booking rules at a glance)](booking-rules-at-a-glance) · [What does the customer see when paying a deposit or saving a card?](guest-payment-experience) · [What's different about Christmas Day? (Special dates)](special-dates)";export{e as __helpBodySentinel,a as default};
2//# sourceMappingURL=what-guests-pay-DpY18A_K.js.map