booking flow with payments and deposits

Here’s a simple booking flow with payments and deposits you can use for a service, rental, appointment, or event.

1) Customer selects booking

• Choose service/item/date/time/location
• See price, deposit required, cancellation policy, and availability

2) Booking details entered

• Customer provides contact info and any required details
• System calculates:
  • Total price
  • Deposit amount
  • Remaining balance
  • Taxes/fees if applicable

3) Payment options shown

Common options:

• Pay deposit now, rest later
• Pay full amount now
• Pay nothing now, hold booking (optional, usually with card authorization)
• Partial payment custom amount (optional)

4) Deposit payment collected

• Customer pays deposit via card, wallet, bank transfer, etc.
• Booking status becomes something like:
  • Pending payment
  • Confirmed with deposit
• Confirmation email/SMS is sent

5) Booking confirmation

• If deposit succeeds:
  • Reservation is secured
  • Customer gets receipt and booking details
• If payment fails:
  • Customer can retry or choose another method
  • Booking may remain unconfirmed for a limited time

6) Balance handling

Before service date:

• Send reminders for remaining balance
• Allow customer to:
  • Pay balance online
  • Pay on arrival
  • Convert deposit to partial credit if booking changes

7) Check-in / fulfillment

• Booking is used as normal
• Final payment is collected if not already paid
• Deposit may be:
  • Applied toward total
  • Refunded, partially refunded, or forfeited depending on policy

8) Cancellation / reschedule flow

• If customer cancels:
  • System checks refund rules
  • Deposit may be refundable, partially refundable, or non-refundable
• If rescheduled:
  • Deposit can be transferred to new booking if policy allows

---

Typical status flow

Draft → Pending Deposit → Confirmed → Partially Paid → Paid in Full → Completed

Alternative: Draft → Pending Payment → Expired/Cancelled

---

Important rules to define

• Deposit amount: fixed or percentage
• When booking expires if not paid
• Refund policy for cancellations/no-shows
• Balance due date
• Whether deposit is refundable
• Whether payment authorization or capture happens immediately
• Taxes, fees, and discounts handling

---

Example

• Total booking price: $200
• Deposit required: $50
• Customer pays $50 today
• Remaining balance: $150
• Balance due 24 hours before appointment or at check-in

If you want, I can turn this into:

1. a step-by-step user flow,
2. a database/schema design, or
3. a payment state machine diagram.