How do I charge no-show fees?

Save a guest's card at booking (every day, or only on the days, times and dates you choose) and charge a fee — per booking or per guest, after a reversible safety delay — when your team deliberately mark a no-show.

No-show protection saves a guest's card when they book online — nothing is charged at booking — and lets you charge a fee if they deliberately fail to turn up. Set it up in the Card to hold section of Settings → Payments and deposits → What guests pay.

It's Available on Plus plan and above, needs Stripe connected (connecting is owner-only), and only Owners and Admins can open the page.

Stripe not connected: guests book without a card

Until your Stripe account can take payments, Enable no-show protection and Card required to complete booking can't be switched on — the section says Connect Stripe first and links to Payouts and Stripe. If they're already on when Stripe isn't connected (or Stripe pauses card payments), the section says no-show protection isn't working: your booking page doesn't ask for a card, online bookings go through without one, and no no-show or late-cancellation fee can be charged on them. Owners and admins get a bell row ("Connect Stripe — online bookings are going through without a card or payment") on each day it happens, and Connect Stripe shows on Home's set-up card. Switching protection off always works.

Switching it on

Only on certain days, times or dates

Under More options in Card to hold:

"A special date beats your day-and-time rules, which beat your everyday rules."

The two extra switches

How the fee is actually charged

Switching no-show protection off also stops queued fees whose payment request has not started. Requests already processing are checked with the payment provider; they are not treated as cancelled or unpaid without a confirmed outcome. Completed charges keep their normal refund options. The booking shows when a queued fee was stopped or a payment still needs checking.

Only a member of your team deliberately marking the booking as a no-show and choosing to charge ever arms the fee (the Who can charge it row says so) — the automatic no-show system never charges, and a guest who showed up is never charged. Arming the charge asks you to confirm your password — and needs the Refund payments and deposits permission — or a manager's PIN from someone who has it. After the safety delay the saved card is charged and the guest is emailed. If their card is declined, the guest is emailed a secure link to pay with any card and you're alerted; if their bank said "not now" (not enough money, a temporary problem) the card is tried once more automatically 24 hours later, and your team can press Retry charge on the booking once. A strict fraud rule you set in your own Stripe account (Stripe's Radar rules) can also block the charge — it's treated just like a declined card.

The card is only held while the booking is live. As a deliberate privacy protection, the guest's saved card is released automatically the moment their booking finishes — marked completed or cleared, or cancelled. That means a fee can only be charged by marking the no-show directly: once a booking has been completed or cleared, switching it to a no-show afterwards can't charge anything, because the card has already been released. Marking a no-show itself never releases the card, so the charge decision at that moment works as normal.

Only online bookings are ever asked for a card (your booking page and website widget) — bookings your team takes, walk-ins and the waitlist never are. "Pay in full beats a deposit; a deposit beats a card to hold": bookings that already pay — a deposit or a pay-in-full booking — won't also be asked to save a card; the payment covers the no-show risk, and the fee never applies to a paid-in-full booking. A booking with only paid extras or a pre-order to pay saves its card once: it pays for them and is kept for no-shows — and when that booking waits for your approval, the card pays them when you approve and stays as its no-show card from then (declining the request releases it). One exception: a special date with its own Hold a card replaces your everyday deposit and pay in full that day, so guests booking it save a card instead (the date's own deposit or pay in full, if it sets one, still comes first). A charged fee can be refunded later from the booking (password confirmation, or a manager's PIN approval).

Related: How do I mark a no-show (and charge the fee)? · When is a no-show fee actually taken? · When can guests book? · What does the guest see when paying a deposit or saving a card? · How do I ask a guest to save a card after they've booked?

A failed card refund after a no-show fee

On the Payments page, open the amber strip ("1 payment review needs your attention") — the Fee payment reviews list is inside; it's on the booking too. The strip only shows while something needs reviewing. The review shows money returned by Stripe, completed repayments recorded by your venue, and the exact amount still outstanding. Current and earlier fee payments stay separate.

If Stripe confirms the original refund failed and the money returned to the venue balance, an owner or a manager explicitly granted Record completed no-show fee repayments can record a bank transfer or cash repayment after the guest has received it. Enter the exact completed amount, payment date, a unique transaction or receipt reference, the reason and the guest's agreement. Review the details, then confirm again with your password or an authorised manager's PIN. Do not enter bank details, card numbers or contact information in the reference or reason.

ResoFlow records that completed repayment; it does not send a bank transfer or cash. Partial repayments leave the remaining amount in the review queue. A recorded venue repayment never becomes a Stripe refund, and the original failed refund stays in the payment history. If Stripe later reports conflicting money, the review keeps both amounts visible so you can investigate before any further action.