Skip to main content
NewNMC’s advertising guidelines for doctors are in force from 6 Oct 2026. See what to change, and get a free compliance auditNew NMC advertising rules for doctors: what to change
Website

Deposit and Payment Flows for Elective Surgery Bookings in India

How to choose a payment gateway and design refund states for consultation deposits and surgical package bookings, with the RBI turnaround rules your ledger has to respect.

Deposit and Payment Flows for Elective Surgery Bookings in India

Taking money online turns a booking form into a financial system. A patient pays a consultation deposit or a package advance, the bank debits them, and something in the chain fails: the page times out, the payment succeeds but the booking does not, or the appointment is cancelled and the refund state is unclear. The patient sees a debit and no confirmation, then calls the hospital, and the front desk has no reliable answer.

This post is for health tech founders, hospital product teams and the developers who build their booking and payment flows. It assumes you know how a payment gateway works and focuses on what is specific to healthcare bookings: deposits that may be partly refundable, package prices that are revised after a consultation, and the refund timelines Indian payment rules set. It is not legal or tax advice; your finance and legal teams must approve the policy, and the hospital's own refund and cancellation terms govern.

We link to RBI primary sources where we have confirmed them. We could not confirm every current detail of RBI's payment aggregator directions during writing, so where a point depends on them, we say so and tell you what to check.

Decide what you are charging for

Three payment types need different handling, even if they use the same gateway.

TypePurposeTypical refund logicDesign risk
Consultation feePay for a visitRefund if the hospital cancels or the slot is lost; policy for patient cancellationsPay-before-book creates a debit with no booking if the slot is taken
Booking depositHold a slot or a procedure datePartly or fully refundable by a stated ruleAmbiguity about what the deposit covers
Package advancePart payment on a quoted packageAdjusted against the final bill; refunded under policyQuote changes after clinical assessment

For elective surgery, the price is rarely fixed at the moment of booking. The final plan depends on the surgeon's assessment. A good flow takes a modest deposit tied to a consultation or a date hold, labels it clearly, and defers the package amount to the stage where the quote is confirmed by the clinical team. Avoid any wording that implies a price or outcome the clinician has not agreed. Claims about packages must pass the same review as other advertising, as set out in the NMC compliance handbook.

Choosing a payment gateway

Do the selection as a checklist, not a feature comparison.

Regulated status. A payment aggregator in India needs RBI authorisation, and the framework has been revised recently. Ask any gateway to state its authorisation in writing and check it against RBI's published list before you integrate. Do not rely on a sales deck.

Settlement and refunds. Ask how long settlement takes, whether refunds are deducted from future settlement or need a pre-funded balance, and whether partial refunds are supported. A deposit with a partial refund rule needs partial refund by API.

Methods. UPI, cards, net banking and wallets each fail differently. UPI has collect and intent flows and relies on the patient's app; cards can hit additional authentication; net banking redirects can time out. Offer the methods your patients use and test each in the gateway's sandbox.

Webhooks and reconciliation. You need reliable server-to-server notifications of payment success, failure and refund, with signatures you can verify and a way to fetch status on demand. The browser redirect alone is not proof of payment.

Recurring or instalment collection. If a package is paid in instalments by auto-debit, a separate set of rules applies. RBI's e-mandate framework for recurring online transactions is referenced in its circular on e-mandates; read the framework document it links to and ask the gateway how it implements it. For most booking deposits, a one-time payment is simpler and safer.

Data handling. Patient health details should not travel in payment metadata. Pass an opaque booking reference, not a diagnosis or procedure name.

The payment state machine

The most common bug is treating "payment" as a flag. It is a lifecycle, and your ledger should model it.

StateMeaningWho moves it
createdOrder created, nothing paidYour server
authorised or pendingPatient initiated; bank has not finalisedGateway webhook
capturedMoney receivedGateway webhook
failedPayment did not completeGateway webhook
refund_initiatedYou asked for a refundYour server
refund_processedGateway has sent the refundGateway webhook
refund_failedRefund could not be completedGateway webhook, needs human
reversed_by_bankAuto-reversal of a failed debitBank, gateway report

Two rules keep the model honest. First, only a verified webhook or a status fetch from the gateway moves a payment to captured, never the redirect URL. Second, every state change writes an immutable row with a timestamp and the source, so the finance team can answer "what happened to this payment" without guessing.

The three problems that cause support calls

Debited but not booked. The payment is captured and the slot booking failed, or the slot was taken between selection and payment. Design for it: create the booking hold before payment, make the payment bound to the hold, and have a job that finds captured payments with no confirmed booking and either completes the booking, offers alternatives, or refunds. Tell the patient on screen what is happening while it resolves.

Booked but not paid. The patient completed the payment, but the webhook is delayed. The booking page shows "payment pending". Poll the gateway for status for a short period, then show a clear message and send an SMS or WhatsApp update when it resolves. Do not release the slot instantly while the payment is in an unknown state.

Cancelled and refund unclear. The patient cancels, the doctor is unavailable, or the hospital reschedules. The refund begins and then vanishes into silence. Give the patient a refund reference, the method and the expected timeline, and let the front desk see the same state.

Want this applied to your practice? Get a free website audit.

Book my free audit

RBI turnaround times: what your refund promises must respect

India's central bank has set outer limits for resolving failed transactions and compensation for delay. The September 2019 RBI circular on harmonising turnaround time lists scenarios such as a UPI transfer where the beneficiary is not credited, which the beneficiary bank must reverse by T+1, where T is the transaction day, and a UPI merchant payment with no confirmation, which must be resolved within T+5, with compensation of Rs 100 per day beyond the limit in those cases. The circular states that the prescribed turnaround time is the outer limit and that compensation is credited to the customer's account without a claim.

Three practical consequences follow for a hospital product team. Do not tell patients a refund will arrive on a fixed day that your system does not control; say it depends on the bank and the method, and give the reference to quote. Do not treat a failed-debit auto-reversal as your refund; it is the bank's, and your ledger should record it as reversed_by_bank. And read the circular's table for the scenario your gateway falls under, because it does not specify a limit for every method. Check also for later RBI changes before relying on the 2019 text.

Your own refund policy for cancelled bookings sits on top of this. It should state, in plain words: what is refundable, when, to which method, who decides, and how the patient can follow up.

Reconciliation and finance

Run a daily reconciliation between three sources: your ledger, the gateway's settlement report and the bank statement. Match on gateway payment ID and your booking reference. Flag any item that is captured but not settled, settled but not in your ledger, or refunded at the gateway but not marked in your system. Give finance a view with filters for state, age and amount.

Generate a receipt or acknowledgement with the booking reference, amount, purpose (deposit, fee or advance) and the refund terms in short form. Tax treatment of different payments is a finance and legal decision; do not hard-code it in the front end.

Hypothetical walk-through

A 200-bed hospital in Pune takes a deposit to hold a consultation with a surgeon for a planned procedure. The patient selects a slot, the system holds it for a short time, and the payment is created against that hold. The bank debits the patient but the webhook is late. The booking page shows "payment pending" and polls; the webhook arrives and the booking confirms. In another case the patient pays but the hold has expired and the slot has gone. The reconciliation job finds a captured payment with no booking, the app offers the nearest slots, and if the patient declines, a refund is started and the patient sees the reference. The cases are invented to show the state logic; the amounts and timings would be set by the hospital.

Checklist before you launch

  • Payment types are labelled and separated: fee, deposit, package advance.
  • Gateway authorisation confirmed in writing and against RBI's list.
  • Partial refunds supported by API and tested in sandbox.
  • Payment status is driven by verified webhooks and status fetches, never the redirect.
  • All states above exist in the ledger with timestamps and sources.
  • A job handles captured payments with no confirmed booking.
  • Refund policy is written, approved by finance and legal, and visible before payment.
  • No clinical details in payment metadata.
  • Daily reconciliation runs across ledger, gateway and bank.
  • Front desk can see the same payment and refund state the patient sees.

For related build work, see our pages on payment and billing integration and appointment scheduling, and the earlier notes on booking optimisation and chatbot-led booking.

Filed underonline payment appointment booking hospitalconsultation deposit payment gateway Indiasurgery package booking paymentrefund handling payment gateway hospitalRBI failed transaction refund

About the author

Co-Founder & CTO · Gurugram, India

Arush builds the systems the rest of the company runs on — the patient-acquisition pipelines, the AI chatbots, the analytics that tie a single click to a booked appointment. If a campaign reports a number, it's because something his team built is tracking it.

Free guide · 13 pages

WhatsApp AI Chatbot for Hospitals (14-Day Deploy)

The 14-day WhatsApp booking-bot implementation playbook.

The Pioneers Brief — one essay, three benchmarks, one teardown, every Thursday. Subscribe free →

Free website audit

Your next chapter starts with a conversation.

Three quick questions. We come prepared with a plan for your specialty and city.

  • A 30-minute call with a healthcare specialist
  • Your top three growth opportunities, in writing
  • Honest advice — even if that means not hiring us
  • No obligation and no hard sell
You’ll speak with a senior strategist
Consultations are hosted by Arush Thapar’s team.
Step 1 of 3Takes 30 seconds

What do you want to improve first?

Details stay privateNo obligationReply within 1 working day

Client portfolio · Healthcare websites

Work relevant to deposit and payment flows for elective surgery bookings in india.

Explore client work →