QR payments have changed how Nepal pays. From tea shops to hotels, customers scan a Fonepay QR from their mobile banking or wallet app and show the cashier a "payment successful" screen. It is fast and convenient — but for the business it hides a real problem.
The problem with static QR codes and screenshots
Most businesses still use a static QR: one printed code at the counter. The customer types the amount themselves, pays, and shows a screenshot or the success screen. The cashier then has to decide, by looking at a phone, whether the money really arrived. This causes daily headaches:
- Fake or reused screenshots. An old screenshot, or one edited to show a different amount, looks the same at a glance during a busy rush.
- Wrong amounts. The customer types Rs 1,500 instead of Rs 15,000, and nobody notices until the evening.
- No link to the bill. At the end of the day someone has to match a list of incoming payments against bills and bookings by hand.
- Messy accounts. Digital payments get mixed with cash, so the books never quite reconcile.
Dynamic QR with automatic verification
A dynamic QR is generated for one specific bill and one exact amount. The customer just scans — they don't type anything. Then the software asks Fonepay directly whether that QR was paid, matching both the reference and the amount, before it records the payment. Nobody has to look at a screenshot at all.
In practice this means:
- The amount is always correct, because the customer never types it.
- The payment is attached to the exact bill, booking or invoice it was for.
- It is recorded as a digital payment in the accounts automatically.
- The money goes to your own merchant account — the software only verifies it.
Paying before arrival: payment links
The same idea works remotely. A hotel can send a guest a link in their booking confirmation; the guest opens it, sees their own QR for the advance or the full amount, and pays. The payment lands already attached to their booking. An IT company can do the same for invoices: every invoice gets a permanent "pay online" link that creates a fresh QR whenever the customer opens it.
Where we have built it in
- SajhiloStay HMS — front desk, restaurant till and guest pay-links all use auto-verified Fonepay QR on the hotel's own merchant account.
- OMIT Pay — our central payment service. Business systems call it through a secure API instead of keeping Fonepay credentials inside their own code. Every request is logged, and each system's credentials are stored encrypted.
- Custom websites and apps — we can add verified QR checkout to an existing website or business system. See also our guide to eSewa and Khalti integration.
Is it secure?
Done properly, yes. Credentials should never sit in a browser or a public file; the business server talks to the payment service with a secret key, and the payment service signs every notification it sends back so it can't be forged. The result is safer than a static QR, not riskier.
Frequently asked questions
Do customers need a special app?
No. Fonepay QR can be scanned from the mobile banking and wallet apps customers already use.
Do we need our own Fonepay merchant account?
Yes — the money goes straight to your account with your bank. We handle the technical setup and testing.
What if the internet drops at the moment of payment?
The payment can be re-checked with Fonepay afterwards, so a paid QR is never lost just because the screen didn't update.
Still checking screenshots? Talk to OM IT Solutions about adding verified Fonepay QR to your hotel, restaurant, shop or website.