{"id":566,"date":"2026-11-04T12:00:00","date_gmt":"2026-11-04T12:00:00","guid":{"rendered":"https:\/\/paymentsetu.com\/blog\/?p=566"},"modified":"2026-11-04T12:00:00","modified_gmt":"2026-11-04T12:00:00","slug":"upi-deep-link-parameters-explained","status":"publish","type":"post","link":"https:\/\/paymentsetu.com\/blog\/upi-deep-link-parameters-explained\/","title":{"rendered":"UPI Deep Link Format: pa, pn, am, tn, tr and cu"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">The UPI deep link format lets your website or app open a customer&#8217;s UPI app with the payee, amount and order details pre-filled. It reduces typing, but it does not prove that money was paid, so your server still needs to verify the UTR and amount before marking an order complete.<\/p>\n\n\n\n<aside class=\"ap-card\" aria-label=\"PaymentSetu Pro\">\n<span class=\"ap-card__badge\">Best for growing stores<\/span>\n<div class=\"ap-card__body\"><p class=\"ap-card__name\">PaymentSetu Pro<\/p><p class=\"ap-card__best\">Best for growing WooCommerce \/ WHMCS stores and service businesses with up to 1,000 UPI payments a month (most popular)<\/p><ul class=\"ap-card__features\"><li>1,000 credits (1 credit = 1 successful payment verified)<\/li><li>0% commission, direct-to-bank UPI settlement<\/li><li>Dynamic QR, webhooks and API access<\/li><li>WooCommerce and WHMCS plugins<\/li><li>Priority support<\/li><\/ul><\/div>\n<div class=\"ap-card__side\"><p class=\"ap-card__price\">\u20b9999 <small>Most popular \u00b7 \u20b9999 \/ 30 days \u00b7 1,000 verified payments<\/small><\/p><a class=\"ap-card__btn\" href=\"https:\/\/paymentsetu.com\/auth\/register\">Get Pro \u2192<\/a><\/div>\n<\/aside>\n\n\n\n<h2 class=\"wp-block-heading\">Anatomy of a <code>upi:\/\/pay<\/code> URL<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A UPI deep link is a URI with the <code>upi:\/\/pay<\/code> scheme followed by query parameters:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>upi:\/\/pay?pa=merchant%40bank&amp;pn=Sunrise%20Cafe&amp;am=1499.00&amp;cu=INR&amp;tr=ORD-1042&amp;tn=Order%20ORD-1042<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Read it from left to right:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li><code>upi:\/\/<\/code> is the URI scheme that tells a compatible device or app this is a UPI payment link.<\/li>\n\n\n<li><code>pay<\/code> is the action.<\/li>\n\n\n<li><code>?<\/code> starts the query string.<\/li>\n\n\n<li>Each <code>name=value<\/code> pair is a parameter.<\/li>\n\n\n<li><code>&amp;<\/code> separates parameters from one another.<\/li>\n\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The link is data for the payment screen. A UPI app can use it to display the merchant and amount, but the payer must review the details and authorise the payment with their UPI app. NPCI&#8217;s <a href=\"https:\/\/www.npci.org.in\/what-we-do\/upi\/product-overview\" target=\"_blank\" rel=\"noopener\">UPI product overview<\/a> explains UPI&#8217;s broader payment model; its published <a href=\"https:\/\/www.npci.org.in\/PDF\/npci\/upi\/circular\/2017\/Circular18_BankCompliances_to_enbaleUPIMerchantecosystem_0.pdf\" target=\"_blank\" rel=\"noopener\">UPI merchant ecosystem circular<\/a> is also useful background for developers working with merchant-initiated flows.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For a static counter QR, you can keep the link simple. For an invoice or online order, add a fixed amount and a unique reference so the payment can be matched to one order later.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">UPI deep link parameter reference<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The table below covers the fields most useful in a normal merchant link. NPCI&#8217;s UPI Linking Specification 1.6 distinguishes static and dynamic use, so treat a field&#8217;s required status as dependent on the flow and the UPI app or PSP handling it.<\/p>\n\n\n\n<figure class=\"wp-block-table ap-table\"><table><thead><tr><th>Parameter<\/th><th>Meaning<\/th><th>Example<\/th><th>How to use it<\/th><\/tr><\/thead><tbody><tr><td><code>pa<\/code><\/td><td>Payee virtual payment address (VPA)<\/td><td><code>merchant%40bank<\/code><\/td><td>The UPI ID that receives the money. This is the most important value to protect from accidental changes.<\/td><\/tr><tr><td><code>pn<\/code><\/td><td>Payee name<\/td><td><code>Sunrise%20Cafe<\/code><\/td><td>The name shown to the payer. Use the merchant name customers will recognise.<\/td><\/tr><tr><td><code>am<\/code><\/td><td>Amount<\/td><td><code>1499.00<\/code><\/td><td>Pre-fills a payment amount. Use digits and a decimal point, not a rupee symbol or comma separators.<\/td><\/tr><tr><td><code>cu<\/code><\/td><td>Currency<\/td><td><code>INR<\/code><\/td><td>Use <code>INR<\/code> for Indian rupee payments.<\/td><\/tr><tr><td><code>tn<\/code><\/td><td>Transaction note<\/td><td><code>Order%20ORD-1042<\/code><\/td><td>A short human-readable description. Keep it useful and encode spaces and reserved characters.<\/td><\/tr><tr><td><code>tr<\/code><\/td><td>Transaction reference<\/td><td><code>ORD-1042<\/code><\/td><td>Your order, invoice, booking or subscription reference. Generate it on your server and keep it unique.<\/td><\/tr><tr><td><code>mc<\/code><\/td><td>Merchant category code<\/td><td><code>5812<\/code><\/td><td>The merchant category code, when supplied by the acquiring or merchant setup. Do not invent one. Pass the value provided for your merchant account.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Two fields are easy to confuse:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li><code>tr<\/code> is an identifier for the transaction or order. Your backend can use it to connect the payment attempt to a record.<\/li>\n\n\n<li><code>tn<\/code> is a description for people and payment screens. It is not a secure authentication token and should not be your only matching key.<\/li>\n\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The older NPCI table also describes fields such as <code>tid<\/code>, <code>url<\/code>, <code>mode<\/code>, <code>orgid<\/code> and <code>sign<\/code> for particular merchant or PSP flows. Do not fill those with made-up values. <code>tid<\/code> is not simply another name for your order number, and signed or secure intents need the relevant merchant and PSP setup. For a basic link, use only the fields your flow genuinely needs.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Example links for common payment situations<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">1. Counter or printed QR<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">If the customer should enter the amount after scanning, omit <code>am<\/code>:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>upi:\/\/pay?pa=shop%40bank&amp;pn=Kaveri%20Stationery&amp;cu=INR<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">This is suitable for a static counter QR where the final bill can vary. The UPI app should show the payee and currency, while the customer enters the amount.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For a fixed-price counter item, add the amount and a reference generated for that sale:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>upi:\/\/pay?pa=shop%40bank&amp;pn=Kaveri%20Stationery&amp;am=250.00&amp;cu=INR&amp;tr=SALE-20261023-01&amp;tn=Notebook%20and%20pens<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Do not reuse a dynamic order reference for multiple unrelated payments. If your system cannot associate a QR with a specific order, it will have less context when reconciling payments.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2. Invoice link<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">An invoice can carry a fixed amount and a readable reference:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>upi:\/\/pay?pa=freelancer%40bank&amp;pn=Ananya%20Designs&amp;am=3500.00&amp;cu=INR&amp;tr=INV-2026-0087&amp;tn=Invoice%20INV-2026-0087<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The invoice number is useful to the payer, but your server should still compare the payment amount and UTR with the invoice record. A note displayed by an app is not a substitute for payment confirmation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you need a customer to view full invoice details, use your own HTTPS invoice page separately. Do not place a long invoice body in <code>tn<\/code>; the field is intended as a short note and app displays can vary.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">3. Online order<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">For an online checkout, create the order first, then build the link from server-side values:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>upi:\/\/pay?pa=store%40bank&amp;pn=River%20Goods&amp;am=1299.00&amp;cu=INR&amp;tr=ORD-20261023-1042&amp;tn=Payment%20for%20ORD-20261023-1042<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The order record should contain the expected amount, currency, reference and an initial unpaid state. When the customer returns from the UPI app, show a pending or confirmation screen until your server has checked the payment. Never trust an amount or order ID sent back by the browser alone.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You can also turn a link into a QR code. PaymentSetu&#8217;s <a href=\"https:\/\/paymentsetu.com\/free-upi-qr-code-generator\">free UPI QR code generator<\/a> is useful for a static QR or a simple printable payment flow; an online order still needs a reliable reconciliation step after payment.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Common mistakes when building the URL<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Encoding the whole link instead of each value<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Build the scheme and separators yourself, then encode each parameter value. Do not URL-encode the complete string after adding <code>?<\/code> and <code>&amp;<\/code>, or the UPI app may receive one large, unusable value.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, the human-readable note <code>Payment for Order #1042 &amp; delivery<\/code> should become a value similar to:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Payment%20for%20Order%20%231042%20%26%20delivery<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The <code>&amp;<\/code> inside the note is <code>%26<\/code>; otherwise it will be interpreted as the start of another query parameter. Encode characters such as spaces, <code>#<\/code>, <code>&amp;<\/code>, <code>?<\/code>, <code>%<\/code> and non-ASCII text according to the URI component rules used by your language.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Double-encoding values<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">If a library has already changed a space to <code>%20<\/code>, encoding that result again can turn <code>%20<\/code> into <code>%2520<\/code>. The payment app then sees the literal characters <code>%20<\/code> instead of a space. Decide whether your URI builder expects raw values or already encoded values and apply encoding exactly once.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The <code>@<\/code> in a VPA is another common source of confusion. A value such as <code>shop@bank<\/code> may appear as <code>shop%40bank<\/code> in the final URI. That is normal percent-encoding. Test the exact output on the UPI apps and devices your customers use.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Formatting <code>am<\/code> like a price label<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Keep <code>am<\/code> machine-readable:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>am=1299.00<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Avoid these forms:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>am=\u20b91,299\nam=1,299.00\nam=1299 rupees<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Do not calculate the amount in a browser and then trust it at payment time. Calculate it on the server, store it with the order, and validate the received payment against that stored value. Use a decimal-safe money type or integer paise in your application so floating-point rounding cannot change the payable amount.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Treating <code>tr<\/code> and <code>tn<\/code> as interchangeable<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Use <code>tr<\/code> for a stable reference such as an order or invoice ID. Use <code>tn<\/code> for a short label a person can understand. Avoid putting secrets, API keys, phone numbers or unnecessary personal information into either field because these values can appear in payment screens, logs or receipts.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Making a note too long<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Long notes make links harder to share and can be displayed differently across apps. Keep <code>tn<\/code> short, put the full details on your own invoice page, and use your database record\u2014not the note\u2014as the source of truth.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Why the link alone cannot confirm payment<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Opening a UPI deep link proves only that a payment request was handed to a UPI app. It does not prove that:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li>The customer completed the authorisation.<\/li>\n\n\n<li>The money reached the intended merchant account.<\/li>\n\n\n<li>The final amount matched the order.<\/li>\n\n\n<li>The reference was unique and associated with this customer.<\/li>\n\n\n<li>The customer did not close the app, edit a client-side value or return without paying.<\/li>\n\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">An Android activity result, redirect, browser callback or \u201csuccess\u201d screen can help the interface decide what to display next, but it is not your accounting record. A screenshot is also not proof of settlement.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Your server should accept an order as paid only after checking the payment information available from the merchant account or verification service. At minimum, match:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>the exact expected amount;<\/li>\n\n\n<li>the merchant account that should receive it;<\/li>\n\n\n<li>the UTR or equivalent bank transaction reference;<\/li>\n\n\n<li>the order or invoice state; and<\/li>\n\n\n<li>whether that UTR has already been used for another order.<\/li>\n\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Make the update idempotent: receiving the same confirmation twice should not create two fulfilments, two shipments or two credit entries. Keep the order pending when the result is not yet verifiable and provide a safe way to check again.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Verifying through an API and webhook<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">For a custom checkout, the robust sequence looks like this:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li>Your server creates an order and a unique <code>client_txn_id<\/code> with the expected amount.<\/li>\n\n\n<li>Your server builds the <code>upi:\/\/pay<\/code> link and sends it to the browser or app.<\/li>\n\n\n<li>The customer pays in a UPI app. The money goes to the merchant&#8217;s own UPI merchant account.<\/li>\n\n\n<li>Your verification service checks the incoming payment against the order&#8217;s amount and reference.<\/li>\n\n\n<li>Your webhook endpoint receives the verified event, validates its HMAC signature, checks that the event has not already been processed, and marks the order paid.<\/li>\n\n\n<li>Your server returns the fulfilment result to the customer only after its own database update succeeds.<\/li>\n\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">PaymentSetu is a payment verification service in this flow, not a payment gateway: it does not hold the money. The customer pays the merchant&#8217;s connected Paytm Business or PhonePe Business account, PaymentSetu matches the UTR and amount to the dynamic QR or order, and the service sends a webhook. Its API includes <code>POST \/api\/create_order<\/code>, <code>GET \/api\/order_status\/{client_txn_id}<\/code> and <code>GET \/api\/check_credits<\/code>, with API-key authentication and HMAC-signed webhooks.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This approach separates two jobs that are often mixed together:<\/p>\n\n\n\n<figure class=\"wp-block-table ap-table\"><table><thead><tr><th>Job<\/th><th>What the deep link does<\/th><th>What your backend must do<\/th><\/tr><\/thead><tbody><tr><td>Start payment<\/td><td>Opens a UPI app with payee and order details pre-filled<\/td><td>Create the order and keep the expected values on the server<\/td><\/tr><tr><td>Identify payment<\/td><td>Carries <code>tr<\/code> and a note that may help a person recognise the order<\/td><td>Match the verified UTR, amount and order state<\/td><\/tr><tr><td>Update checkout<\/td><td>Lets the customer return to your site or app<\/td><td>Trust only a verified, signed, idempotently processed server event<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">For a WooCommerce store or WHMCS installation, a ready integration can remove custom callback work. For a bespoke app, keep the same principle: the URL starts the payment, while the server-side verification event authorises fulfilment. If you want to connect a merchant account and test the API flow, <a href=\"https:\/\/paymentsetu.com\/auth\/register\">create a PaymentSetu account<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">A practical implementation checklist<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Before putting a UPI deep link or QR into production, check each item:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Generate <code>pa<\/code>, <code>pn<\/code>, amount and order reference from trusted server-side data.<\/li>\n\n\n<li>Encode every query value once, especially notes containing spaces or <code>&amp;<\/code>.<\/li>\n\n\n<li>Use <code>INR<\/code> and a plain decimal amount such as <code>250.00<\/code>.<\/li>\n\n\n<li>Use a unique <code>tr<\/code> for every invoice or order that needs automatic matching.<\/li>\n\n\n<li>Keep <code>tn<\/code> short and free of secrets or unnecessary personal data.<\/li>\n\n\n<li>Display the payee name and amount before the customer confirms payment.<\/li>\n\n\n<li>Treat the customer return as pending until the backend verifies the payment.<\/li>\n\n\n<li>Verify the UTR and exact amount against the intended merchant account.<\/li>\n\n\n<li>Validate the webhook signature and make event processing idempotent.<\/li>\n\n\n<li>Record the verification result and reference for reconciliation.<\/li>\n\n<\/ul>\n\n\n\n<aside class=\"ap-cta\" aria-label=\"Confirm every paid order\"><div class=\"ap-cta__content\"><p class=\"ap-cta__eyebrow\">Reliable UPI verification<\/p><p class=\"ap-cta__title\">Confirm every paid order<\/p><p class=\"ap-cta__text\">Connect your own merchant account and verify UPI payments with API and signed webhooks.<\/p><\/div><a class=\"ap-cta__btn\" href=\"https:\/\/paymentsetu.com\/auth\/register\">Create your account<\/a><\/aside>\n\n\n\n<h2 class=\"wp-block-heading\">FAQ<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">What is the standard UPI deep link format?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The common structure is <code>upi:\/\/pay<\/code> followed by query parameters such as <code>pa<\/code>, <code>pn<\/code>, <code>am<\/code>, <code>cu<\/code>, <code>tr<\/code> and <code>tn<\/code>. The values describe the payee and payment request; the UPI app still asks the customer to review and authorise the payment.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Is <code>am<\/code> required in a UPI URL?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No for a basic static payment link where the customer enters the amount. For a dynamic order or invoice, include a server-calculated <code>am<\/code> so the payment screen is pre-filled and your backend has an expected amount to verify.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What is the difference between <code>tr<\/code> and <code>tn<\/code>?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><code>tr<\/code> is the transaction reference, such as an order or invoice ID. <code>tn<\/code> is a short descriptive note; it helps people recognise the payment but should not be treated as a secure or unique payment identifier.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Can I mark an order paid when the UPI app returns success?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. A return result only describes what the customer app reported to the calling interface. Verify the payment on the server using the merchant-account transaction data or a verification service, then update the order once with an idempotent webhook or API flow.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Can a UPI deep link replace payment verification?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. It can start a payment and carry useful matching fields, but it cannot independently confirm that the correct amount reached the correct account. Use the deep link for initiation and a server-side UTR-plus-amount check for fulfilment.<\/p>\n\n\n\n<script type=\"application\/ld+json\">{\"@context\": \"https:\/\/schema.org\", \"@type\": \"FAQPage\", \"mainEntity\": [{\"@type\": \"Question\", \"name\": \"What is the standard UPI deep link format?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"The common structure is upi:\/\/pay followed by query parameters such as pa, pn, am, cu, tr and tn. The values describe the payee and payment request; the UPI app still asks the customer to review and authorise the payment.\"}}, {\"@type\": \"Question\", \"name\": \"Is `am` required in a UPI URL?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No for a basic static payment link where the customer enters the amount. For a dynamic order or invoice, include a server-calculated am so the payment screen is pre-filled and your backend has an expected amount to verify.\"}}, {\"@type\": \"Question\", \"name\": \"What is the difference between `tr` and `tn`?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"tr is the transaction reference, such as an order or invoice ID. tn is a short descriptive note; it helps people recognise the payment but should not be treated as a secure or unique payment identifier.\"}}, {\"@type\": \"Question\", \"name\": \"Can I mark an order paid when the UPI app returns success?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. A return result only describes what the customer app reported to the calling interface. Verify the payment on the server using the merchant-account transaction data or a verification service, then update the order once with an idempotent webhook or API flow.\"}}, {\"@type\": \"Question\", \"name\": \"Can a UPI deep link replace payment verification?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. It can start a payment and carry useful matching fields, but it cannot independently confirm that the correct amount reached the correct account. Use the deep link for initiation and a server-side UTR-plus-amount check for fulfilment.\"}}]}<\/script>\n\n","protected":false},"excerpt":{"rendered":"Learn the upi deep link format with pa, pn, am, tn, tr, cu and mc examples, encoding rules, and reliable server-side payment verification for developers.","protected":false},"author":1,"featured_media":565,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_singular_sidebar":"","csco_page_header_type":"","csco_page_load_nextpost":"","footnotes":""},"categories":[29],"tags":[6,30,137,115,28],"class_list":["post-566","post","type-post","status-publish","format-standard","has-post-thumbnail","category-upi-payment-verification","tag-payment-verification","tag-upi","tag-upi-deep-link","tag-upi-intent","tag-webhooks","cs-entry"],"_links":{"self":[{"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/posts\/566","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/comments?post=566"}],"version-history":[{"count":1,"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/posts\/566\/revisions"}],"predecessor-version":[{"id":771,"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/posts\/566\/revisions\/771"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/media\/565"}],"wp:attachment":[{"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/media?parent=566"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/categories?post=566"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/tags?post=566"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}