Integrations & API
The connections a school actually needs, and no marketplace of logos
Payment gateways, WhatsApp and DLT-registered SMS, biometric attendance devices, accounting exports, a REST API and webhooks. Listed with what each one actually does, and what it does not.
No integration charged as an add-on except where a third party charges us
Connects to
Razorpay
PayU
Cashfree
Stripe
WhatsApp Business
DLT SMS
Payments
Four gateways, and the reconciliation attached
A gateway integration that takes money is easy. What matters is that the settlement, the receipt and the ledger entry are linked afterwards, so “I already paid” takes ten seconds to answer with a transaction reference.
Razorpay
Cards, UPI, net banking and wallets. Settlement reports reconcile against receipts, and refunds initiated here reverse in the ledger.
PayU
The same flow. Widely used by schools with an existing PayU relationship and their own negotiated rate.
Cashfree
Including UPI Autopay for recurring instalments where a parent consents to a mandate.
Stripe
For international schools taking card payments from abroad. Fees are still billed in INR.
Your account, your rate
You connect your own gateway account. The gateway’s percentage goes to the gateway and we add nothing to it — which also means your negotiated rate is the rate.
Failed payment handling
A failed or abandoned payment does not create a phantom receipt. A payment that succeeded at the gateway but failed to return is reconciled from the settlement rather than lost.
Messaging
WhatsApp, SMS and e-mail — and the Indian rule that decides whether SMS works
This is the integration schools are most often misled about. In India, transactional SMS must be sent on a DLT-registered template. An unregistered message is dropped by the operator without an error, which means software can honestly report “sent” while nothing arrived on a single phone. We therefore require an approved template before a campaign can send, and we show you the delivery report rather than the send log.
- 01 WhatsApp Business API Template-based messages for fee reminders, absence alerts, results and notices, with delivery and read status. Your own WhatsApp Business number.
- 02 DLT-registered SMS Through your SMS provider, with the sender ID and template IDs registered on DLT. Templates are mandatory in the software, which is inconvenient once and reliable afterwards.
- 03 SMTP e-mail Your own SMTP or a transactional provider, so mail comes from your domain and does not land in spam as a shared sender would.
- 04 Voice call templates For schools that use automated voice announcements, on the same template discipline.
- 05 Delivery reports, not send logs The number that tells you the truth is on the same screen as the campaign, deliberately.
Devices
Hardware, with an honest answer about compatibility
Device integration is where vague promises cost schools money. The right time to check a make and model is before you buy, so bring yours to the call and we will confirm rather than assume.
Biometric attendance
Fingerprint and RFID devices that can export or push punch logs feed the same register the manual marking writes to — one source of truth rather than two lists.
Late arrival by real time
A punch after your cut-off is marked late automatically, which removes the argument about who decided.
GPS trackers
Vehicle position from supported trackers, used for the bus-started and stop-reached alerts. Without a tracker, the driver app can trigger those manually.
Barcode scanners
Any USB scanner works for library circulation and stock verification, because it presents as a keyboard.
Thermal receipt printers
For the fee counter and the canteen POS, on standard ESC/POS printers.
What we will not integrate
Facial recognition attendance and CCTV. Not a technical limit — a decision. We are not building systems that identify children by face.
Accounting
Most schools stop using Tally. Some CAs would rather not.
Because the fee module posts to a real double-entry general ledger with periods that close, the statutory statements come out of this system and a separate accounting package becomes unnecessary. In practice that is not always the decision a school gets to make — so the export exists for the CA who wants their own copy.
- 01 A complete general ledger here Trial balance, income and expenditure, balance sheet, day book, account ledgers and cash flow, all generated from posted journals rather than summed from receipts.
- 02 Tally-compatible export Vouchers and masters in the XML format Tally imports, so your CA can carry a period across without re-entry.
- 03 CSV for everything else Journals, ledgers and trial balance as CSV for any other package or for a spreadsheet review.
- 04 GST and TDS reports The data your CA needs for the returns. We compute correctly; we do not file on your behalf, and we would rather say so than imply a compliance guarantee.
API & webhooks
Your data, programmatically
A REST API and outbound webhooks, available on plans that include API access. Built for the two things schools actually ask for: pushing enquiries into a CRM, and pulling data into a reporting tool of their own.
REST API
Token-authenticated, scoped by the same permissions as a user. Students, staff, fees, attendance and results.
Lead webhooks
Every website enquiry and every trial signup posted to your CRM as it happens, including which plan was chosen.
Event webhooks
Admission enrolled, payment received, invoice raised. Signed, retried on failure, and visible in a delivery log.
Scoped tokens
A token carries abilities and a campus scope, so an integration cannot read more than the role it was issued for.
Bulk export
Everything, in open formats, at any time, by you, without asking us. This is the integration that matters most and it is on every plan.
Audit of API access
API calls land in the same audit log as human actions, with the token’s identity as the actor.
Questions
Integration questions
Something not answered here?
Will you integrate with the specific software we already use?
Ask, with the name and version, and you will get a specific answer — including “no” where that is the truth. What we will not do is say yes on a call and discover the gap during implementation. Where there is no integration, bulk export and the API usually cover the practical need, and we will tell you honestly whether they do in your case.
Do you charge for integrations?
No, except where a third party charges us or you. Payment gateways charge their own percentage, which goes to them. SMS credits are passed through at the operator’s rate with no margin. WhatsApp Business has its own per-conversation pricing from Meta. The integration itself is not an add-on line on our invoice.
Can we use our own payment gateway account?
Yes, and you should. You connect your own Razorpay, PayU, Cashfree or Stripe account, so settlements land in your bank and your negotiated rate applies. We do not sit in the payment path or take a share of it.
Why do you insist on a DLT-registered SMS template?
Because without one the message does not arrive. Indian operators drop unregistered transactional SMS silently — no error is returned — so any software that lets you send without a template will report a successful send for messages that reached nobody. Requiring the template is us refusing to show you a comforting number. WhatsApp and e-mail have no equivalent restriction.
Will our existing biometric devices work?
Often, and the honest answer depends on the make and model. Devices that can push or export punch logs generally integrate. Bring the model number to the call and we will confirm rather than guess — and where a device cannot integrate, manual marking on a phone takes about fifteen seconds per section, which most schools find acceptable.
Do we still need Tally?
Most schools stop using it, because the general ledger here produces the statutory statements from the same journals the receipts posted into. Where your CA prefers their own copy, the Tally-compatible XML export carries a period across. Both are supported; the choice is usually the CA’s rather than the school’s.
Is the API on every plan?
API access is on the higher plans; bulk export in open formats is on every plan including the lowest, because getting your own data out should never be a paid feature. If an integration is central to your decision, check which plan you need before you buy.
Can new signups and enquiries reach our CRM automatically?
Yes. Every website enquiry and every trial signup is posted to a webhook URL you configure, including the plan chosen at signup, the source and the school’s details. Deliveries are signed, retried on failure, and visible in a log so a missed lead is discoverable rather than invisible.
Next step
Bring the list of what you already use
Gateway, SMS provider, biometric model, accounting package, CRM. Twenty minutes and you will have a specific answer on each one, including where the answer is no.
- No card required
- Your data stays yours — export any time
- Setup help included