Fonepay QR in Paymentsnp checkout
The customer sees a QR made for their order on Fonepay's page and pays it from their bank's mobile banking app. Paymentsnp checks Fonepay's signed return for the exact amount before the order counts as paid.
- Payments settle to your own Fonepay merchant setup
- No minimum amount set by Paymentsnp
- Customers approve the payment in their bank app

Scan with your mobile banking app
Powered by Paymentsnp
How Fonepay works in Paymentsnp. A QR for every order.
A signed request
When the customer picks Fonepay, the browser is sent to Fonepay's page with a request our server has signed with your secret key using HMAC-SHA512.
A QR for this order
Fonepay shows a QR made for this one order and its exact amount.
Scan with a bank app
The customer opens their bank's mobile banking app, scans the QR and approves the payment there. PINs and OTPs stay in the bank app.
Signed return, exact amount
Fonepay sends the customer back with a signed result. We recompute the signature and require the right attempt, your merchant code, a success status and the exact amount.
What we send and what we check. The fields come from the code.
The request for a Rs 2,500 order and the checks on Fonepay's return. Test mode uses Fonepay's development host.
- Signature
- HMAC-SHA512 with your Fonepay secret key
- Order reference
PRN, the payment attempt id- Amount
- Taken from the order and checked twice on return
- Status lookup
- None. Fonepay offers no lookup API
GET https://clientapi.fonepay.com/api/merchantRequest
PID = <your Fonepay merchant code>
MD = P
PRN = <payment attempt id>
AMT = 2500
CRN = NPR
DT = <today's date in Nepal, MM/DD/YYYY>
R1 = Paymentsnp checkout
R2 = Paymentsnp
RU = <checkout return URL>
DV = <HMAC-SHA512 of the values above, hex>Fonepay returns the customer with:
PRN, PID, PS, RC, UID, BC, INI, P_AMT, R_AMT, DV
Paymentsnp recomputes DV with your secret key, then
requires PRN = this attempt, PID = your merchant code,
PS = success, and P_AMT = R_AMT = the order amount.When the customer does not come back. The one gap in Fonepay's flow.
Paymentsnp does not guess. Without Fonepay's signed return, the attempt stays pending until it expires, and an order is never marked paid on a customer's word or a screenshot.
| What happened | Paymentsnp result |
|---|---|
| Signed return, success, exact amount | Succeeded |
| Signed return, not a success | Failed |
| Signature, merchant or amount wrong | Not paid |
| No return within 30 minutes | Expired |
| You record it from the Fonepay panel | Manually confirmed |
Bank apps that can pay. Fonepay's network, not ours.
These banks are on Fonepay's own member list, so their mobile banking apps can scan the Fonepay QR at our checkout. None of them is a Paymentsnp partner.
Banks on Fonepay's network, as listed by Fonepay. They are not Paymentsnp partners. How providers and banks relate to Paymentsnp
Commercial banks on Fonepay's list
- Agricultural Development Bank
- Citizens Bank
- Everest Bank
- Global IME Bank
- Himalayan Bank
- Kumari Bank
- Laxmi Sunrise Bank
- Machhapuchchhre Bank
- Nabil Bank
- Nepal Bank
- Nepal Investment Mega Bank
- Nepal SBI Bank
- NIC Asia Bank
- NMB Bank
- Prabhu Bank
- Prime Commercial Bank
- Rastriya Banijya Bank
- Sanima Bank
- Siddhartha Bank
- Standard Chartered
Citizens Bank and Sanima Bank are on the list but have no logo in the row above yet. Fonepay's list also includes development banks, finance companies and wallets, which are not listed here.

What you need. From your bank and Fonepay.
Fonepay merchant web payment access comes through your bank. Paymentsnp does not arrange it for you.
| Access | Fonepay merchant web payment access from your bank |
|---|---|
| Credentials | The merchant code and secret key Fonepay issues |
| Environments | Separate test and live configuration |
| Minimum amount | None set by Paymentsnp |
Saving your credentials
When you save a merchant code and secret key, Paymentsnp first checks them with Fonepay for the environment you are in. If Fonepay does not accept them, nothing is saved. Saving does not switch Fonepay on; you enable it yourself, separately for Test and Live.
Settlement and fees follow your agreement with your bank and Fonepay. Use reconciliation to match their settlement file against verified payments.
Fonepay website (opens in a new tab)Questions about Fonepay.
Which banks can my customers pay with?
Any bank whose mobile banking app can scan a Fonepay QR. The commercial banks on Fonepay's own member list are shown on this page; Fonepay's list also includes development banks, finance companies and wallets.
Is my bank a Paymentsnp partner?
No. Paymentsnp has no partnership with any bank or with Fonepay. The banks shown here are on Fonepay's network, and you get Fonepay access through your own bank.
What if my customer paid but the order is not marked paid?
Fonepay has no lookup API, so if the customer did not return to the checkout we cannot confirm it. Check the reference in your Fonepay merchant panel and record the payment as manually confirmed. That record is audited and marked as not provider-verified.
Can I try Fonepay in Test mode?
Yes. Save your Fonepay test configuration in Test mode and Paymentsnp uses Fonepay's development host. The Sandbox gateway also lets you test a full payment without any Fonepay access.
When does Fonepay money reach my account?
Settlement timing and fees are set by your agreement with your bank and Fonepay. Paymentsnp never holds the money.












