UPI and IMPS payouts in India. Pending is not failed.

The short answer

A UPI or IMPS payout API lets a business push money from its account to a recipient’s UPI ID or bank account and IFSC, through a bank or a payment provider, usually in seconds and at any hour. The hard part is not sending; it is the in-between states. A payout can be pending or deemed for a while before its final outcome, and a debit that never reached the beneficiary must be reversed. Resolve those states by status check against the transaction reference, never by sending the payout again.

UPI, IMPS or NEFT for payouts?

What a payout API does

1. Validate the beneficiary. Check the UPI ID or the account and IFSC, and where the provider supports it, verify the account holder’s name before the first payout.
2. Send once, with your reference. Each payout carries a unique reference of yours that the provider treats as idempotent, so a retry of the same request cannot pay twice.
3. Receive a rail reference. Successful and pending payouts return a bank reference, commonly the RRN, which many banks and providers show as the UTR.
4. Report the status. Through a callback and a status-check endpoint: success, failure, or pending.
5. Report the money. A payout report and the statement of the account or balance that funds payouts.

Per-transaction limits and supported methods differ by rail, bank and provider, so confirm them with the provider for each payout type you run.

Verify the beneficiary before the first payout

Most avoidable payout failures in India start with beneficiary details: a mistyped account number, a wrong IFSC, a UPI ID that belongs to someone else, or an account that has since been closed. Verify before the first payout and whenever the details change.

• UPI IDs: validate the ID and read back the name registered to it, where your provider supports it.
• Bank accounts: some providers verify an account by sending a small test credit and reading back the account holder’s name, often called a penny drop.
• Name matching: compare the returned name with the name you hold, and decide in advance what happens when they differ.
• Record it: keep the verification result, the date and the provider’s reference with the beneficiary, so a later dispute has evidence.

References: RRN, UTR and yours

Three references tie a payout together, and each appears in a different record:

• Your reference: generated by you, stored before sending, and echoed in the provider’s callbacks and reports.
• The provider’s payout id: in its API responses and payout report.
• The rail reference (RRN or UTR): on the bank side, and what the recipient’s bank can trace.

Store all three on the payout as they arrive. Bank statement narrations differ from bank to bank, so match statement lines on the rail reference and amount rather than on free text.

Pending, deemed and the RBI turnaround rules

On UPI and IMPS a payout can sit in a pending or deemed state when the final response from the beneficiary’s side has not come back in time. From your side it may look like a failure; money may still have moved. Treat it as unknown: check the status against the reference at intervals your provider documents, and do not send a second payout.

The Reserve Bank of India’s circular on turnaround times (20 September 2019) sets the rule for failed credits: for IMPS and for UPI fund transfers, where an account is debited but the beneficiary account is not credited, the beneficiary bank must auto-reverse by T+1 day, with compensation of ₹100 per day if the delay goes beyond T+1. For payouts, that means a failed credit should come back within a known window, and you should expect and match that reversal.

Failure modes and what to check

Funding payouts, and a daily routine

Payouts are funded either from your own current account at the bank that sends them, or from a balance you keep with the payout provider. Either way, that account or balance is a position to reconcile every day.

1. Load the provider’s payout report and the statement of the funding account or balance.
2. Match each payout on your reference, the provider’s payout id and the RRN or UTR.
3. Check every pending or deemed payout from the previous day: resolved, reversed, or still open with an owner.
4. Match reversals to the payouts they belong to, and check they arrived inside the T+1 window.
5. Reconcile the balance: opening balance plus top-ups, minus payouts and fees, plus reversals, equals the closing balance.
6. Raise every unexplained line or difference as an exception with an owner.

Reconciling Indian payouts

Reconcile each payout three ways: your instruction and reference, the provider’s payout report with the RRN or UTR, and the debit on the account or prefunded balance that funds payouts. Reversals are new evidence for an existing payout, matched on the same references. At the end of each day, the funding balance should equal the opening balance plus top-ups, minus payouts and fees, plus reversals.

That is what Flominzo means by 100% reconciliation: every payment is matched or explained, with evidence: it ends either matched against independent evidence - the provider’s records, the settlement file and the bank statement - or as an open exception with an owner and a reason. None is silently assumed paid.

How Flominzo fits

Flominzo records every payout attempt before it is sent, classifies each provider result, and resolves a pending or unknown payout by status lookup and evidence, never by sending it again. Recon matches payouts on the reference each rail returns and treats reversals as evidence for the original payout. Flominzo is operated from Gurugram; the banks, providers and rails in scope are agreed for your deployment.

Questions

Related reading

Sources

• Reserve Bank of India: Harmonisation of Turn Around Time and customer compensation for failed transactions (20 September 2019)