Two patterns reduce no-shows by 60-80%:
- Deposit at booking — customer pays a percentage upfront
- Card on file — customer authorises a card; you charge it if they no-show
Both work. They create different customer experiences.
How they compare
| Deposit | Card on file | |
|---|---|---|
| Customer friction at booking | High (pays now) | Medium (saves card) |
| Effect on bookings | -10 to -25% | -5 to -10% |
| No-show reduction | 70-85% | 60-75% |
| Ease of fee collection | Easy (already paid) | Medium (charge later) |
| Disputes | Low | Medium |
| Customer experience | Transactional | Trust-based |
| Tech requirement | Payment gateway | Stripe SetupIntent or similar |
When deposits win
Choose deposits if:
- Your services are high-cost ($150+) and the deposit is a meaningful percentage
- Your customer base is medical / specialist where prepayment is normal
- You have time-blocked services where the slot can’t be resold (e.g., 3-hour color appointments)
- You’re at booking volume where chasing no-show fees is expensive
For high-end salons, medical / dental specialists, and complex services, deposits work great.
When card-on-file wins
Choose card-on-file if:
- Your services are mid-cost ($30-150) and a deposit feels heavy
- Your customer base is consumer (salon, fitness, spa) where paying-before-service feels weird
- You want to minimise booking friction
- You don’t process online payments otherwise
For most consumer-facing service businesses, card-on-file hits the sweet spot.
How to implement deposits
Two patterns:
Fixed-amount deposit:
“$25 deposit required to book. Applied to service total.”
Simple, predictable, customer knows exactly what they’re paying.
Percentage deposit:
“30% deposit required. Remainder due at appointment.”
Scales with service price. Better for businesses with wide price range.
For most operators, a 25-50% deposit is the right level. Less than 25% doesn’t move no-shows much; more than 50% creates booking friction.
How to implement card-on-file
The flow:
- Customer fills out booking page.
- Before confirming, customer enters card details.
- Card is authorised (not charged) via Stripe SetupIntent or equivalent.
- Customer agrees to the no-show fee in plain language: “By booking, you authorise us to charge a $50 no-show fee if you don’t show or cancel within 24 hours.”
- Booking confirmed.
- If no-show: charge the card. Email confirmation of charge.
The “agree to fee at booking” step is critical — it makes the charge defensible if disputed.
Combining both
Some businesses use both:
- Deposit at booking (e.g., $25)
- Card on file for the no-show fee balance
This is overkill for most. Pick one.
What about cash-only customers?
Some service businesses are cash-only by tradition (older salons, some trades). For cash businesses, neither deposit nor card-on-file works.
Alternative: require a phone-call confirmation 24 hours before. Customers who don’t respond get the slot opened up (and called from a waitlist).
This is more labour-intensive but works for cash-first businesses.
How customers feel about each
Survey data and operator reports:
- Deposits: customers feel committed but slightly resentful at booking. Feels formal.
- Card on file: customers feel mildly cautious but generally accept. Feels modern.
For first-time customers, card-on-file has a lower abandonment rate. For repeat customers who trust the business, both work similarly.
Stripe / Razorpay setup
Both Stripe (US/UK/EU/IN) and Razorpay (India) support card authorisation without immediate charge:
- Stripe: SetupIntent → off-session PaymentIntent later
- Razorpay: Recurring/Authentication tokens
Most modern booking platforms (including Zedule) handle this flow natively. You just pick “card on file” or “deposit” in settings.