Skip to content

Integrations

What Vidyapeeth360 connects to — and what it deliberately doesn’t.

Every integration below is described exactly as it ships: whose account it runs on, what your school configures, and where the boundary sits. Nothing on this page is a roadmap item, and the not-offered list is published on purpose.

  • School-owned gateway accounts
  • School-approved message templates
  • Boundaries stated in writing

The connected services, one card each — including what each one does not do.

Live integration · school-owned account (BYOG)

Payment gateways — your own account

Collect through your own Razorpay or Cashfree account. Provider callbacks update the invoice being paid; final settlement timing, deductions and bank credit remain provider and bank evidence for the school to reconcile.

Vidyapeeth360 never pools or routes your fee money — collections settle to the school's own gateway account.

Configured per school

WhatsApp & SMS

Configured WhatsApp and SMS workflows using school-approved templates — announcements, fee reminders and configured parent communication.

Provider onboarding, template and DLT approval, consent, acceptance, delivery and read evidence remain channel-specific; the product itself is not “DLT-compliant”.

Configured per school

Transactional email

Transactional email via SendGrid or your own SMTP, logged into the same delivery view as the other channels.

Record preparation & import — not a live government link

UDISE+ & APAAR record preparation

Prepare UDISE+ and APAAR records, review readiness findings, manage consent evidence and import an APAAR ID after it is generated through the government process.

Vidyapeeth360 does not generate APAAR IDs and has no live UDISE+ synchronization.

Built in · optional live registry check

GSTIN verification

GSTIN validation with optional live registry verification for the school's billing details.

Export path · reviewed with your accountant

Tally-oriented accounting exports

Export accounting vouchers in a Tally-oriented XML format, alongside CSV exports on the statements your accountant already works from.

Device scope confirmed per deployment

Biometric attendance devices

A supported biometric device can feed the attendance register so presence is recorded from the device event rather than a manual roll call.

Device models, connectivity and server scope are confirmed for your deployment before rollout.

Reviewed during implementation

DigiLocker

A deployment-specific DigiLocker integration can be reviewed during implementation.

Not a general-availability live push; no government synchronization is promised.

One-time setup and recurring charges for integrations (WhatsApp setup, payment-gateway setup, biometric devices and server connectivity, Tally, GPS and more) are published in the cost schedule on the pricing page. The approved scope and tax treatment for your school remain written-order terms.

Not offered — stated plainly

  • Aadhaar e-KYC. Identity documents are uploaded manually and reviewed by the school administrator.
  • Live government synchronization. There is no live UDISE+, DigiLocker or ABC data link; record preparation and post-generation imports are the shipped scope.
  • Split settlement of school fees. Collections run on the school's own gateway account — never pooled through ours.

If a vendor conversation depends on one of these, bring it to a walkthrough — we would rather lose an evaluation than mis-describe a boundary.

Reviewing the trust posture behind these connections? See who processes your data (and how to get our DPA), the Security overview and the DPDP guide for schools.

Bring your providers. We’ll map the exact fit.

Your gateway, your message channels, your accountant’s workflow — a walkthrough confirms each connection against your school’s real setup before you commit.