Flow Release Notes | Version 3.8.5

Enhancing Compliance for UPI Collect Product as per NPCI Guidelines

Changelog: UPI Collect Restrictions & MCC Whitelisting

Deployment Date: 19th February 2026

Product: UPI Collections V3 - Issue Collect Request

Impact: High (Action Required for non-whitelisted merchants)

In compliance with the latest NPCI guidelines, we have updated our UPI Collect (Pull) request processing logic. To minimize fraud risk and align with ecosystem mandates, UPI Collect is now restricted to specific high-trust merchant categories.

Key Changes

1. MCC-Based Whitelisting: Access to the Issue Collect Request API is now restricted based on your Merchant Category Code (MCC).
2. Permitted Categories: Only merchants registered under the following categories can continue using UPI Collect:
   1. MCC 6012
   2. MCC 6211
3. Automated Blocking: Requests from merchants with any other MCC will be intercepted and declined with a new error status to prevent downstream failures at the bank/NPCI level.

API Response Updates

For merchants outside the whitelisted MCCs, the Issue Collect Request API will now return the following response:

• HTTP Status: 200 OK
• API Status: SUCCESS (Request processed by Decentro)
• Response Key: error_service_deprecated
• Message: As per NPCI directives, this service is not available for the Merchant Category Code (MCC) assigned to you. Please reach out to our support team for more information.

What should you do?

1. Check your MCC: If your business does not fall under 6012 or 6211, your UPI Collect integration will cease to function.
2. Migrate to UPI Intent: We strongly recommend migrating to UPI Intent or Dynamic QR, which offer higher success rates and remain unaffected by these specific restrictions.