Flow Advisory | Autopay Mandates

Advisory: Important Update - UPI AutoPay Interoperability

Deployment Date : July 1st, 2026

This is to inform you of an important update to UPI AutoPay mandates on our platform, in line with NPCI's directive on UPI AutoPay Interoperability, effective July 1st, 2026.

What is UPI AutoPay Interoperability?

NPCI has introduced UPI AutoPay Interoperability to enhance the mandate execution experience for end users.
This allows mandates to be executed across payment gateways and provides end users with visibility of their mandates across UPI apps.
As part of this, NPCI has introduced a new purpose code AZ replacing the earlier purpose code 14.

What is changing on our platform?
We will be handling all required changes at our end. Here is a summary of what changes on July 1st:

New Mandates
All new UPI AutoPay mandates registered on or after July 1st 2026 will be automatically registered with purpose code AZ. No changes are required on your end for new mandate registrations.
Existing Mandates - Created via Intent Flow
Existing mandates created by the payer through the intent flow cannot be migrated to purpose code AZ as per current NPCI and provider guidelines. These mandates will continue to execute as before on the originating bank. Interoperability will not be available for these mandates. There is no impact on execution for your end users - debits will continue to work normally.

What do you need to do?

All changes are being handled at our end. Your existing API integration requires no modifications.

Timeline Summary :

New mandates registered with purpose code AZ - 1st July 2026
Intent mandates - no change, continue on purpose code 14

If you have any questions about this change or how it impacts your integration, please reach out to us.
Please note that you may experience some temporary issues during this deployment. Our team is actively monitoring and will address any concerns promptly to ensure a smooth transition.