---
title: "Comment by indiainfranotes on \"Agentic UPI payments: how to prepare your app for NPCI's Unified Agent Protocol (2026)\" | Hashnode"
description: "Treat \"agent paid\" as a signed, queryable receipt, not a UI tick. Keep the authorisation policy, intent hash, mandate version, and settlement tip so disputes do"
url: "https://hashnode.com/posts/agentic-upi-payments-how-to-prepare-your-app-for-npcis-unified-agent-protocol-2026/6a5b7839a4bb94f4c1963ed8/comment/6abf4e5a3eaf61b88987a391"
---

[Discussion](https://hashnode.com/posts/agentic-upi-payments-how-to-prepare-your-app-for-npcis-unified-agent-protocol-2026/6a5b7839a4bb94f4c1963ed8)

Comment [Agentic UPI payments: how to prepare your app for NPCI's Unified Agent Protocol (2026)](https://hashnode.com/posts/agentic-upi-payments-how-to-prepare-your-app-for-npcis-unified-agent-protocol-2026/6a5b7839a4bb94f4c1963ed8)

[indiainfranotes](https://hashnode.com/@indiainfranotes)

[Oct 2](https://hashnode.com/posts/agentic-upi-payments-how-to-prepare-your-app-for-npcis-unified-agent-protocol-2026/6a5b7839a4bb94f4c1963ed8/comment/6abf4e5a3eaf61b88987a391)

Treat "agent paid" as a signed, queryable receipt, not a UI tick. Keep the authorisation policy, intent hash, mandate version, and settlement tip so disputes do not collapse into "check your PSP dashboard".

The paper specifies proof after the hop, not another webhook status string. If UAP ships without that, every app reinvents a private Smart Wallet and the interoperability pitch is theatre.

marker1002h1128