Payment adapters per market: UPI in India, cards and ACH in the US, SEPA across Europe, and mobile money — M-Pesa, MTN MoMo, Airtel Money — across Africa, where the phone is the bank. One reconciliation model behind every rail so the day-close is the same screen everywhere.
How you actually use it
1Add the public half of a merchant accountOn Accounts, Add an account: the processor — razorpay, phonepe, cashfree, paytm, stripe, upi_qr or manual — what to call it, the public reference (a Razorpay key id, a PhonePe merchant id) and, for a gateway-free UPI QR account, the VPA. The form has no field for the secret on purpose.
2Seal the secret in KeysThe key lives sealed in Keys under the payments purpose. Verifying it there is what sets Status and Checked on the account; nothing on this screen can read it back. Disable and Enable switch an account off and on.
3Read what the counter can doRails declared counts the rails active accounts carry. Cash and bank transfer always work; a card or UPI payment refuses at the counter while no account carries the rail, and the screen says so rather than hiding it.
4Payments and card machinesPayments lists every payment from the moment the counter asks for one — before the patient pays — with its rail, processor, reference, status and when it settled; only a succeeded, unreconciled payment can be matched to a receipt. Card machines lists each registered machine with when it was last heard from.
5AutopayStanding authorisations lists each UPI Autopay or e-mandate with its ceiling and whether the payer has given it; Check asks the processor again. Debits carry a reference you choose, the same reference twice is the same debit, and the database refuses a debit above the ceiling. A debit the processor has not answered stays pending and is never turned into a receipt.
See it on screen
Live product01Payment Methods — Take payments however your country paysCaptured from the running demo clinic
1 of 1
Connected to
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.
Same patient record as every other app — nothing is copied into a silo. Data class: PHI-lite.
What it does not do
It does not store card or account credentials — every rail hands off to its processor, and the platform keeps only the reference.
Every app page carries this section. A listing with only benefits is an advertisement.
Questions clinics ask
What data does PayRails read and write?
PayRails reads bills, processor callbacks and writes payment intents, reconciliations. Its data class is PHI-lite. Every app works on the same patient record — nothing is copied into a silo.
What does PayRails deliberately not do?
It does not store card or account credentials — every rail hands off to its processor, and the platform keeps only the reference.
What happens to our data if we uninstall PayRails?
Every record stays; only the workflow leaves.
Is PayRails available today?
Yes — PayRails is live in clinics today. Set up your practice on MedAppz and install it from your dashboard.
Ask about PayRails
Want to see PayRails running on your own patients?
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.