Sunpays
Sunpays
Payment Gateway
Sunpays

Guide

The business owner's guide to UPI payments in India

UPI is how most Indian customers now expect to pay: they approve a request inside an app they already have, and the money lands in a bank account within seconds. This guide explains what that means operationally for a business collecting in INR — how a collection flows end to end, what settlement and costs look like, how payouts work on the same rails, and what actually separates one UPI payment gateway from another.

24/7

Real-time bank rails

Seconds

Customer-side confirmation

< 2s

Sunpays pay-in link generation

8

Channels per merchant

Why UPI became the default for Indian merchants

UPI is operated by NPCI and moves money account to account in real time, with no card network in the middle. For a merchant this changes three practical things: the customer does not type card details, confirmation is immediate instead of an authorisation you capture later, and the payment works the same for a first-time buyer as for a returning one. That combination is why collection volumes over UPI dwarf card volumes for most India-facing consumer platforms.

  • Account-to-account transfer, confirmed in seconds
  • Works from any UPI app — intent link, QR or collect request
  • No stored card credentials for you to protect
  • Same rails available in reverse for payouts

How a collection flows, step by step

The integration itself is a short loop, and every gateway worth using implements the same shape. Understanding it makes provider comparison much easier.

  • Your server creates an order with the gateway, sending your own order id and the amount
  • The gateway returns a payment link, UPI intent or QR, which you show the customer
  • The customer approves the payment in their UPI app; the bank confirms to the gateway
  • The gateway posts a signed callback to your notify URL with the order id and final status
  • Your server verifies the signature, marks the order once (idempotently), and returns HTTP 200
  • A reconciliation job calls the order query endpoint for anything without a callback

Settlement, balance and payouts

The UPI leg is instant, but when you can use the money depends on the provider's settlement cycle — that is the number to ask about, not just the rate. With Sunpays, collections credit your gateway balance immediately; from that same balance you can push UPI and IMPS payouts to customers, run bulk payouts, or settle to USDT on a schedule you choose. Running both directions through one provider means one balance to reconcile instead of stitching two vendors together.

What costs actually look like

Expect a percentage of the collected amount plus a flat per-transaction component, quoted separately for collections and payouts and negotiated per merchant. Two things matter as much as the headline rate: the minimum and maximum ticket size the provider accepts, because orders outside that band simply fail, and the real success rate on your ticket profile, because a cheaper rate on a channel that converts ten points worse is more expensive in practice.

How to compare UPI payment gateways

Once you have seen a few integrations, the API differences shrink and the operational differences dominate. These are the questions that separate providers in production.

  • Can it route across multiple upstream channels, and fail over automatically when one stalls?
  • How fast are pay-in links generated under load?
  • Are callbacks signed, and is finalisation idempotent if the same callback arrives twice?
  • Are there order query and balance query endpoints for reconciliation?
  • What are the per-merchant minimum and maximum limits, per direction?
  • Can you see per-channel success rates and move volume before a bad channel costs you conversions?

Where Sunpays fits

Sunpays is a routing layer over multiple UPI channels rather than a single upstream. Each merchant can be pinned to up to eight channels per direction and currency, orders rotate system-wide across the filled slots, and a stalled channel hands the order to the next slot instantly — the customer still sees one link. Requests are form-encoded with an MD5 signature over sorted parameters and your own order id, so a platform already integrated with a Chinese-style gateway moves over as a configuration change rather than a rebuild.

Frequently asked questions

What is UPI and why do Indian businesses use it?
UPI (Unified Payments Interface) is India's real-time account-to-account payment system, operated by NPCI. A customer approves a payment inside any UPI app and the money moves directly between bank accounts within seconds. Businesses use it because customers already have it installed, there is no card entry step, and confirmation is immediate rather than deferred.
How does a UPI collection actually flow?
Your system creates an order with the gateway and receives a payment link, UPI intent or QR. The customer approves it in their UPI app, the bank confirms to the gateway, and the gateway sends your server a signed callback with the order id and final status. Your server acknowledges with HTTP 200 and marks the order paid. A query endpoint exists for reconciliation when a callback is delayed.
What does a UPI payment gateway cost?
Pricing is normally a percentage of the collected amount plus a flat per-transaction component, quoted per merchant and per direction (collection vs payout). Ask any provider for the pay-in rate, the payout rate, the settlement cycle and the minimum and maximum ticket sizes before you integrate, because ticket limits affect conversion as much as the rate does.
How fast is settlement?
The UPI leg itself is instant, but when the balance reaches you depends on the provider's settlement cycle. Sunpays credits collections to your gateway balance immediately and lets you withdraw as INR through UPI/IMPS payouts, or settle in USDT on a schedule you choose.
Can I send money out over UPI too?
Yes. Payouts push funds from your balance to a customer's UPI id or bank account over UPI/IMPS. Running collections and payouts through one provider means one balance, one set of credentials and one reconciliation job instead of two.
What should I check before choosing a provider?
Look at success rate rather than headline rate, whether the provider can route across multiple upstream channels and fail over when one stalls, how quickly pay-in links are generated, whether callbacks are signed and idempotent, and whether order query and balance query endpoints exist for reconciliation.

Start collecting in a day

One REST API for pay-ins, payouts, balance and signed webhooks. Sandbox keys the same day, live traffic after KYB.