--- page_title: Interoperable Mandates product: API Reference page_source: https://juspay.io/in/docs/api-reference/docs/express-checkout/interoperable-mandates llms_txt: https://juspay.io/in/docs/llms.txt product_llms_txt: https://juspay.io/in/docs/api-reference/llms.txt --- # UPI Mandates Interoperatability ## **Overview** **UPI Interoperability** is a new NPCI capability that allows **Purpose Code 14 mandates** to be linked to an NPCI-issued **Merchant Identifier Code (MIC)** instead of a specific payment gateway (PG). This enables mandate execution across multiple supported PGs. **This feature is applicable only to Purpose Code 14 mandates** and **does not apply** to: * One-Time Mandates (Purpose Code 01) * Single-Block Multi-Debit Mandates (Purpose Codes 76, 77) ## **How a Mandate Becomes Interoperable** ### **1. New Mandates** To create an interoperable mandate, the **AZ purpose code** must be sent to NPCI. Once supported by a PG, this will be handled by either **Juspay or the PG** , allowing merchants to execute the mandate through any supported gateway. ### **2. Existing Mandates** Existing mandates must be converted using a PG-provided **"Update Mandate to Interoperable"** API. > **Note** > Mandate lifecycle webhooks from the TPAP will continue to be routed to the original PSP. --- ## **Payment Gateway Changes** ### **1. Mandate Registration** PG implementations currently vary as the ecosystem is still evolving: * Some PGs require the **AZ purpose code** during mandate registration. * Others require a separate interoperability flag followed by an **Update Mandate to Interoperable** API after registration. ### **2. Mandate Execution** Since different PGs may not have the mandate's execution history, merchants must provide the **sequence number (seqNumber)** during recurring execution. If the mandate was registered on a different PG, additional fields may also be required (depending on the PG), such as: * UMN - NPCI Side identifier * seqNumber - Donates the count of the execution at NPCI against a UMN * originalMerchantRequestId - MerchantRequestId sent during Registeration * payerVpa - Users VPA * purpose - AZ ( a new purpose code turning the earlier purpose code recurring mandates into interoperable Mandate) * MIC - Merchant identification code ( NPCI Side merchant identifier) - Common entity on which the mandate will become interoperable Juspay is developing a unified API to abstract these gateway-specific differences. Documentation will be shared shortly. ### **3. Making of the existing Mandates to be interoperable Mandates** The older Mandates can be ported to new interoperable Mandates by calling the Port Mandate API of Juspay ( Currently still the docs are being awaited by different PGs at Juspays end) to port the mandates once thats done, older Mandates can be ported to new Interoperable Mandates. > **Note** > Even after making the Mandates interoperable the Mandate lifecycle webhooks will still continue to come on the original Payee PSP only. Just the Mandate execution and notification can be hit to different PG. --- ## **Supported Gateways:** | Payment Gateway | Mandate Registration | Mandate Recurring | Older Mandates to interoperable Mandates API | |---|---|---|---| | AXIS_BIZ | Integrated | Currently integrating | Integrated | | KOTAK_BIZ | Integrating | Currently integrating | Integrated | | RBL_BIZ | Integrated | Currently integrating | Integrated | | YES_BIZ | Integrated | Currently integrating | Integrated | | HSBC_BIZ | Integrating | Currently integrating | Integrated | | HDFC_UPI | Integrating | Not picked up | Not picked up | | Billdesk | Awaiting docs | Awaiting docs | Awaiting docs | | Camspay | Awaiting docs | Awaiting docs | Awaiting docs | | Cashfree | Awaiting confirmation | Awaiting confirmation | Awaiting confirmation | | Digio | Awaiting docs | Awaiting docs | Awaiting docs | | Easebuzz | Awaiting docs | Awaiting docs | Awaiting docs | | HDFC_SMARTGATEWAY | Integrating | Awaiting docs | Awaiting docs | | Hyper_PG | Awaiting docs | Awaiting docs | Awaiting docs | | ICICI_UPI | Awaiting docs | Awaiting docs | Awaiting docs | | Paytm_V2 | Awaiting docs | Awaiting docs | Awaiting docs | | PayU | Awaiting docs | Awaiting docs | Awaiting docs | | Phonepe | Awaiting docs | Awaiting docs | Awaiting docs | | Pinelabs online | Awaiting docs | Awaiting docs | Awaiting docs | | Razorpay | Awaiting docs | Awaiting docs | Awaiting docs | | SETU | Awaiting docs | Awaiting docs | Awaiting docs | | TPSL | Awaiting docs | Awaiting docs | Awaiting docs | > **Note** > Please check with the gateways for latest integration status , Some gateways have done changes at thier end and started making the mandates interoperable at their end but still are in the process of sending the communication out. or suggesting the required changes. --- ## FAQ’s ## FAQs: ### Is interoperability mandatory for all merchants, or can I continue using the existing flow? Currently the NPCI Mandate is to start having all the eligible recurring transaction ( purpose code 14) to be created as interoperable Mandates, but the execution for interoperable Mandates is on the discretion of the merchants. ### Can a converted mandate be reverted back to a non-interoperable mandate? No, the interoperable Mandates can be converted back to Non interoperable Mandates ### Does converting a mandate require customer consent or re-authentication? No, The Mandates can be made interoperable without the user-consent here ### What all changes are needed for the merchants? Currently its PG dependent, Some PGs are mandating merchants to make changes such as pass purpose code as 14 to make the mandates as interoperable, whilst other PGs are handling this at their own. By default creating the Mandates as interoperable mandates. ### Interoperatability was in news for a long time, but wasnt rolled out because of UPI Interoperatability system readiness. Is the ecosystem ready now? Still the readiness of the ecosystem is happening , but NPCI has asked the major Banks and TPAPs to be ready and approx 15-20 Banks are ready along with the major TPAPs for now. So some of the PGs are exposing a field right now to see if the mandate can be interoperable, and if the mandate can be interoperable, the API can be called to make it interopable for the merchants side. Juspay will also be exposing the required fields in the order status and Mandate status API. ### Can i execute the interoperable Mandates to different PGs? Still awaiting the docs from PGs for the mandate execution API, as now another set of NPCI execution required parameters will be needed to be exposed. At Juspay we are building currently a PL logic for Notification and Mandate execution where merchants can enable whether if they want the Mandate to be interoperable at the Juspays dashboard, And then based on the PL the mandatePayment transactions can be routed. --- ## See Also - [One Time Mandate](https://juspay.io/in/docs/api-reference/docs/express-checkout/one-time-mandate) - [Mutual Fund Flow in Mandates](https://juspay.io/in/docs/api-reference/docs/express-checkout/mutual-fund-flow-in-mandates)