EdPayU familyFamily homeEdPayU+ — you are hereEdPayU · the school app →
Deploy & white-label

Runs where you say.
Wears your name.

Three deployment shapes, one product. The families see your brand, the money moves through your gateway, the messages send from your registered identity. Ownership is not a tier — it is the default.

The three shapes

Same product,
three places it can live.

Shared cloud

  • Your institution at its own subdomain — the address is yours
  • Fastest to start; we operate everything
  • The shape most institutions should pick first

Your own domain

  • The web and parent apps at your domain, your certificate
  • Sign-in happens at your address, not ours
  • Our name appears nowhere a family looks

Your own server

  • On campus or in your datacentre, for data-residency mandates
  • A supported deployment we ship to — not a do-it-yourself edition
  • Priced honestly: on-premise costs more to support, and we say so

What is yours

Which parts of a deployment belong to the institutionThe domain, DLT sender identity and payment gateway are registered to the institution, not to the vendor. The platform sits behind them and can run on shared infrastructure or on the institution's own server.Registered to youyour.schoolyour domainSender IDyour DLT registrationGatewayyour merchant accountEdPayU+ platformwhite-labelled — the family never sees a vendor nameRuns where you chooseManagedYour own server
The parts a family sees — the domain, the sender identity, the payment gateway — are registered to the institution. Moving vendor does not move them.

Bring your own

The credentials stay
in your name.

Payment gateway

  • Your merchant account, your settlement, your reconciliation
  • Fees land in your bank without touching ours
  • Leaving us never means re-boarding a gateway

Messaging identity

  • Your SMS credentials on your DLT registration
  • Your WhatsApp business number, not a shared pool
  • Parents see the institution calling, because it is

Mobile apps

  • Your icon, your name, your store listing when you want one
  • Publishable under your developer account or ours
  • One codebase underneath — updates reach every brand

Why this matters at exit

Ownership you never have to negotiate back.

Most white-label stories in this market are paint: the vendor’s gateway with your logo, the vendor’s SMS pool with your name typed into the sender field, an app that is yours until the contract ends. The difference here is structural. The merchant account is yours from day one, so the money never routes through us. The messaging identity is yours, registered to you, so switching vendors never silences your communication. The domain is yours, so the address families have bookmarked keeps working whatever happens to us.

This is also why the exit clause can be real. Full export on demand is easy to promise when the vendor holds everything; it is only worth something when the things that are hard to move — the merchant relationship, the sender identity, the address — were never moved in the first place. We built it that way because we sell to institutions that measure vendors in decades, and a vendor that plans your exit honestly is one you can afford to stay with.

Tell us where

Cloud, your domain, or your server — the scope session covers all three with real numbers.

Chat with us