v1
latestOpenAPI 3.1.02026-08-045901.5 MBUPI Mandate
Request body
The customer’s UPI ID from which the mandate amount will be debited.
The fixed amount that will be debited from the customer’s UPI account on each cycle.
The transaction amount to be charged for the current order or execution under the mandate.
The date from which the UPI mandate becomes active and eligible for debit.
The date on which the UPI mandate automatically expires.
Defines how often the mandate amount will be debited.(Mandate Frequency can be : WK=Weekly MT=Monthly QT=Quarterly HY=half yearly YR= yearly)
Specifies the rule for when the debit should occur relative to the scheduled date.
The day on which the debit will be attempted based on the selected mandate frequency. For WEEKLY, the value should be between 1 (Monday) and 7 (Sunday). For MONTHLY, QUARTERLY, HALF-YEARLY, and YEARLY, the value should be between 1 and 30/31 depending on the month. For AS (As Presented) frequency, this field is not mandatory as there is no fixed debit day.
Note displayed to the user in the UPI app (PSP) during mandate approval. Maximum length is 50 characters.
Remark or reference entered by the payer for personal identification of the mandate. Maximum length is 50 characters.
Full name of the customer for whom the UPI mandate is being created.
Email address of the customer used for mandate-related communication and reference.
Mobile number of the customer registered with the UPI account for mandate notifications and verification.
Indicates whether the mandate should be automatically executed once it becomes active, without manual intervention.
Response
200
Example response
{
"status": 200,
"message": "Transaction Initiated",
"data": {
"transaction_id": "1765886351475031958",
"BankRRN": "100001955780"
}
}