The problem: collections and payouts that live in separate worlds
Many consumer platforms in India take deposits through one provider and send withdrawals through a different provider, a bank portal or an internal script. Each side has its own dashboard, its own status codes and its own settlement report. The result is familiar to most payment teams. User balances drift out of line with what actually moved, support tickets need checks in two places, and month-end reconciliation becomes a manual exercise.
Brand is a second issue. When the checkout or payment page shows a third-party name, users hesitate, abandon or contact support to ask whether the request is genuine. For payment resellers the pain is structural. Every new merchant means another set of credentials, another integration and another way of reporting, with no clean separation between clients.
How a single collection and payout API for India addresses it
Centabal Pay sets up and operates a payment channel for you. Deposits arrive through UPI and withdrawals leave through IMPS or NEFT, and both run through one API, one transaction ledger and one set of callbacks. Your platform sees a single model for money in and money out, so a user's deposit and later withdrawal can be traced in one place.
The division of work is deliberate. You bring the merchant and bank accounts and keep the relationship with them. We build, host and run the technology that sits on top: the API, the branded payment page on your domain, the reseller panel and round-the-clock operations. Funds settle into the accounts you hold, not into an account controlled by us.
Because the channel is white-label, users see your brand and your domain from the moment they start a deposit to the moment a withdrawal confirmation reaches them.
Scope: what the UPI payin and IMPS payout channel includes
The scope covers the full lifecycle of a transaction, not just the request to a bank. That matters because most operational effort goes into pending states, failed transfers and mismatched records rather than into successful payments. The components below are part of the setup. How each is configured depends on the accounts you bring and the way your platform manages user balances.
- Deposit API for UPI pay-in, with order creation, status query and asynchronous callbacks to your server
- Branded payment page hosted under your own domain, showing UPI options to the user
- Withdrawal API for IMPS and NEFT payouts to Indian bank accounts, with request, status query and callbacks
- Unique order references and duplicate-request protection, so a retried call does not create a second payment
- Transaction records that link each pay-in and payout to your own user or order IDs
- Multi-tenant reseller panel, so each merchant you serve has separated transactions, settings and reporting
- Reports and exports for reconciliation against your bank and merchant account statements
- 24/7 operations monitoring of the channel, with support handled on Telegram
Deposit and withdrawal API India: how integration proceeds
Integration is a joint project. Its length depends mostly on how quickly your accounts are ready, how your backend handles asynchronous callbacks and how much testing your team wants before real users go live. We do not quote a fixed timeline until we have seen your accounts and your current flow. The usual sequence looks like this.
- Scoping call on Telegram: your user flows, expected volume profile, countries and the accounts you hold or are arranging
- Channel configuration: we connect the merchant and payout accounts you provide and set up your domain for the payment page
- Branding: logo, colours and text on the payment page and in user-facing messages
- Sandbox integration: your developers connect to the deposit and withdrawal APIs and handle callbacks and status queries
- Test transactions: small real pay-ins and payouts to confirm settlement, callbacks and reconciliation match your records
- Go-live: traffic moves over, often in stages, with operations watching the first days closely
- Steady state: ongoing monitoring, account changes and support through the reseller panel and Telegram
What you need to prepare before starting
The model only works if the account and compliance side is in place on your end. We run the technology; we do not hold your licences or your merchant relationships, and we do not advise on ways around regulation. Licensing, KYC of your users, tax treatment and any approvals required by the Reserve Bank of India, NPCI rules or your banks remain your responsibility, as they do in every other country you operate in.
On the technical side, your team needs a backend that can receive callbacks, store order references and keep a user's balance consistent while a payment is still pending. That last point is where most integrations need care, because a UPI deposit or an IMPS transfer can stay pending before it resolves.
- Merchant account or accounts able to accept UPI collections
- Bank or payout account able to send IMPS and NEFT transfers, funded as your payout volume requires
- Confirmation that your business model and user base are permitted under your licences and account terms
- A domain or subdomain for the branded payment page, and access to adjust its DNS settings
- A developer contact who owns the integration and a payments contact for daily operations
- Your internal rules for withdrawals, such as review steps, limits per user and handling of failed payouts
Risks and trade-offs to plan for
Any payin payout gateway in India depends on banks, UPI apps and the payment schemes underneath it. Bank downtime, scheme-level outages and transfers that stay pending are outside the control of any technology provider. What a well-run channel can do is detect them early, keep statuses accurate and give your support team clear information while issues are resolved.
There are trade-offs in the model itself. Bringing your own accounts gives you control over settlement and relationships, but it also means account limits, fees and risk reviews are set by your bank or account provider, not by us. Transaction limits for UPI, IMPS and NEFT also depend on the scheme and on the bank, so your payout rules should allow for them. Finally, a white-label channel puts your brand in front of users, which means users will contact you, not a third party, when something goes wrong.
After launch: 24/7 operations and changes over time
Once the channel is live, Centabal Pay operates it around the clock. Operations covers monitoring of pay-in and payout success, follow-up on pending and failed transactions, callback delivery issues and changes to connected accounts. Support runs Telegram-first, so your payments team can raise an issue in the same place it already coordinates with us during setup.
Over time you will add merchants, switch or add accounts, or change withdrawal rules. For resellers, new merchants are added as separate tenants in the panel rather than as new integrations. For platforms expanding into Pakistan, Bangladesh, Vietnam, the Philippines or Myanmar, the same channel approach can be extended, using local collection and payout methods available through the accounts you arrange in each country. Local regulatory approvals there also remain with you.