Skip to main content
  • If you are a new customer, use UPI Intent.
  • If you are an existing customer, you must migrate to UPI Intent or UPI QR code to continue accepting UPI payments.

Exemptions

UPI Collect will continue to be supported for:
  • MCC 6012 & 6211 (IPO and secondary market transactions).
  • iOS mobile app and mobile web transactions.
  • UPI Mandates (execute/modify/revoke operations only)
  • eRupi vouchers.
  • PACB businesses (cross-border/international payments).

UPI Collect Flow Configuration

To migrate from UPI Collect, you need to remove the UPI Collect flow configuration from your API calls and replace it with UPI Intent.

Step 1: Remove UPI Collect

Based on your API endpoint, remove the following UPI Collect configuration:
  • For /v1/payments/create/json and /v1/orders endpoints:
  • For /v1/payments/create/upi endpoint:

Step 2: Add UPI Intent

Replace the above configuration with UPI Intent:

Migration Steps by Platform

Follow the platform-specific implementation details below:

Web (Desktop Web)

After updating your API configuration to use UPI Intent (as shown above), the UPI QR code will be generated for desktop web users. Supported API Endpoints:
  • https://api.razorpay.com/v1/payments/create/json
  • https://api.razorpay.com/v1/orders
  • https://api.razorpay.com/v1/payments/create/upi
Refer to the UPI Intent documentation for implementation details.

Mobile Web and WebView

After updating your API configuration to use UPI Intent (as shown above), follow these additional steps:
  1. Use the Intent flow API instead of the Collect flow API.
  2. Once the intent URL is generated, you can:
    • Embed the URL into a QR code that you generate on your end, or
    • Use the returned deeplink directly to initiate the UPI Intent flow.
Refer to the UPI Intent documentation for implementation details.