Collect · QR payments
A QR code for every order, confirmed by webhook.
Create a checkout for the amount owed, show the QR, and let the customer scan and pay with Khalti, eSewa or a card. TolaPay verifies with the rail and tells your system with invoice.paid.
Share anywhere
app.tola.com.np/l/tcl_9q…m4ab
- Opens
- 1,128
- Payments
- 87
- Coupon
- LAUNCH20
In short
How do QR payments work in TolaPay?
Every TolaPay checkout has a public URL, and the hosted page renders that URL as a QR code. To take a QR payment for a specific order, create a checkout with POST /api/v1/checkouts for that product, plan, invoice or wallet top-up, then show the QR on screen or at the counter. The customer scans it with their phone's camera, lands on the same checkout, and pays with Khalti (wallet, mobile banking, e-banking or connectIPS), eSewa or a card. TolaPay verifies the payment with the rail, marks the invoice paid and sends one signed invoice.paid webhook. It is not a Fonepay or NepalPay merchant QR: the code opens a TolaPay checkout, and the payment itself goes through your own Khalti, eSewa or Stripe merchant account.
How it works
QR payments in 4 steps.
- 01
Create the checkout
POST /api/v1/checkouts with the product or amount, the customer and an optional allowed_providers list.
- 02
Show the QR
Open the returned url: the hosted page renders its QR. Or render the url as a QR yourself with any library.
- 03
The customer scans and pays
Their phone opens the checkout; they pick Khalti, eSewa or a card and approve in that app.
- 04
Confirm from the webhook
TolaPay verifies with the rail, marks the invoice paid and delivers invoice.paid. Fulfil from that, not from the screen.
In practice
The same checkout on both screens
The QR encodes the checkout's own URL, so the phone shows exactly what the desktop or counter shows: the order, the total and every connected rail.
Open Khalti on
…and every other bank Khalti routes to.
Paying with Khalti · Mobile banking at Nabil
In practice
Proof comes from the rail, not the scan
A scan is not a payment. TolaPay confirms with Khalti's lookup or eSewa's signed response before the invoice is marked paid and your webhook fires.
POST https://api.chautari.example/tola
- Tola-Event
- invoice.paid
- Tola-Signature
- t=1792311420,v1=5f0c9e…b81a
- User-Agent
- Tola-Webhooks/1.0
{
"id": "we_…",
"type": "invoice.paid",
"created_at": "2026-10-18T08:17:00Z",
"data": {
"number": "INV-2083-0142",
"customer_id": "cus_7k2mq9vd4r8xw3ba6tyn",
"total_cents": 703764,
"currency": "NPR",
"status": "paid"
}
}HMAC-SHA256 over the timestamp and raw body. Retried on failure.
Capabilities
What's included.
- 01
One QR per order
Create a checkout for the exact amount and item; its QR is tied to that order and nothing else.
- 02
Reusable QR
A checkout link's QR mints a fresh checkout on every scan, for posters, menus and counters.
- 03
Desktop to phone
A buyer on a laptop scans the QR to finish on the phone where their wallet app lives.
- 04
Khalti, eSewa, cards
The scanned page offers every rail you have connected, or only the ones you allow.
- 05
Verified, then webhook
Khalti lookup or eSewa's signed response first, then one invoice.paid webhook to your system.
- 06
Status while you wait
Poll GET /api/v1/checkouts/{id}/status to update your own screen when the payment lands.
Who uses it
Where it fits.
Counters and events
Create a checkout for the bill and show its QR on a tablet. The customer's phone opens TolaPay's checkout and pays with Khalti or eSewa; the order completes when the webhook arrives.
Use case 01Desktop checkouts
A buyer on a laptop scans to pay with the wallet app on their phone instead of switching devices by hand.
Use case 02Print and menus
A checkout link's QR on a poster or table card sells the same product to every customer who scans it.
Use case 03
Integration
Create a checkout for one order
Use product_id with the product's one-time price, or amount_cents for a custom amount. The response's url is what the QR encodes; public_id is what success_url's {CHECKOUT_ID} becomes.
curl https://api.tola.com.np/api/v1/checkouts \
-H "Authorization: Bearer $TOLA_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"product_id": "prod_m3n8p2qv7r4xw9ka1tyb",
"amount_cents": 250000,
"customer": { "name": "Walk-in customer", "email": "counter@phewa.example" },
"allowed_providers": ["khalti", "esewa"],
"success_url": "https://pos.phewa.example/paid?checkout={CHECKOUT_ID}",
"metadata": { "order_ref": "T12-0427" }
}'Questions
Questions about qr payments.
Is this a Fonepay or NepalPay QR?
No. The QR opens a TolaPay checkout page. The customer then pays with Khalti, eSewa or a card through your own merchant accounts. Fonepay and NepalPay merchant QR are not payment rails in TolaPay's API today.
Is there an API that returns a QR image?
Not as a separate endpoint. The checkout response includes url, which is what the hosted page's QR encodes. Render that URL as a QR with any library if you want it on your own screen or receipt.
Which rails are live?
Khalti, eSewa and cards through Stripe are the rails in the API. Test mode, with sandbox versions of all three, is open to every workspace. Live payments are enabled for businesses in the closed pilot; join the waiting list for a pilot code.
How do I know the customer has paid?
From the invoice.paid webhook, signed with Tola-Signature. While the customer is paying, GET /api/v1/checkouts/{id}/status tells your screen whether the checkout is pending, processing or completed.
Can the same QR take payments from many customers?
Yes, if it is a checkout link's QR. Each scan creates a fresh checkout, so every customer gets their own invoice. A single checkout's QR is for one order only.
Can I try it before going live?
Yes. Every workspace has a test mode with separate tola_test_ keys and sandbox Khalti, eSewa and Stripe.
Your product deserves better billing infrastructure.
Create a free workspace, try the whole flow in test mode with sandbox Khalti, eSewa and Stripe, and go live when you're ready.
Free while TolaPay is in public beta. You pay only your payment providers' own fees.