Existing details about the parameters that will be posted to returnUrl can be seen here:
In addition to this, there will be 3 extra parameters.
-
mandate_id - This is a reference Id which needs to be passed by merchant in Notification API and Mandate Execution API for recurring transactions.
-
mandate_token - Merchants who have implemented Mandate token as reference id are suggested to use mandate_id since Notification API supports only mandate_id.
Note: Mandate Execution API supports both mandate_id and mandate_token. -
mandate_status - Based on the authenticated transaction status, this status can be ACTIVE, FAILURE, CREATED.
| Transaction status | Mandate status | Remark |
|---|---|---|
| PENDING_VBV | CREATED | Awaiting for status from PG. This can either move to any of the below 4 status |
| AUTHORIZING | CREATED | Pending - awaiting for terminal state |
| CHARGED | ACTIVE | Transaction is success and the Mandate is set ACTIVE. Recurring debits can only be attempted if Mandate is ACTIVE |
| AUTHORIZATION_FAILED | FAILURE | User completed authentication, but the bank refused the transaction |
| AUTHENTICATION_FAILED | FAILURE | User drop off or not initiated |
Sample Response
https://sandbox.juspay.in/?status_id=21&status=CHARGED&order_id=guest-test-26&mandate_id=h439sfj3430&mandate_token=0ed6dd3dc5984db090b535294b662d01&mandate_status=ACTIVE&signature=wCFja5ZtDzm687LUxkqlw1NQYraC%2Bz540CitnlCouYI%3D&signature_algorithm=HMAC-SHA256
The mandate details will also be provided in order status API and webhook.