Parents pay in two taps, receipts post themselves

Online payment is only useful if the receipt is right

Many schools added a payment link and then discovered a new problem: parents who paid but got no receipt, receipts for payments that actually failed, and an accountant reconciling the gateway report against the fee register every evening.

SSMS never trusts the browser alone. When a parent pays, the receipt is created only after the server verifies the payment with the gateway — the order, the amount and the currency. The browser return, the gateway's webhook and a reconciliation job that re-checks pending orders every few minutes may all arrive; database locks make sure only one receipt is ever created.

Your money goes to your account

The payment gateway account belongs to your school (Razorpay first, with other gateways following the same design), with its secrets stored encrypted. Money settles directly in your bank, not through SSMS. Separate accounts can be used later for transport or a canteen run by another entity.