Bookings, deposits and cancellations: avoid taking payment when a slot is full
A booking needs both a confirmed place and a payment record. Rescheduling, cancellations and refunds must follow the same rules.

The workflow illustrates a possible design and is not a client case study.
- Hold capacity
- Confirm payment
- Confirm or release
Why can a paid booking remain unconfirmed?
A customer pays, but their booking stays pending. Another cancels and still receives reminders. When payment and availability are handled separately, staff have to sort out the mismatch. What happens if two people book the last place, payment arrives late or a customer closes the checkout page?
Which booking rules should you check?
Calendly can collect payment when an appointment is booked. Try an existing product for straightforward appointments, then test your less usual rules. Shared rooms, instructors and equipment, visit credits and staged deposits may need more configuration or development. Check the plan’s limits before deciding.
Take one booking from hold to cancellation
Use one service and one payment method to work through a whole booking: hold the place, confirm payment, notify the customer and release the place if they cancel. Staff should be able to use the booking reference to find its payment and handling history. Agree the refund conditions and who can approve a refund as part of this trial.
Test the final available place
Have two people book the last place at the same time and check who gets it. Follow with delayed and repeated payment notifications, rescheduling and partial refunds. Include daylight-saving changes for bookings across time zones. For each test, compare what the customer sees with availability, payment and staff records.
Bring your service and cancellation rules
List your services, capacity, cancellation policy and current payment platform, with examples of awkward cases. Available payment methods depend on the service region and account settings; you can add them in stages.