The accountant has done this before, just never for the school.
She has an eSewa account. Personal. She's used it to pay for a mobile top-up, split a dinner bill, buy a movie ticket. So when the principal asks her to "just set up online fee payment," her first instinct is to open the eSewa app on her own phone and look for a way to add students to it.
That's where it stops working. A personal eSewa or Khalti wallet can receive money from another person, but it can't generate a fee invoice, can't tell you which student a payment belongs to, and can't be searched by the tax office without raising questions about whose account 40 lakh rupees a year is actually passing through. What the school needs is a business account - a merchant account, in eSewa and Fonepay's language, or a listed institution, in Khalti's. That's a different application, with different documents, sitting behind a different login.
This is where most schools get stuck. Not because digital payments are complicated, but because nobody explained the difference between "I have Khalti" and "my school is registered with Khalti as a merchant." This guide walks through exactly what that setup looks like - the documents, the account types, the settlement timing, and how Khalti, eSewa, and Fonepay actually compare for a school's specific needs.
Why a Personal Wallet Doesn't Work for School Fees
A personal Khalti or eSewa account is built for one person spending their own money. It has no concept of "student," no way to batch-generate invoices for 400 families, and no separation between this month's fee collection and the accountant's own transactions.
There's also a compliance problem. If parents are sending fee payments into an individual staff member's personal wallet, that money is legally ambiguous - it's not clearly the school's income, it's not clearly traceable for audit, and if that staff member leaves, the school has just lost visibility into a chunk of its fee history. Schools that discover this the hard way usually do so during an audit, when nobody can produce a clean list of who paid what through which personal account.
The fix is a registered business account. eSewa calls it a merchant account. Khalti calls it listing your institution as an education merchant. Fonepay works through your bank's merchant QR program. In all three cases, the account is tied to the school's own PAN and bank account, not an individual's phone number - which means the money, the records, and the audit trail all belong to the institution, not to whoever happened to set it up.
What eSewa, Khalti, and Fonepay Actually Are
It helps to know what you're actually applying to, because these aren't casual apps operating in a grey zone. Nepal Rastra Bank (NRB), the central bank, regulates digital payment providers under the Payment and Settlement Act, 2075, and licenses them into two categories: Payment Service Providers (PSPs), which offer wallets and payment services directly to users and merchants, and Payment System Operators (PSOs), which run the underlying settlement infrastructure that connects banks and wallets to each other.
eSewa and Khalti are both licensed by NRB as Payment Service Providers. Fonepay operates as a Payment System Operator - it's the interoperable network that lets a QR code on your school's counter accept payment from practically any bank app or wallet in Nepal, not just one brand. NRB's Payment Systems Department is the body that issues these licenses, sets the rules, and publishes the list of who's authorized to operate.
That distinction matters practically. eSewa and Khalti are the two options where a parent pays directly out of a wallet balance they've topped up. Fonepay is what makes it possible for a parent who only has a bank's mobile banking app - not eSewa, not Khalti - to still scan a QR code at your school and pay in seconds. Most schools end up using more than one, precisely because parent households don't all standardize on the same wallet.
Whichever provider you apply through, the underlying KYC (Know Your Customer) requirement doesn't change: your school must be a legally registered institution with a valid PAN, and the account has to be opened in the school's name, not an individual staff member's. Skipping this step, or using someone's personal account "temporarily," creates a compliance and audit problem that's much harder to unwind later than it is to avoid now.
Khalti vs eSewa vs Fonepay: A Practical Comparison for Schools
Each of the three has a genuinely different shape once you look past the logo. Here's how they compare on the things that actually matter for a school's fee collection.
| | Khalti | eSewa | Fonepay | |---|---|---|---| | What it is | Digital wallet + payment service provider | Digital wallet + payment service provider | Interoperable QR network (connects banks & wallets) | | Parent reach | Strong in Kathmandu Valley and urban centers; over 1,000 schools/colleges already listed | Nepal's oldest and most widely distributed wallet; broad reach beyond urban areas too | Reaches parents who use any participating bank app, not just wallet users | | Onboarding path | Apply directly with Khalti's education team; school gets listed in-app | Apply as a merchant via app, web portal, or in person | Apply via your bank, or Fonepay's own merchant enrollment form | | Settlement to school | Withdraw to bank anytime via merchant dashboard, no withdrawal fee | Settles to the linked bank account; exact cycle confirmed at onboarding | Real-time - funds move to the merchant's bank account as the payment completes | | Reconciliation for fees | Dashboard shows per-transaction logs; usable without custom integration | Dashboard and reporting; deeper reconciliation typically needs API/system integration | Ties to whichever bank or software reads the QR settlement feed | | Typical fee for schools | Free to sign up; no charge in year one, small per-transaction fee after - confirm current rate with Khalti | Not publicly published for merchants; confirm current rate when you apply | No fee currently advertised for accepting QR payments | | Best fit for a school when... | Most of your parent base is urban and already comfortable with Khalti | You want the widest possible reach across parent demographics | You want a single QR that catches parents who don't use eSewa or Khalti at all |
The honest takeaway: this isn't really an "either/or" decision. Most Nepal schools that go digital end up offering eSewa, Khalti, and a Fonepay-compatible QR side by side, because parent households don't all use the same wallet, and refusing one option just pushes those parents back to cash.
The Documents You'll Need Before You Apply
Both eSewa and Khalti ask for a similar bundle of documents to open a school's business account, because they're both satisfying the same underlying NRB KYC requirement. Based on what each provider publishes for institutional/business onboarding, expect to prepare:
- School registration certificate - proof the institution is legally registered and recognized (with the Ministry of Education, a local government body, or the relevant registering authority for your school type).
- PAN or VAT certificate - the school's tax registration, not an individual's.
- Latest tax clearance certificate - confirms the institution's tax filings are current.
- School's bank account details - the account fee collections will actually settle into.
- Authorization letter or board resolution - naming who is allowed to sign and operate the account on the school's behalf (principal, chairperson, or authorized accountant).
- Citizenship document of the authorized signatory - the individual signing the agreement, verified against the school's authorization letter.
- School logo and basic profile information - for how the school appears inside the Khalti or eSewa app once listed.
eSewa's own guide for merchants lists a comparable set for general business applicants - business registration certificate, PAN/VAT certificate, the signatory's citizenship document, recent tax clearance, and a bank account with a partner bank. Khalti's school fee payment page asks specifically for the school registration certificate, PAN/VAT certificate, latest tax clearance, and the school's logo for verification.
None of this is unusual paperwork for a registered school - it's the same documentation you'd already have ready for a bank account or an audit. The friction isn't the documents themselves, it's that nobody assigns collecting them to a specific person until the application is already half-started.
How to Actually Get Started: Setting Up Khalti and eSewa for Your Fee Collection
Here's the practical sequence, in the order that avoids the most rework.
-
Assign one owner for the application. Usually the accountant or office manager, with the principal or chairperson as the authorized signatory. One person chasing documents beats three people assuming someone else has it.
-
Gather the KYC documents above in one folder - digital scans and physical originals both, since some steps still want a wet signature or an in-person visit.
-
Decide which providers you actually need. If your parent base is concentrated and digitally comfortable, eSewa and Khalti alone may cover 90% of cases. If you have parents scattered across districts or relying on bank apps rather than wallets, add Fonepay QR to catch the rest.
-
Apply to eSewa as a merchant. Fill out eSewa's merchant application, by app, web form, phone, or in person at their Pulchowk office. A representative reviews your documents and discusses integration options - a simple listing, an API-based Epay integration if you have a student portal or website, or a form-based setup if you don't.
-
Apply to Khalti's education team. Contact Khalti directly through their school fee payment program or by emailing education@khalti.com. You'll sign an agreement, submit the same document bundle, and provide your school's logo so it can be listed inside the Khalti app under education institutions.
-
Set up a Fonepay QR through your bank, if you're adding it. Most Nepali banks that already hold the school's account can register a Fonepay QR against it directly - this is often the fastest of the three, since your bank already has your KYC on file.
-
Test with a small batch before rolling out school-wide. Run one grade's fee cycle through the new payment channels first. Confirm that a payment made by a parent actually shows up against the right student's record, and that the accountant can reconcile it without guesswork.
-
Announce to parents with clear instructions. Once the accounts are live and tested, tell parents exactly which app, which QR, or which link to use - screenshots help more than a paragraph of text.
-
Keep manual/cash collection running in parallel for the first term. Not every parent will switch immediately, and that's fine. The goal in month one is a working channel, not 100% adoption.
Apply to Khalti and eSewa at roughly the same time rather than sequentially. The document bundle is nearly identical for both, so preparing it once and submitting to both providers together saves a second round of digging up the same paperwork a few weeks later.
How Settlement Actually Works
"Settlement" is the part schools worry about most, understandably, since it's the difference between fees collected and fees actually sitting in the school's bank account.
Fonepay is the most straightforward of the three: payments made through a Fonepay-linked QR settle to the merchant's bank account in real time, as the transaction completes, according to Fonepay's own business page. There's no waiting period baked into the product itself, though your bank's own processing may add a short delay on its end.
Khalti works through a merchant dashboard rather than instant bank transfer by default - collected fees sit in the school's Khalti merchant balance, viewable per-transaction, and the school withdraws to its bank account whenever it chooses, at no withdrawal fee. That gives schools flexibility (withdraw daily, weekly, or monthly) at the cost of an extra manual step compared to Fonepay's automatic settlement.
eSewa's settlement cadence for merchants isn't something either provider publishes as a fixed public number for schools specifically, and it can depend on the integration type you choose (Epay/API vs. a simpler listing). The honest answer is: confirm your specific settlement cycle directly with eSewa's merchant team when you apply, and get it in writing as part of the onboarding conversation, so your accountant knows exactly when to expect funds and can build the school's own cash flow planning around it.
Whatever the cycle turns out to be, the important operational habit is the same: your fee management system's internal record of "paid" should update the moment the payment gateway confirms it, even if the bank settlement itself takes a day or two longer. Parents shouldn't be told to wait for bank settlement before their child's fee status updates.
What Transaction Fees Typically Look Like
This is the section where it's tempting to quote a clean percentage, and also the section where doing that would be dishonest.
What's publicly confirmed: Khalti's school fee service is free to sign up, with no cost for the first year and a nominal per-transaction fee that begins after that - Khalti doesn't publish the exact post-year-one percentage on its public school fee page, so that number needs to be confirmed directly when you sign the agreement. Fonepay currently advertises no fee for accepting QR payments. eSewa doesn't publish a standard merchant transaction fee on its public site at all - pricing for merchants appears to be discussed during onboarding rather than posted as a rate card.
That's a genuinely reasonable way for these providers to operate, since fee structures can vary by transaction volume, integration type, and any negotiated terms for institutions like schools and hospitals. But it means the responsible thing for a school to do is treat "what will this cost us per transaction" as a question to ask explicitly during onboarding, in writing, rather than an assumption to carry in from a blog post - including this one. Any specific percentage you've heard quoted secondhand should be verified directly with the provider before you build it into your fee budgeting.
Reconciliation: Making Sure Every Payment Matches a Student
Collecting the payment is only half the job. The other half is knowing, without manually checking, that a payment made through eSewa actually landed against the right student's fee record.
This is where the gap between "we accept Khalti and eSewa" and "our fee system is actually digital" shows up. If your school's billing and fee management isn't connected to your payment gateways, someone still has to manually check the Khalti dashboard, the eSewa merchant portal, and the school's own records, then cross-reference all three by hand every week. That's the exact manual reconciliation work that going digital was supposed to eliminate.
A connected setup - where the fee management system reads directly from the payment gateway rather than someone checking three separate dashboards - is what turns "we accept digital payments" into "we know our fee collection status in real time." That's the difference between a school that added a payment button and a school that actually digitized fee collection.
The unmatched-transaction cases - a parent pays the wrong amount, pays against the wrong child, or pays twice - are rare, but they happen. What matters is that they're flagged automatically for review rather than discovered a month later when a parent disputes their balance.
Parent Adoption: The Part Onboarding Doesn't Cover
Getting the merchant accounts approved is the school's job. Getting parents to actually use them is a separate project, and skipping it is the most common reason a technically correct setup collects less money than expected in month one.
Not every parent has Khalti or eSewa installed, and even fewer have used it to pay something as specific as a school fee before. A few things make the difference:
Explain the "why" before the "how." A short note home - fewer queues at the office, instant digital receipts, no more cash going missing in transit with a child - gets more buy-in than a QR code posted with no context.
Show, don't just tell. A one-page instruction sheet with actual screenshots of the payment flow, in Nepali, beats a paragraph of English instructions that assumes comfort with the app.
Keep the counter open. Don't cut off cash and bank transfer on day one. Let the digital channel prove itself over a term while parents who aren't ready yet keep paying the way they always have.
Make the receipt visible immediately. When a parent pays through eSewa or Khalti and gets an instant digital receipt with their child's name on it, that single moment does more for trust than any announcement could.
Schools that treat parent adoption as part of the rollout, not an afterthought, typically see digital payment usage climb steadily over one or two terms rather than stalling at "the tech-savvy 20% of parents use it and everyone else still pays cash."
Common Mistakes Schools Make Setting This Up
Using a staff member's personal wallet "for now." It always outlasts "for now," and it's the single hardest thing to unwind later, because every historical payment is tied to a person, not the institution.
Applying to only one provider. A school that only sets up eSewa will lose some parents who only have Khalti, and vice versa. Given how similar the document bundle is, applying to both at once costs little extra effort.
Not asking about the fee structure in writing. Verbal assurances during a sales conversation aren't the same as a documented rate. Get the fee schedule - even if it's "confirm at signing" - in writing before your first billing cycle goes live.
Skipping the test batch. Rolling out to all 500 families before confirming that one payment correctly matches one student's record is how a school ends up with a pile of "unidentified payment" entries in week one.
Assuming settlement is instant everywhere. It's close to instant with Fonepay, but Khalti requires a withdrawal step and eSewa's cadence should be confirmed directly. Build your cash flow assumptions around what's confirmed, not what's assumed.
The Bottom Line
Setting up Khalti and eSewa for a school isn't technically hard - it's a documentation and coordination task more than an engineering one. The KYC bundle is standard paperwork most registered schools already have on hand. The real work is assigning ownership of the application, applying to more than one provider so you're not excluding parents who prefer a different wallet, and confirming settlement timing and fees in writing rather than by assumption.
Where it gets genuinely valuable is on the other side of onboarding - when payments made through Khalti, eSewa, or a Fonepay QR flow directly into the school's own fee records instead of sitting in three separate dashboards someone has to check by hand. That's the point where "we added online payment" becomes "our fee collection actually runs itself." If you're comparing what a full school management platform costs against building this reconciliation layer yourself, the merchant account setup described here is usually the smaller half of the project.
Gurukul's billing module connects directly to Khalti, eSewa, and Fonepay, so payments reconcile automatically against student records instead of sitting in separate dashboards. Book a free demo →
