1. The tracking problem

Service businesses rarely lose money because they never charged. They lose it because payment and job live in different places — cash in a drawer, an UPI screenshot in a chat, an advance written on the job slip that later walks off. At month end, nobody can reconstruct what was actually collected.

The fix is not a new payment app. It is attaching payment state to the booking itself, so the job and its money are the same record.

2. How payments attach to bookings

On plans with payments enabled, each booking can carry its own payment state:

  • Advance or full payment at booking — collected online when the slot is reserved. This is the strongest no-show defence available: customers show up for appointments they have already paid for.
  • Part payment — an agreed amount now, the rest at the visit. Useful for high-value jobs where full prepayment is unreasonable.
  • Pay at visit — nothing collected upfront, but the "due" state is still recorded, so completion and collection can be checked against each other.
Whichever model you choose, the amount and its state sit on the booking — not in memory, not in a notebook.

3. Where Razorpay fits

Card and UPI payments are processed by Razorpay. The customer enters payment details on Razorpay's payment flow; the platform receives the outcome — paid, pending, failed — and records it against the booking.

  • Card and UPI details never touch the platform's records
  • Customers pay through the flow they already trust
  • Every payment is traceable back to its booking

4. Reading payment states

Payment states in practice

Illustrative example
StateMeaningAction
Paid onlineFull amount collected at bookingDeliver the service
Part paidAdvance taken, balance outstandingCollect balance at visit
Due at visitNothing collected yetCollect on completion

Illustrative data shown to explain how states appear in the product.

The operational habit this creates is simple: at the end of each day, every open booking either has its money or has a recorded reason why it does not.

5. Settlement and reporting

Collected payments settle to the business through Razorpay under its standard cycles. On advanced plans, settlement and payment reporting are available on the platform, so reconciliation starts from the booking records rather than from bank statements alone.

6. Refunds and cancellations

Refunds belong to whoever took the money. Booking payments were taken for the business delivering the service, so cancellation positions and refunds for them are handled by that business. Plan fees paid to Nishop Booking follow the Refund Policy. Either way, the rule is the same: the decision, the amount and the reason belong on a record, not in a negotiation later.

For plan structure and which plan includes payment features, see pricing. For security details, see the security page.