Mandate Status
This API can be used by Merchant for checking the recent status of the mandate / (mandate action).
If merchantRequestId is not passed in the requestBody: Recent status of the mandate is denoted by gatewayResponseStatus field in the response. Based on different scenarios gatewayResponseStatus can have multiple values like SUCCESS, FAILURE, REVOKED, PAUSED, COMPLETED, DECLINED, EXPIRED depending upon the current status of the mandate.
If merchantRequestId is passed in the requestBody: Then gatewayResponseStatus denotes the status of that particular action (UPDATE, REVOKE, PAUSE and UNPAUSE) taken on mandate.
Refer to table below for different value of gatewayResponseCode and gatewayResponseStatus.
|
merchantRequestId in reqBody
|
gatewayResponseCode
|
gatewayResponseStatus
|
Description
|
|---|---|---|---|
Present
| 00
| SUCCESS
| Mandate is in active state
|
Present
| 01
| PENDING
| Mandate is in pending state
|
Present
| JPMR
| REVOKED
| Mandate is revoked
|
Present
| JPMP
| PAUSE
| Mandate is paused
|
Present
| JPMC
| COMPLETED
| Mandate is completed
|
Present
| JPMD
| DECLINED
| Mandate is declined by payer
|
Present
| JPMX
| EXPIRED
| Mandate is expried due to no action by payer
|
Not Present
| 01
| PENDING
| Respective Mandate Action is in pending state
|
Not Present
| 00
| SUCCESS
| Corresponding Message for Mandate Action
|
Present / Not Present
| Else
| FAILURE
| Any other reason.
|
Header value should be same as of originalMerchantRequestId sent in request body
Defines the role of the merchant in the mandate.
Value: PAYEE.
Merchant request of the original create mandate request.
Merchant generated unique id for the mandate action. To be used for update, revoke, pause, unpause operations.
Condition: Should be passed to know the status of the Mandate Action.
It should not be passed for create mandate status else BAD_REQUEST error will be thrown.
Current Epoch Unix timestamp string. Has to be of 13 digit in Milliseconds.
Example: 1496918882000.
Merchant Defined Parameters
Example: "{\"udf1\":\"value1\",\"udf2\":\"value2\",…}"
Note: Few special characters are not allowed. Regex for the characters which are not allowed : ^[^/#-()*!%~`]+$
PSP status of the API
Values:SUCCESS, FAILURE
PSP response code for the API.
Values: Refer Codes Guide in Resource Section.
PSP response message for the API.
Values: Refer Codes Guide in Resource Section.
Amount for mandate
Values:Amount in two decimals. Decimals are mandatory
Rule on Mandate Amount. If amountRule is MAX, then mandate can be executed for amount less than or equal to the passed amount . If amountRule is EXACT, then mandate should always be executed for the same amount.
Values:As passed for amountRule in create mandate.
Unique id for the selected bank account. It will not be present if role passed in request is PAYEE and payeeVpa is of merchant.
Values: bankAccountUniqueId in the response of Fetch Accounts api call.
Denotes whether customer's fund should be blocked or not. True for recurring mandate, for ONETIME mandate can be true or false
Values:true / false
Timestamp until which mandate request is valid. It will only be present if request is pending for approval for create mandate or update mandate.
Format:Timestamp in YYYY-MM-DDTHH:MM:SS+05:30 format.
UPI request id returned by gateway for the particular mandate / mandate action request
Customer reference number (rrn) for the mandate / mandate action operation.
Response code returned by gateway for the mandate / mandate action operation.
Values:Refer table below.
Response message returned by gateway for the mandate / mandate action operation.
Denotes the current status of the mandate if upiRequestId is not passed in reqBody. Denotes the status of mandate action if upiRequestId is passed in reqBody.
Values:SUCCESS, FAILURE, PENDING, REVOKED, PAUSE, COMPLETED, DECLINED, EXPIRED
Defines who has initiated the mandate
Values:PAYER, PAYEE
Time instant at which create mandate request was approved. Only present if mandate was initiatedBy PAYEE and upiRequestId is not passed in reqBody.
Format:YYYY-MM-DDTHH:MM:SS+05:30.
Name of the mandate
Timestamp of when the mandate / mandate action was initiated
Format:YYYY-MM-DDTHH:MM:SS+05:30
Defines the type of mandate operation
Values:CREATE, UPDATE, REVOKE, PAUSE, UNPAUSE
Unique id for the merchant channel.
Values:As passed for x-merchant-channel-id in request headers.
Merchant generated unique profile id for customer. It will not be present if role passed in request is PAYEE and payeeVpa is of merchant.
Values:Alphanumeric string with dot(.). Maximum length is 256.
Unique id for the merchant.
Values:As passed for x-merchant-id in request headers
Merchant generated unique id for collect request.
Constraint: Max 35 characters & Alphanumeric.
Refers to upiRequestId used during creation of mandate.
Values:Same as upiRequestId of create mandate.
Defines the date on which the mandate should unpause. It will only be present if mandateType is PAUSE, UNPAUSE.
Format: "YYYY/MM/DD".
Defines the date from which the mandate should pause. It will only be present if mandateType is PAUSE, UNPAUSE.
Format: "YYYY/MM/DD".
Merchant Category Code of the payee merchant.
Name of the Payee involved in mandate. Only present if role is PAYER in request.
VPA of payee.
Name of the Payer involved in mandate. Only present if role is PAYEE in request.
Defines whether mandate is revocable by PAYER or not. Applicable only when it is ONETIME mandate and initiatedBy PAYEE
VPA of payer.
Recurrence Pattern for Mandate.
Values:Same as original mandate in create mandate response.
Recurrence Rule for Mandate. It will not be present for ONETIME, DAILY and ASPRESENTED recurrence pattern.
Values:Same as original mandate in create mandate response.
Recurrence Value for Mandate. It will not be present for ONETIME, DAILY and ASPRESENTED recurrence pattern.
Values:Same as original mandate in create mandate response.
Invoice as sent by merchant or reference to the mandate in the form of url.
Values:String. As passed during creation of mandate.
Any mandate summary
Values:As passed during create mandate response.
Defines the role of the customer in the mandate.
Values:PAYER, PAYEE.
Descibes whether mandate will be shared with payee or not. Applicable only when it is ONETIME mandate and initiatedBy PAYER.
Values:String - true,false.
Type of Mandate Operation.
Values:UPI_MANDATE, QR_MANDATE, INTENT_MANDATE, P2M_MANDATE
Unique Mandate Number used for execution of the mandate. It will not be present if mandate is pending for payer's approval.
Date before which mandate can be executed.
Format:YYYY/MM/DD.
Date after which mandate can be executed.
Format:YYYY/MM/DD.
Merchant Request Id of original mandate.
Account ref id used for approving mandate.
UPI request id returned by gateway for the transaction.
Hashed value of accounts to be passed by merchant for TPV.
Recurrence Value for Mandate. It is not required for ONETIME, DAILY and ASPRENTED recurrencePattern.
Value:FAILURE / SUCCESS
Merchant Defined Parameters
Example: "{\"udf1\":\"value1\",\"udf2\":\"value2\",…}"

