Agentic payments in India. UPI, consent and AI agents.

The short answer

India is one of the first markets where agentic payments are being built into the national rail itself. NPCI has described UPI Reserve Pay as letting users give consent once and allow intelligent systems to transact on their behalf in a controlled, transparent way. For businesses, agents can also prepare payouts, supplier payments and bill payments over IMPS, NEFT, RTGS and Bharat Connect, with the same controls any agent payment needs.

Two things make India different: UPI’s scale and speed, and payment states such as pending or deemed that must be resolved by lookup, never by paying again.

UPI and agent consent

According to NPCI’s statement published by Razorpay, UPI Reserve Pay supports consent-based, pre-authorised payments that let AI agents transact within approved spending limits. The same page also points to UPI Circle, NPCI’s feature for delegated and shared payment authorisations. These are consumer and merchant capabilities offered through banks and payment apps; check the current NPCI and provider documentation for availability.

The pattern is the one agentic payments converge on everywhere: the person gives consent once, with limits, and each payment the agent makes is checked against that consent. A business building on UPI should keep its own record of that consent and of every payment made under it, so each one can be matched later.

Agent payments for businesses in India

Most of a business’s money moves outside consumer UPI. Agents can prepare:

• Payouts to sellers, riders, agents and customers over IMPS, UPI or NEFT, addressed by account and IFSC or UPI ID.
• Supplier payments from approved invoices, with high-value items over RTGS.
• Loan disbursements and insurance claims, within limits per product.
• Bill payments through Bharat Connect (BBPS), where payment, biller fulfilment and settlement are separate events.

For each, the mandate should state the purposes, payees, rails and caps, and a person should approve anything outside them or any change to a payee’s bank details.

Pending, deemed and timed out

UPI and IMPS payments can sit in a pending or deemed state before their final outcome, and a failed debit may be reversed later. For an agent this is the most dangerous moment: a model that sees "failed" or "timeout" and tries again can pay the same person twice.

The rule is the same as for any unknown outcome. Record the attempt as unknown, query its status against the UTR or RRN with the same key, and wait for the settlement evidence. Never send again to find out. Our guide to duplicate payouts and unknown status sets out the protocol.

Reconciling agent payments on Indian rails

Each Indian rail returns its own reference, and that reference is the thread that connects the agent’s intent, the provider’s response and the bank credit. Capture the UTR or RRN at every stage, match the settlement report and the bank statement on it, and tie every reversal back to the original payment. For Bharat Connect, a successful payment with no biller confirmation is an exception, not a success.

Flominzo Recon reconciles each payment against provider, settlement and bank evidence. That is 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.

Controls to require before agents pay

• A recorded mandate per agent, separate from any consumer consent, stating purposes, payees, rails and caps.
• Payee verification through a name lookup before the first payment to an account or UPI ID.
• Approval tiers for RTGS-sized payments and for any payee whose details changed.
• A status lookup before any retry, keyed to the intent.
• RBI rules still apply, including those on e-mandates and additional authentication; check the current circulars with your bank or provider. Nothing here is legal advice.

Where Flominzo fits in India

Flominzo is operated from Gurugram. Flominzo AgentPay records each agent’s mandate and turns requests into structured payment intents the deterministic core checks before execution; payments run through the licensed providers and banks you use, over the rails agreed for your deployment. Flominzo does not hold customer funds. See Flominzo in India for the rails and statement formats we reconcile.

Where agent payments fit first in India

• Lending disbursals: an agent prepares disbursals for sanctioned loans, checks the borrower’s account by name lookup and submits them over IMPS or NEFT within per-product caps.
• Insurance claims: approved claims paid within limits set per policy type, with larger ones held for a person.
• Gig and marketplace payouts: daily payouts to riders and sellers, assembled from settled orders.
• Supplier payments: approved invoices paid on due dates, with RTGS for high-value items.
• Bill payments through Bharat Connect: recurring bills to known billers, where the agent must wait for biller confirmation before treating a bill as paid.

A worked example: a lender’s disbursal agent

Say a lender lets an agent disburse sanctioned personal loans. The mandate allows disbursals only for loans marked sanctioned in the loan system, only to the borrower’s verified account, up to ₹5 lakh each and ₹2 crore a day, over IMPS or NEFT.

The agent reads 312 sanctioned loans and proposes 309; three borrowers changed their bank account after sanction, so those go to a person. Of the 309 IMPS transfers, 301 succeed at once, five stay pending and three time out. The agent does not resend any of them. It queries each by its key and UTR; six are established as credited and two as failed, and the two are re-proposed as new intents after a person confirms the account.

The next morning the bank statement is matched on UTR. Every disbursal has one debit, one credit reference and one loan. Nothing was paid twice, and each exception has an owner.

Which rail for which agent payment

Questions

Related

Sources

• Razorpay: Agentic payments on UPI, including NPCI’s statement on UPI Reserve Pay
• NPCI: National Payments Corporation of India
• Google Cloud: Announcing the Agent Payments Protocol (AP2)