Included in No-Show Shield
Payments & deposits
A booking with money attached behaves differently
$600Days 8–14 of the build
The leak
The economics of a cancellation. When payment happens after the service, a no-show costs everything and recovers nothing.
Stripe collection built into the booking flow, with deposit rules set per appointment type — so the highest-value slots are the protected ones.
Where this sits
This module is part of No-Show Shield. It is not sold on its own, because the handoff between it and the module beside it is where revenue actually escapes.
Journey stage 4 · They arrive — or they do not
Payment after the service means a no-show costs everything and recovers nothing. A booking with no money attached is a reservation, not a commitment.
The full value of the slot, plus the staff time spent preparing for it and chasing it.
Handoff · Payment
High leakUnowned: After the service, so a no-show recovers nothing.
Owned by this module: Payments & deposits
What gets built
The deliverable, stated the way the contract states it
Card payment and deposit collection inside the booking flow itself, plus saved payment methods at Tier 2 so a returning client does not re-enter a card to rebook.
At a glance
- Itemised value
- $600
- Build window
- Days 8–14 of the build
- Sold inside
- No-Show Shield
Yours at handover — domain, accounts, data and source code.
How it works
The mechanism, not the marketing
Trigger on the left, the rule the system applies in the middle, the consequence on the right. Read it as the logic your practice would otherwise be running in someone's head.
book.yourpractice.com/checkoutIllustrative interface
| Appointment type | Deposit rule | Effect on the slot |
|---|---|---|
| Routine visit | No deposit | No friction added where little revenue is at risk |
| High-value treatment | Deposit collected at the point of booking | The booking carries a commitment, not just a reservation |
| Returning client | Saved card, managed by them in the Stripe portal | Rebooking stops being a payment conversation |
- Your Stripe account
- Card data never reaches your database
- Reconciled against the booking
Capabilities
What it does, and why that matters commercially
Deposits inside the booking flow
Collected at the point of booking, not requested afterwards by email. Payment friction removed from the moment of intent.
Deposit rules per appointment type
Protect a crown seat or a high-value treatment slot without adding friction to routine visits. The rule follows the revenue at risk.
Saved cards via the Stripe Customer Portal
At Tier 2, clients manage their own saved payment methods. Rebooking stops being a payment conversation.
Payouts and reconciliation you can read
Payments reconcile against bookings in the owner dashboard, so the schedule and the money are not two separate stories.
Implementation
How this gets built, and when it is done
Same standard as every module: a milestone you can verify yourself, not a status report.
Timeline
Days 8–14 of the build
Definition of done
The build is accepted when the client can complete a live booking, receive a reminder, and complete a test payment without error.
Built on
- Stripe
- Stripe Customer Portal
- Next.js server routes
Deployed on infrastructure registered in your name. You hold the accounts, the data and the source code when the build completes.
Who it matters most for
The practices where this leak is largest
Every practice loses something here. These are the ones where it is the dominant loss rather than a minor one.
Med spas & aesthetic clinics
Deposit-less bookings walking away. High-value treatment slots held with nothing attached to them, then released hours before.
Med Spa & Wellness systemsDental practices
Two separate leaks: same-week no-shows, and recall appointments that were never rebooked at all. The second one is larger and almost never measured.
Dental systemsPhysiotherapy & chiropractic clinics
Cancellations concentrate mid-plan. The patient feels better around visit four, cancels visit five, and never reschedules the remaining seven.
Physio & Chiro systems
This module on its own is a smaller answer
It closes one leak. The reason it is sold inside a tier is that the next leak sits immediately beside it, and an unowned handoff costs the same whether or not the module beside it is good.
Questions
Payments & deposits, in detail
Do we have to require deposits?
No. Deposits are configurable per appointment type, including off entirely. We will tell you where we think the risk sits and you decide.
Whose Stripe account is it?
Yours. Funds settle to your account directly. We build against it; we do not sit between you and your money.
Are card details stored on our system?
No. Card data is handled by Stripe and never touches your database. Your system stores a token reference, not a card number.
Next step
Find out what your booking flow is costing you
Send the four numbers your practice already has. You get a written figure for the monthly revenue your current flow is leaking, and a recorded teardown of where it goes. Three business days, no obligation, no call required.
- 20 minutes discovery call, only if you want one
- 90-Day No-Show Recovery Guarantee
- 3 new practices a month