{"id":544,"date":"2026-11-01T12:00:00","date_gmt":"2026-11-01T12:00:00","guid":{"rendered":"https:\/\/paymentsetu.com\/blog\/?p=544"},"modified":"2026-11-01T12:00:00","modified_gmt":"2026-11-01T12:00:00","slug":"upi-collect-request-discontinued-merchants","status":"publish","type":"post","link":"https:\/\/paymentsetu.com\/blog\/upi-collect-request-discontinued-merchants\/","title":{"rendered":"UPI Collect Request Discontinued: What Merchants Use Now"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">UPI collect request discontinued is the search many Indian merchants make after a customer can no longer pay by entering a UPI ID and waiting for a request. The change is narrower than \u201cUPI has stopped\u201d: NPCI ended person-to-person Collect transactions from 1 October 2025, while merchant checkouts are moving towards payer-initiated QR and intent flows.<\/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\">What changed and when<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">There are two changes that are often mixed together.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">First, NPCI Circular <strong>NPCI\/UPI\/OC\/220\/2025-26<\/strong>, issued on 29 July 2025, says that <strong>UPI P2P Collect shall not be allowed to be processed from 1 October 2025<\/strong>. It instructs member banks, Payment Service Providers and UPI apps to stop P2P Collect from being initiated, routed or processed. You can read the <a href=\"https:\/\/www.npci.org.in\/PDF\/npci\/upi\/circular\/2025\/UPI-OC-No-220-FY-2025-26-Discontinuing-the-service-of-UPI-Collect-Request-for-Person-to-Person-P2P-transactions.pdf\" target=\"_blank\" rel=\"noopener\">original NPCI circular<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">P2P means one person requesting money from another person. For example, a freelancer might have entered a client&#8217;s UPI ID and sent a request, or a friend might have requested a share of a dinner bill. The payer then received a notification and approved the debit with a UPI PIN.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Second, merchant checkout providers have been migrating manual VPA-entry Collect flows to QR and intent-based flows. Many implementations stopped offering one-time Collect entry on Android and desktop from 28 February 2026, while the exact channel and use-case treatment depends on the provider, acquirer and applicable exemptions. Confirm the live behaviour of your payment setup before changing a production checkout.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The practical rule for a merchant in October 2026 is simple: do not build a new checkout around \u201center your UPI ID and we will send a request\u201d. Build around a customer-initiated payment, then verify the resulting payment against the order.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Is UPI Collect discontinued for all payments?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">No. \u201cUPI Collect request discontinued\u201d does not mean UPI, UPI IDs, QR codes or merchant payments have been switched off.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">NPCI\u2019s own <a href=\"https:\/\/www.npci.org.in\/what-we-do\/upi\/faqs\" target=\"_blank\" rel=\"noopener\">UPI FAQ<\/a> describes several UPI payment modes, including QR, intent, application-based and Collect. The FAQ is useful background, but a merchant should follow the current flow supported by its bank, PSP or checkout provider because implementation rules change over time.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Use this distinction when explaining the change to your team:<\/p>\n\n\n\n<figure class=\"wp-block-table ap-table\"><table><thead><tr><th>Flow<\/th><th>Who starts the payment?<\/th><th>What the customer does now<\/th><\/tr><\/thead><tbody><tr><td>P2P Collect<\/td><td>The requester<\/td><td>This person-to-person request is no longer processed after 1 October 2025<\/td><\/tr><tr><td>Merchant QR<\/td><td>The payer<\/td><td>Scans the merchant QR, checks the amount and approves in a UPI app<\/td><\/tr><tr><td>UPI Intent<\/td><td>The payer<\/td><td>Selects a UPI app or payment option and approves the pre-filled payment<\/td><\/tr><tr><td>Manual VPA-entry Collect<\/td><td>The merchant or payee<\/td><td>Treat as a legacy flow and confirm whether your provider still permits it<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">The customer still needs to review the payee and amount before entering a UPI PIN. A PIN authorises money leaving the payer&#8217;s account; it is never needed to receive money.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Who is affected?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The first group affected was people using P2P Collect for personal requests. A request from one individual to another is the clearest case covered by Circular 220. They should instead share a QR code, UPI ID or payment link and let the payer initiate the transfer.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The second group is merchants whose checkout asks the buyer to type a UPI ID or mobile number. This is especially relevant to older hosted checkouts and custom integrations that show a \u201cPay by UPI ID\u201d field. Those integrations need a current provider confirmation and, in most cases, a migration to QR or intent.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The third group is developers maintaining order systems. Even when the payment rail remains available, a payment method is only useful if the order can be matched reliably. A static QR with no order reference may collect money but leave the merchant matching each credit by hand.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Not every merchant has to rewrite an entire store. Start by listing every place where UPI appears:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li>Website or app checkout.<\/li>\n\n\n<li>Payment links sent by WhatsApp or email.<\/li>\n\n\n<li>Printed QR at a counter or service desk.<\/li>\n\n\n<li>Invoices for services, renewals or bookings.<\/li>\n\n\n<li>Webhook and order-status handling in your backend.<\/li>\n\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Mark any screen that asks the buyer to type a UPI ID. That is the first integration to review. QR and intent buttons should remain the primary choices, subject to the current support of your bank or payment provider.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">QR and intent flows: the practical alternatives<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">QR and intent are both payer-initiated, but they suit different screens.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Dynamic UPI QR<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A dynamic QR is generated for a particular order. The customer scans it in a UPI app, checks the displayed payee and amount, and approves the payment. The order reference can travel with the payment request so your system has a useful key for matching.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This works well on desktop checkout, a second phone, an invoice PDF or a counter display. For a small counter that only needs a reusable QR, PaymentSetu also provides a <a href=\"https:\/\/paymentsetu.com\/free-upi-qr-code-generator\">free UPI QR code generator<\/a>; for order-level automation, use a dynamic QR tied to the order.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">UPI Intent<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Intent lets a customer choose a UPI app from the checkout. On a compatible mobile device, the selected app opens with the merchant and amount pre-filled. The customer reviews the details and approves with the UPI PIN.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Intent is usually the smoother mobile experience because the buyer does not have to remember or type the merchant&#8217;s UPI ID. Your checkout still needs a QR fallback for browsers, desktops and devices where the selected app cannot open directly.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">A payment link<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A payment link can take the customer to a page that presents the current QR or intent options. It is useful for WhatsApp orders, invoices and service appointments because the merchant can send a single order-specific URL.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The link is not the verification itself. Your backend should wait for a confirmed payment event or status response, match it to the order, and only then mark the order paid.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How automatic verification replaces the old request workflow<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The old Collect model was attractive because the merchant could address a request to a customer&#8217;s UPI ID. The safer replacement is to create an order first, show the customer a payer-initiated QR or intent flow, and verify the payment after the customer completes it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">With PaymentSetu, the customer pays directly into the merchant&#8217;s own connected Paytm Business or PhonePe Business merchant account. PaymentSetu is a payment verification service, not a payment gateway: it matches the UTR and amount to the dynamic QR or order and sends a webhook. It does not hold the payment.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A typical flow looks like this:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li>Your store creates an order with a unique order ID and exact amount.<\/li>\n\n\n<li>The checkout displays a dynamic QR and, where appropriate, an intent option.<\/li>\n\n\n<li>The customer approves the payment in their UPI app.<\/li>\n\n\n<li>PaymentSetu matches the payment details to the order.<\/li>\n\n\n<li>Your server receives the HMAC-signed webhook and checks the event before fulfilling the order.<\/li>\n\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">The important difference is that the customer initiates the payment. The merchant&#8217;s system is responsible for presenting the right amount and verifying the result, not for asking the payer to approve an unsolicited pull request.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For a WooCommerce store, the <a href=\"https:\/\/paymentsetu.com\/woocommerce-plugin\">PaymentSetu WooCommerce plugin<\/a> can connect the checkout to this workflow. Hosting companies can use the <a href=\"https:\/\/paymentsetu.com\/whmcs-plugin\">WHMCS module<\/a> for invoices and renewals. Developers using a custom stack can use the API and HMAC-signed webhooks documented in their PaymentSetu setup.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">A migration checklist for merchants<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Use this checklist before removing an old Collect option:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li><strong>Inventory the old flow.<\/strong> Find every page, plugin, API call and message template that asks for a UPI ID or mobile number.<\/li>\n\n\n<li><strong>Confirm the supported channels.<\/strong> Ask your bank, PSP or provider which QR and intent modes are live for your merchant account, devices and customer browsers.<\/li>\n\n\n<li><strong>Create an order-specific reference.<\/strong> Keep the order ID, amount and expiry together so a payment can be matched without relying on a screenshot.<\/li>\n\n\n<li><strong>Add both QR and intent where useful.<\/strong> Intent suits mobile; QR is important for desktop, second-device and fallback journeys.<\/li>\n\n\n<li><strong>Verify server-side.<\/strong> Do not mark an order paid because the buyer saw a success screen or sent a screenshot. Check the provider status or signed webhook.<\/li>\n\n\n<li><strong>Make webhook handling idempotent.<\/strong> The same event should not fulfil an order twice. Store the event or transaction reference and ignore a duplicate after the first successful update.<\/li>\n\n\n<li><strong>Test the customer journey.<\/strong> Test mobile intent, desktop QR, a delayed return to checkout and an already-paid order in staging before changing live settings.<\/li>\n\n\n<li><strong>Update customer instructions.<\/strong> Tell buyers to scan the QR or choose their UPI app. Remove wording that promises a collect request will arrive.<\/li>\n\n<\/ol>\n\n\n\n<aside class=\"ap-note\"><p>A UPI PIN approves a debit from the payer\u2019s account. A customer never needs to enter a UPI PIN to receive money.<\/p><\/aside>\n\n\n\n<h2 class=\"wp-block-heading\">How to choose between QR, intent and a payment gateway<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The choice depends on how much control you need over the merchant account and reconciliation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Choose QR when customers may pay from a desktop, a second phone, a printed invoice or a physical counter. Choose intent when most customers are already on mobile and you want the shortest path into their UPI app.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Choose an automated verification layer when a successful payment must change an order, invoice, booking or account balance without manual checking. PaymentSetu keeps the UPI payment in your own connected merchant account, charges 0% commission on the payment, and uses a flat plan rather than a per-transaction commission. Its <a href=\"https:\/\/paymentsetu.com\/auth\/register\">Pro plan<\/a> is \u20b9999 per 30 days with 1,000 credits, where one credit represents one successful payment verified.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That is different from selecting a payment gateway solely because it offers a Collect field. The field may disappear as the ecosystem moves to payer-initiated flows; your lasting requirement is the combination of a customer-friendly payment method and a trustworthy order-status signal.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Common mistakes after Collect is removed<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Treating every failed request as a UPI outage<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A missing Collect notification may simply mean the old flow is no longer permitted for that channel. Check whether the customer was offered QR or intent before diagnosing a wider payment issue.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Keeping a UPI ID field as the only option<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Manual entry adds typing and creates a dependency on a flow that is being retired in many merchant checkout implementations. Put QR and intent at the centre of the checkout and keep the payment instructions current.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Accepting screenshots as proof of payment<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A screenshot can show that a payment screen was opened; it does not give your backend a confirmed order status. Match the amount and transaction reference through your merchant account or verification service before fulfilment.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Using one static QR for every order<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A static QR can be useful at a counter, but every credit may look alike. For an online order, generate a QR tied to the amount and order reference so reconciliation is automatic.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">FAQ<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Is UPI Collect completely discontinued in India?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. NPCI Circular 220 discontinued <strong>P2P<\/strong> Collect from 1 October 2025. Merchant checkout implementations are also moving away from manual VPA-entry Collect, with availability depending on the channel, provider and use case, so merchants should not assume an old integration will remain available.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Can customers still pay a merchant by scanning a UPI QR?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Yes. QR is a payer-initiated UPI flow: the customer scans, checks the payee and amount, and approves the payment in their UPI app. A merchant should still verify the resulting transaction before delivering goods or services.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What is the difference between UPI Collect and UPI Intent?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Collect asks the payee or merchant to address a request to the customer&#8217;s UPI ID. Intent starts from the customer&#8217;s checkout action and opens a selected UPI app with payment details pre-filled; the customer then reviews and approves the debit.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How can I verify QR payments automatically?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Use a dynamic QR tied to the order and a server-side status or webhook flow. PaymentSetu matches the UTR and amount to the order and sends a webhook, so your store can update the order after confirmation instead of relying on a screenshot.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Do I need to replace my whole checkout?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Not necessarily. First identify the old UPI ID-entry step, then confirm the QR and intent options supported by your provider. Many merchants can update the payment method and verification callback while keeping the rest of their order, invoice or booking workflow.<\/p>\n\n\n\n<aside class=\"ap-cta\" aria-label=\"Verify every QR payment\"><div class=\"ap-cta__content\"><p class=\"ap-cta__eyebrow\">Ready for payer-led UPI<\/p><p class=\"ap-cta__title\">Verify every QR payment<\/p><p class=\"ap-cta__text\">Move from old Collect requests to QR, intent and automatic order verification with PaymentSetu.<\/p><\/div><a class=\"ap-cta__btn\" href=\"https:\/\/paymentsetu.com\/auth\/register\">Start verifying payments<\/a><\/aside>\n\n\n\n<p class=\"wp-block-paragraph\">DONE upi-collect-request-discontinued-merchants words=2056<\/p>\n\n\n\n<script type=\"application\/ld+json\">{\"@context\": \"https:\/\/schema.org\", \"@type\": \"FAQPage\", \"mainEntity\": [{\"@type\": \"Question\", \"name\": \"Is UPI Collect completely discontinued in India?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. NPCI Circular 220 discontinued P2P Collect from 1 October 2025. Merchant checkout implementations are also moving away from manual VPA-entry Collect, with availability depending on the channel, provider and use case, so merchants should not assume an old integration will remain available.\"}}, {\"@type\": \"Question\", \"name\": \"Can customers still pay a merchant by scanning a UPI QR?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Yes. QR is a payer-initiated UPI flow: the customer scans, checks the payee and amount, and approves the payment in their UPI app. A merchant should still verify the resulting transaction before delivering goods or services.\"}}, {\"@type\": \"Question\", \"name\": \"What is the difference between UPI Collect and UPI Intent?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Collect asks the payee or merchant to address a request to the customer's UPI ID. Intent starts from the customer's checkout action and opens a selected UPI app with payment details pre-filled; the customer then reviews and approves the debit.\"}}, {\"@type\": \"Question\", \"name\": \"How can I verify QR payments automatically?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Use a dynamic QR tied to the order and a server-side status or webhook flow. PaymentSetu matches the UTR and amount to the order and sends a webhook, so your store can update the order after confirmation instead of relying on a screenshot.\"}}, {\"@type\": \"Question\", \"name\": \"Do I need to replace my whole checkout?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Not necessarily. First identify the old UPI ID-entry step, then confirm the QR and intent options supported by your provider. Many merchants can update the payment method and verification callback while keeping the rest of their order, invoice or booking workflow. DONE upi-collect-request-discontinued-merchants words=2056\"}}]}<\/script>\n\n","protected":false},"excerpt":{"rendered":"UPI collect request discontinued? Learn what NPCI changed, which merchant flows remain, and how QR, intent and payment verification work now.","protected":false},"author":1,"featured_media":543,"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":[116,6,114,115,52],"class_list":["post-544","post","type-post","status-publish","format-standard","has-post-thumbnail","category-upi-payment-verification","tag-npci","tag-payment-verification","tag-upi-collect","tag-upi-intent","tag-upi-qr","cs-entry"],"_links":{"self":[{"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/posts\/544","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=544"}],"version-history":[{"count":1,"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/posts\/544\/revisions"}],"predecessor-version":[{"id":740,"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/posts\/544\/revisions\/740"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/media\/543"}],"wp:attachment":[{"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/media?parent=544"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/categories?post=544"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/tags?post=544"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}