Razorpay with KIDUART
Razorpay is the default choice for Indian schools because parents already recognise it and it supports UPI, cards, netbanking and wallets in one checkout. In KIDUART, the parent opens the dues on the parent portal, pays through Razorpay, and the payment is written back against that student's fee record with a receipt number so the accountant is not matching a bank statement to a WhatsApp screenshot the next morning.
What you get
- UPI, cards, netbanking and wallets in one parent checkout
- Payments post against the student's fee record automatically
- Receipts generated from the same fee book the counter uses
- Signature plus webhook confirmation, so a payment is never recorded twice
- Failed and pending attempts stay visible instead of disappearing
The connection, hop by hop
How Razorpay actually works here
No hand-waving about being 'seamlessly integrated'. This is the path a single event takes, end to end.
Parent opens the dues
The parent portal shows outstanding fee heads for that student the same heads the front office sees, not a separate payment page.
Order created with your keys
KIDUART creates a Razorpay order using your school's own key and secret, held encrypted against your school record.
Payment verified twice
The checkout response is signature-verified, and Razorpay's payment.captured webhook confirms it independently before anything is marked paid.
Receipt and ledger written
The payment posts against the student's fee record with a receipt number, and shows up in due management and finance reports the same moment.
Keys, data and the bill
Who holds the credentials
Your Razorpay key and secret, stored encrypted against your school and never shared with another school on the platform.
Where the data sits
KIDUART stores the payment reference, amount and status. Card and UPI credentials are entered on Razorpay's checkout and never reach our servers.
Who gets billed
Razorpay's transaction fee is charged on your own merchant account, and settlement goes to your school's bank account. We are not in the money path.
Where it lands in the product
The modules this integration writes into
An integration is only useful if it writes into the module your staff already work in. These are the exact modules involved.
Setup, step by step
Connecting Razorpay
Open the finance settings in your school panel and choose Razorpay as the gateway
Enter the API key and secret from your Razorpay dashboard
Point the Razorpay webhook at the KIDUART endpoint we provide
Run a test payment against a demo student to confirm the receipt and ledger entry
Enable online payment on the parent portal for the classes you want
What you need on your side
- An active Razorpay merchant account in the school or trust's name
- Fee heads and structures already configured in KIDUART
- A finance or school admin role to enter gateway credentials
Questions schools ask
Razorpay, answered plainly
Does the money come to the school directly?
Yes. Settlement happens from Razorpay into your school's bank account under your own merchant agreement. KIDUART records the transaction and generates the receipt; we are not in the money path.
What happens if a parent's payment fails midway?
The attempt stays visible with its status, and the due remains open. Only a confirmed payment, verified through the webhook, closes the due and issues a receipt.
Can the same fee get paid twice?
The webhook is matched against the order already recorded, so a repeated notification updates the existing entry instead of creating a second receipt.
Can we still collect fees at the counter?
Yes. Cash, cheque and card collection at the counter run through the same fee module, so the dues list stays correct regardless of how a parent chose to pay.
See Razorpay in a live demo
We will run the connection on screen with your own scenario your fee book, your parent groups, your school accounts.
30-minute walkthrough
Booked around your school hours
Run on your own data
Your fee heads, classes and staff roles
No card, no lock-in
Nothing is charged to see the product