Overview

This API allows the platform to initiate an UPI-based mandate registration request. The payer can then authorize the request using Intent flow. In this flow, the platform doesn't need to have the payer's VPA. Decentro validates the request and the payer can pay using any supported UPI app on their mobile device. It is suitable for mobile apps.

👍

We support both Intent Flow and Collect Requests with TPV (Third-Party Validation) for UPI Mandate registration.

Flow

Below is the intent flow for using this API.

• The platform captures the mandate details like amount, frequency, timeframe, etc. at their end
• The platform passes the same in this API against the endpoints
• The platform receives a shortened link that can be displayed on the platform's app
• The payer can choose the app of their choice as available on their app
• The payer authorizes the request by using the UPI MPIN
• The platform receives the Mandate Status Callback to a pre-configured endpoint
• The platform receives the status of mandate registration in the callback itself
• Alternatively, the platform can check the status using the Mandate Status API

UPI Autopay Flows:

• Intent Links: UPI Autopay using Intent Links allows users to authenticate and approve recurring payments via a simple link.
• Intent Links with Deep Links: This flow enhances Intent Links by directing users straight to the UPI app for seamless authorization through deep links.
• Collect Requests: Collect Requests enable merchants to request payments directly from the user's UPI app, streamlining the payment process.
• Collect Requests with TPV: This flow includes third-party validation (TPV), ensuring additional security and compliance for Collect Requests before payment authorization.

📘

As per latest NPCI directives, Collect Request capability is only applicable for select use cases - IPO and Secondary Market transactions (Payee MCC - 6012 and 6211), effective from 28th Feb, 2026.

is_downpayment Flag:

• Introduced support for auto-debit within 5 minutes of registration when is_downpayment = true is passed in the Create Mandate API.
• is_downpayment = false first auto-debit won't happen.
• Applicable across all frequencies. For “Daily” mandates, is_downpayment must be always true.
• Presentation is triggered automatically post successful registration.
• If amount_rule = Max then default_amount will be used for debiting within 5mins of registration.
• If amount_rule = Fixed then amount will be used for debiting within 5mins of registration.
• is_first_txn_amount and is_downpayment both cannot be true.
• is_downpayment flag can not be true if start_date > current date
• downpayment_reference_id value will be passed only if is_downpayment is set as true.
• This downpayment_reference_id will be used to initiate the instant presentations(5mins presentations). Value will be passed only if is_downpayment flag is set as true
• The same value can be used to check the presentation status & will be part of merchant callback.

is_first_txn_amount Flag:

• Mandate is registered with the is_first_txn_amount flag enabled.
• Only supported for QR/Intent-based Autopay flows.
• In FAM, the amount rule type must be set to MAX.
• Merchant can collect the specified FAM amount during the first debit.
• Amount specified in default_amount parameter will be considered for instant debit post registration in both is_first_txn_amount & is_downpayment scenario. No changes with default_amount or amount parameter logic.
• A callback with status "ACTIVE" is sent post successful registration.
• A financial callback is sent after the debit attempt.
• If both is_first_txn_amount and is_downpayment are set to false, the mandate will follow the regular flow without upfront collection.
• is_first_txn_amount and is_downpayment both cannot be true.
• Mandate creation will fail if both flags are enabled simultaneously.
• The FAM flag is mandatory for any merchant intending to use this capability.
• One-time frequency mandates are not supported by FAM.
• Support for FAM has been validated across major TPAPs (GPay, PhonePe, Paytm, CRED). Compatibility may vary for other apps.
• is_first_txn_amount flag can not be true if start_date > current date
• first_txn_amount_reference_id value will be passed only if is_first_txn_amount is set as true.
• This first_txn_amount_reference_id will be used to initiate the instant presentations(5mins presentations). Value will be passed only if is_first_txn_amount flag is set as true
• The same value can be used to check the presentation status & will be part of merchant callback.

is_revokable & is_block_funds:

is_block_funds - This flag is used to block funds in the user's bank account. This feature is available only for one-time mandates and IPO & BIMA-ASBA MCCs.

is_revokable - This flag is used to set non-revokable mandates. It is available only for IPO and Lending MCCs. Accepted values are: "true" – the user can revoke the mandate, "false" – the mandate cannot be revoked by the user.

Validations:

• MCC 7322 – Lending
• Allowed: Non revokable mandates
• Not Allowed: Block funds not supported
• Max Amount: ₹1,00,000
• Frequency: All

• MCC 6211 – IPO & MCC 6300 – BIMA / ASBA (Insurance)
• Allowed: Supports both non revokable & block funds.
• Max Amount: ₹5,00,000
• Frequency: One Time

Mutual Funds Order Details

• A new optional field mutual_funds_order has been added to the request payload.
• This field is an array that supports multiple mutual fund order entries.
• Each entry can include: member_id, user_id, mf_partner, folio_number, order_number, amount, scheme_code, amc_code, pan_number, and investment_type.
• If mutual fund details are included in the request, they will be returned unchanged in the callback payload.
• If omitted, the mandate flow and callback remain unchanged.

📘

Note

If an Autopay intent link is opened on a desktop, a QR code will be displayed by default.

Mandate Status

Frequency

Below are the parameters accepted under the 'frequency' field in the request body and their interpretation.

Rule Type

Below are the parameters accepted under the 'rule_type' field in the request body and their interpretation.

Amount Rule

Below are the parameters accepted under the 'amount_rule' field in the request body and their interpretation.

API Endpoints

Below are the API endpoints to be used by the platform basis the environments.

Simulation Data

Decentro's simulation data helps developers simulate all the real-world scenarios when using the Create mandate API.
This requires the platform to use standard request payloads to handle scenarios for each API and scenario, as mentioned below.
The platform will need to whitelist their IP and configure callback endpoints with Decentro if they wish to handle the flow. Please reach out to us at [email protected] for the same.

How to test?

Below is the flow to test the Simulation data

1. Generate a mandate link by using Create Mandate API with the 'amount' parameter in the required range as mentioned in the test bed section.
   1. Note: To test the instant presentation within a 5-minute scenario when the amount rule is set to MAX, ensure that you pass the simulation amount value in the default_amount parameter.
2. Click the generated link once before proceeding. This is a mandatory step to receive the simulation responses.
3. Next Decentro will propagate the updated status of the mandate as per the amount (range) passed in step-1.
4. Alternatively, client can use Get Mandate Status to fetch the latest status of the mandate.
5. Next proceed to trigger the Pre Debit Notification API to test various scenario basis the amount range values mentioned in the respective test bed section.
6. Next, proceed to trigger the Mandate Presentation API to test various scenarios basis the amount range values as mentioned in the respective test bed section.
7. Note: The simulation environment is an exact replica of production environment including all the checks of production systems for registration, notification and, presentation .

Test Bed

Mandate Creation

Pre Debit Notification

Presentation

Mandate Presentation Callback

Mandate Registration Callback