Unified Payment QR Maker
Combine your Fonepay and NEPALPAY codes into one standee that both networks can read.
1. Add the QR codes you already have
Upload a photo of each standee, or paste the code's raw payload if you have it. Both codes must already be issued to you by your bank or wallet provider — this tool combines codes, it cannot create one.
Photo of this QR
Crop tight, shoot straight on, avoid glare.
Or paste the raw payload
Photo of this QR
Crop tight, shoot straight on, avoid glare.
Or paste the raw payload
About this tool
If you keep two QR standees on the counter because different customers pay through different networks, this merges them into one. Upload each code, and it copies every network's account details across byte for byte, keeps one set of merchant details, and recalculates the checksum. Customers paying from eSewa reach your Fonepay account, customers paying from Connect IPS or mobile banking reach your NEPALPAY account, and apps that support both let the customer choose.
How this works. Every payment QR in Nepal — Fonepay, NEPALPAY QR, and the merchant codes issued by eSewa, Khalti and the banks — follows the EMVCo merchant-presented standard. That standard reserves a block of fields for merchant account information and expects a single code to carry more than one, each opening with an identifier that names the network it belongs to. A paying app is meant to read through them, find the identifier it recognises, and route the payment through that entry.
This tool reads your existing codes, copies each network's account block across byte for byte, keeps one set of merchant details, and recalculates the checksum. Your account identifiers are never re-derived or reformatted — if any block changed during the merge, the result is discarded instead of handed to you.
What it cannot do. It cannot create a payment QR from a phone number, an account number or a wallet ID. Those identifiers are issued by an acquirer and there is no way to derive a working one — a code built from guesses would scan as invalid or, far worse, send money somewhere unintended. Every code you merge here has to be one already issued to you.
Test before you print. The merged payload is standards-valid and its checksum is verified here, but whether a specific app reads it is a property of that app. Run a small real payment through each network, and keep your original standees until you have. If your acquirer offers an official interoperable QR, that is the better route — ask them first.
Do this at scale with AI
This app handles the one-off job. These tools handle it as part of a real workflow.