Checkout
Put an intent or a QR on the pay step, and ship only after the webhook.
01UPI Collection API
Get paid the way your customer already pays.
A collect request to a VPA, a QR with the amount locked in, or an intent that opens their UPI app. Every one of them calls you back with a UTR and the reference you chose.
L
Ref
Paid · UTR
collection.success delivered to your server- 3
- ways to collect, one signature
- 1
- webhook shape for every mode
- Your
- reference, returned with the UTR
- 0
- shared handles to reconcile by hand
Next step
Ask for collection access
Tell us where the money comes in and roughly how much. We reply with sandbox notes and pricing.
- Read by a person the same working day.
- Rate card and sandbox notes, in writing.
- Nothing is switched on until you say so.
Who it is for
The work it takes off your desk
Invoices
One collect or one QR per bill, so the payment names itself.
02Fees
A handle per student or per term, instead of one shared VPA.
03Retainers
Fire the collect on billing day and listen for success or expiry.
04Marketplaces
Map every UTR back to an order, a seller or an account.
05Counters
A fresh QR for each desk, so the drawer stays honest.
06Lifecycle
Every state, named and signed
- 01Reference
You create the collection with your own id.
- 02Customer pays
Collect approval, QR scan or intent tap.
- 03UTR
Returned alongside the reference you sent.
- 04Webhook
Signed — for success, failure and expiry.
The difference
One collection stack, not a vendor for each gesture
- A different provider for QR, intent and collect
- A sandbox that shows up after paperwork
- Money in, with no UTR you can file
- Status you discover by asking
- Collect, QR and intent behind one signature
- Sandbox while the commercial conversation is open
- A UTR on every successful collection
- A webhook for success, failure and expiry
The request
What your developers actually send
Request body
Response
/api/v1/collection/send-collect-request Ask a VPA to approve a specific amount.
/api/v1/collection/generate-dynamic-qr A QR tied to an amount and your reference.
/api/v1/collection/generate-payment-link An intent the payer’s app can open.
/api/v1/collection/status Pending, success, failed or expired — plus the UTR.
Three gestures
However they pay, one reply comes back
Collect
Approve in your UPI app. Request from Acme Store.
POST /api/v1/collection/send-collect-request
Dynamic QR
Amount is locked. Scan to pay.
POST /api/v1/collection/generate-dynamic-qr
Intent
Opens on tap. Pay with your UPI app.
POST /api/v1/collection/generate-payment-link
Questions
Before you write in
Which ways can a customer pay?
A collect request to their VPA, a dynamic QR, or an intent from your checkout. Success carries a UTR. Failure and expiry arrive on the webhook.
How do I match a payment to an invoice?
You send the reference. We return it with the UTR, so the match happens in your own system.
Is there a sandbox?
Yes. You can raise a collect, build a QR and receive the webhook before any commercial onboarding.
Can I refund?
A collected payment can be returned through the payout API, against the same reference.
Do I need the white-label portal?
No. Collection works inside your own product. The portal is optional, for a brand of your own.
The sandbox is open. The docs are public.
LiteBanking is a product of QuiqPe Private Limited.