About this tool
Decode pasted UPI payment and collect-request payloads locally to inspect the payee, amount, reference fields, and debit warnings without opening a payment app.
The UPI Collect Request Decoder parses a pasted upi:// URI in your browser and shows you exactly what it would do — whether it is a collect request that debits you, a pay intent that credits someone else, or a mandate that authorises recurring debits — along with every parameter it carries. It reads the 17 standard UPI fields (pa, pn, am, mam, cu, tn, tr, tid, mc, mid, msid, mtid, mode, orgid, purpose, url, sign), flags anything unrecognised, and prints a plain-language warning for each risk it finds. It is for anyone who has been sent a payment link or QR text and wants to read it before opening a payment app.
Open UPI Collect Request Decoder on AltFTool — it loads instantly in your browser.
Paste the upi:// URI or QR text into the "UPI URI or QR text" box, or press Example to load a sample payload.
Read the Decoded request panel: the action label, Payee, Payee UPI ID and Stated amount, plus warnings for duplicate or invisible-Unicode parameters.
Press Copy report for the full field list, or Clear to wipe the payload — decoding happens in this tab with no network lookup.
collect and request are labelled as debits, pay as an outgoing payment, and mandate as a recurring authorisation, each with the specific consequence spelled out.
It flags duplicate parameters that different apps may resolve differently, and invisible or bidirectional Unicode controls (U+200B–U+200F, U+202A–U+202E, U+2066–U+2069, U+FEFF) that can make a payee ID render backwards.
The payee ID is checked against the name@provider pattern, the amount must be a positive number with at most two decimal places, currency other than INR is called out, and a mam greater than am is reported as an inconsistent payload.
It takes money from your account. A collect request asks you to pay the person who sent it, so approving it with your UPI PIN debits you — receiving money never requires you to enter a UPI PIN.
pa is the payee UPI ID, pn the payee name, am the amount, tr the transaction reference and tn the transaction note. The decoder labels all 17 recognised parameters and lists anything outside that set as an unrecognised field rather than guessing at its meaning.
No — it explains the payload's format and highlights risky patterns, but it cannot verify who owns a UPI ID. Treat it as informational: even when a payload decodes cleanly, confirm the payee and amount inside your own bank or UPI app before approving anything, and report suspected fraud to your bank.
The decoder only displays the sign field; it performs no cryptographic check of the signer. It parses the URI locally in your browser and makes no network calls, so it has no issuer keys to validate a signature against.
Add the UPI Collect Request Decoder widget to your blog or website — free, responsive, no signup. Just keep the “Widget by AltFTool” credit link visible.
<iframe src="https://www.altftool.com/embed/widget/upi-collect-request-decoder"
title="UPI Collect Request Decoder — free AltFTool widget"
width="100%" height="640" style="border:0;border-radius:12px;overflow:hidden"
loading="lazy" referrerpolicy="no-referrer-when-downgrade" allow="clipboard-write"></iframe>
<p style="font-size:12px;margin:4px 0 0">Widget by <a href="https://www.altftool.com/tools/all/upi-collect-request-decoder?utm_source=embed&utm_medium=widget" rel="nofollow">AltFTool — free online tools</a></p>