UPI Collect & Pay API Integration
Initiate UPI collect requests, validate VPAs and reconcile payments through our PSP-grade integration.
What UPI Collect & Pay API integration does
UPI is the default way money moves between people and businesses in India, and integrating it well is mostly about handling asynchrony correctly. A collect request is not a payment; it is a request that may be approved, declined, or simply left to expire while your customer stares at a spinner. The systems that get UPI wrong are almost always the ones that treated it as a synchronous call.
Our UPI integration covers VPA validation, collect request initiation and payment reconciliation through PSP-grade access. Validating the payer's VPA before raising the request removes the most common failure — a typo'd address — before it becomes a customer-visible error. Collect requests carry an idempotency key tied to your order reference, callbacks are matched against it, and undelivered callbacks are replayed, so a webhook outage on your side does not turn into a payment your ledger never heard about.
Payouts run over the same integration, so disbursing to a verified VPA uses the same model as collecting from one.
What teams build with it
In-app collection
Raise a collect request against a validated VPA and confirm payment inside your own flow, without redirecting the customer to a gateway page.
Instant disbursal
Push funds to a customer or partner over UPI for refunds, claims, loan disbursal or gig payouts, with confirmation in seconds.
Subscription collection
Run recurring collections with mandate handling and clean retry semantics on failure.
Marketplace settlement
Collect from buyers and settle to sellers over the same rail with reconciliation against your order ledger.
Endpoints included
POST/upi/v3/vpa/validateChecks if a Virtual Payment Address is valid and resolves the account holder name.POST/upi/v3/collectRaises a UPI collect request to the payer's PSP app.
Try it in the sandbox
https://sandbox.aeologic.io/upi/v3/vpa/validate{
"vpa": "ananya@oksbi"
}What you need before we start
- A settlement account and confirmation of your merchant or platform position
- An endpoint that can receive and acknowledge payment callbacks
- An order reference model that supports idempotency keys
- A defined timeout and retry policy for unapproved collect requests
How we deliver it
- Flow design covering collect, timeout, decline and reconciliation paths
- Sandbox integration with simulated approval, decline and expiry callbacks
- Reconciliation wiring against your order ledger, including replay of missed callbacks
- Production cutover with monitoring on success rate and callback latency
Related Payments integrations
Industries using UPI Collect & Pay
UPI Collect & Pay API integration — FAQs
Do we need our own PSP relationship?
No. The integration runs through Aeologic's PSP-grade access, which is what lets you start collecting without arranging direct bank sponsorship first.
How are duplicate or missed callbacks handled?
Each collect request carries an idempotency key tied to your order reference. Duplicates resolve to the same ledger entry; missed callbacks are replayed until acknowledged.
Can we validate a VPA before charging?
Yes, and you should. VPA validation before raising the collect request removes the most common cause of failed UPI collections.
Does this support payouts as well as collections?
Yes. Collect and pay run through the same integration, so disbursal shares the reconciliation model.
Ship UPI Collect & Pay in days
Tell us your stack and we'll wire up UPI Collect & Pay API integration for your team.
Talk to Aeologic