What FonePay QR is, how merchant onboarding works, what settlement looks like, and why interoperable QR became Nepal's quiet payment default.
FonePay QR is the sticker on every counter in Kathmandu — and increasingly everywhere else. For a Nepali business it is the lowest-friction payment acceptance that exists: no hardware, no per-device cost, and customers who already know the drill. This guide covers what it is, how merchant onboarding works, and where the QR model stops being enough.
What FonePay QR actually is
FonePay is F1Soft’s payment network — the same company behind eSewa — and its QR product rides on the interoperable QR standard adopted across Nepali banking. One QR code at your counter works for customers paying from dozens of bank mobile-banking apps and supported wallets. The customer’s app does the payer-side work; you never see which bank they used unless the settlement report tells you.
For walk-in commerce this interoperability is the product. One sticker replaces a drawer of wallet-specific QR codes, and every year more apps support the same scan.
Merchant onboarding
The path runs through your bank or a FonePay merchant channel:
- Apply with your business registration, PAN/VAT and a bank account in the business name. Many banks can issue a FonePay merchant QR directly alongside your current account — ask at the branch where you bank.
- Sign the merchant agreement. The annex carries your fee and settlement terms. Fees for QR acceptance are typically modest and sometimes zero-promotional for small merchants; get the current terms in writing rather than trusting any article, this one included.
- Receive your QR — a static sticker for the counter, or dynamic-QR access for per-invoice generation.
- Test one payment end-to-end and confirm the settlement lands in your account on the promised schedule before you print a thousand stickers.
Settlement and reconciliation
Payments collect into FonePay and settle to your bank account on a fixed cycle — commonly next business day. The settlement report lists transactions by reference; matching it against your day’s sales is your daily habit. Reconciliation here is simpler than with an API gateway because the volume is usually walk-in, but the discipline is the same: check daily, chase discrepancies within 48 hours while references are fresh.
Where QR is not enough
A counter QR solves physical retail. It does not solve:
- Online checkout — a web store needs a redirect or API flow (wallet or bank rail), not a printable sticker. See eSewa merchant onboarding or connectIPS for that layer.
- Invoicing at scale — manual scan-and-send breaks down past a handful of invoices a day; dynamic QR or a proper gateway fixes it.
- International buyers — QR rails are domestic. Card or international payment routes cover that.
The bottom line
Every Nepali business that takes money at a counter should have an interoperable QR — the cost of being wrong is nearly zero. Pair it with a wallet and bank rail for online sales, and you have covered most Nepali customers. The full picture of rails and their tradeoffs is in our payment gateways field guide.
FAQ
Do my customers need the FonePay app?
No. FonePay QR is interoperable: customers scan and pay from their own bank's mobile-banking app or supported wallets. That is the entire point — one QR at the counter serves customers of many banks.
How fast is settlement?
Funds settle to your bank account on the provider's settlement schedule — typically next business day for standard merchant accounts. Confirm the exact T+N cycle and cutoff times when you sign the merchant agreement.
Can FonePay QR be used for an online store, not just a shop counter?
The counter QR is the common case, but FonePay also supports dynamic QR and online collection flows where the QR is generated per transaction. Ask for the merchant product that matches your sales channel — counter QR alone does not give you an online checkout.