A card deposit at booking through your own Stripe or Razorpay account, applied to the visit’s bill.
Installs with PayLinks and PayRails, whose screen it works on · Offered in: United States, United Kingdom, Canada, Australia, India only.Takes the deposit your booking policy asks for at the moment of booking, on your own processor’s hosted page — Stripe Checkout (card, and ACH, BACS or BECS where your Stripe account offers them) or a Razorpay Payment Link — so a slot is held against a real payment instead of a name on a calendar. No card field and no processor script runs on a page we serve: Stripe or Razorpay holds the card, and this keeps only their references. A deposit is marked paid when the processor’s webhook arrives signed with your own secret (a delivery that does not verify is refused; a retried one changes nothing), or when the processor answers a status check as the patient comes back. When the patient is seen, a person applies the deposit to the visit’s own bill — same patient, once — as an advance; anything beyond what the bill owes is held as the patient’s credit. A deposit paid after its slot was released is flagged for a refund or a credit, and a refund goes back through the same processor only on a person’s confirm, at most what was taken, once per payment, with an idempotency key. The online part needs the clinic’s own Stripe or Razorpay account: until its key and webhook secret are in the clinic’s key settings the screen says “not connected” and what to add, and deposits paid at the desk still go on the bill from here.
/card-depositscarddeposit.readWhat it does not do, by design. A listing with only benefits is an advertisement.
Read out of the code, not the brochure: each app below is here because one service queries the other’s tables. Install either side and the hand-over is already wired.
Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.