Explainer · India agentic payments · updated 13 September 2026
India's Unified Agentic Protocol: AI-agent registry, UPI authority and the reported RBI-clearance pause
NPCI has publicly confirmed that it is examining how to identify and authorise digital AI agents in the UPI ecosystem, while Reuters reports that NPCI is building an AI-agent registry as part of a planned Unified Agentic Protocol. The newest status signal matters: reporting on 11 September says the planned UAP launch was paused for regulatory clearance and further work on user protection, liability and governance. That is different from the separate AiNxt and AtOM platforms NPCI did launch at Global Fintech Fest.
Originally published 12 September 2026 · status rechecked 13 September 2026
Reported paused
11 Sep reporting says the planned UAP launch is awaiting regulatory clearance
Registry in development
Reuters reports NPCI is building identity and monitoring for payment-capable AI agents
No public UAP spec
Do not implement against inferred message formats, fields or limits
What changed at GFF 2026?
NPCI launched agentic-AI infrastructure, but not a public UAP implementation contract
On 10 September, NPCI chairman Ajay Kumar Choudhary said the organisation was examining protocols required to identify and authorise digital AI agents while preserving interoperability, auditability and settlement finality. Reuters separately reported that NPCI is building an AI-agent registry to verify and monitor agents making payments on behalf of users.
NPCI also launched AiNxt and Agentic Orchestration & Messaging (AtOM). AtOM is aimed at payment-ecosystem workflows such as system integration, partner onboarding, testing and certification. Business Standard reports that AtOM uses machine-readable, digitally signed interactions and JSON-RPC 2.0. That is useful agent infrastructure, but it is not evidence that consumer UAP payment authorisation is live.
A separate 11 September report says the planned UAP launch was temporarily paused pending regulatory clearance from the Reserve Bank of India, with user protection, liability and governance still being worked through. Until NPCI or RBI publishes an authoritative UAP specification, circular or approval, treat UAP as an emerging governed-payment framework rather than a production protocol contract.
What is actually public?
Separate confirmed UPI primitives from reported UAP mechanics
Reuters reported on 10 September that the planned registry could initially cover agents making UPI payments and later extend to cards, bill payments and other methods. Early use cases are expected to be small, frequent purchases performed under user-defined rules rather than unrestricted autonomous spending.
Public NPCI documentation already shows bounded delegation primitives. An October 2025 UPI Circle addendum extended Full Delegation concepts to IoT devices and software profiles, including AI Profiles for limited users. UPI Reserve Pay lets a user reserve a defined amount that can support multiple later payments.
Those existing controls make the reported architecture plausible, but they do not prove UAP's eventual wire format, registry schema, limits, liability allocation or launch date.
Control stack
Agentic payments need more than a payment credential
Agent identity
Know which software agent is acting, who operates it and whether it is permitted to transact.
User mandate
Bind the agent to a user-approved task, merchant/category scope, amount ceiling and expiry rather than broad account access.
Funding boundary
Use delegated or reserved-payment controls so the amount at risk is explicit before autonomous execution begins.
Transaction evidence
Preserve instruction, merchant, amount, decision path and final payment state so disputes and retries can be reconciled.
Liability
Define who is responsible when an authorised agent makes the wrong purchase, exceeds intent or encounters an ambiguous payment outcome.
Revocation
Let the user or payment provider pause authority without dismantling the rest of the workflow.
UAP vs AtOM vs UPI Circle vs MCP vs x402
They solve different layers of the machine-commerce stack
| Surface | Primary contract | Best-known job | Steward / ecosystem |
|---|---|---|---|
| Unified Agentic Protocol (reported) | UPI agent authorisation + payment governance | Registry, mandates, limits, auditability and liability | NPCI / India payments ecosystem |
| AiNxt / AtOM | Enterprise AI + agent orchestration | NPCI/bank/PSP workflow automation, onboarding, testing and certification | NPCI |
| UPI Circle | Delegated UPI payment authority | Controlled delegation from a primary user | NPCI / UPI |
| UPI Reserve Pay | Reserved balance for multiple debits | Pre-bounds available funds for a continuing payment relationship | NPCI / UPI |
| MCP | Model/runtime ↔ tool contract | Tool discovery and invocation | Agent/tool ecosystem |
| x402 | HTTP resource payment | Machine-readable payment challenge and settlement | Open machine-payment ecosystem |
One future Indian commerce flow could use MCP to reach a merchant tool, UAP to establish who the agent is and what it may spend, and UPI to move funds. AtOM may help NPCI and ecosystem participants automate operational coordination around payment infrastructure. A machine-native API elsewhere might use x402. The architecture question is which layer owns identity, mandate, payment, delivery and retry state.
zFinia interpretation
The regulatory pause is a signal about authority, not a rejection of agentic payments
The unresolved questions are exactly the hard ones for autonomous procurement: who is the agent, what did the user authorise, how much economic authority travels with that instruction, who can revoke it, and who carries liability when software acts incorrectly. The safer design is to approve a constrained economic policy and enforce it outside the model, rather than give an agent a broadly reusable payment credential.
Sources