post https://api.juspay.in/txns/#Merchant-exercise-the-Mandate
After the Mandate is successful, Merchant will receive a mandate_token from Juspay that should be stored against a customer at their end. From the subsequent charge transactions, Merchant is supposed to pass a combination of customer_id and mandate_token to do a charge without a 2nd factor. This API will create order and will charge it based on the mandate_token passed by the merchant.
| Field | Type | Description |
|---|---|---|
| order_id | String | OrderID for which the payment is being started. |
| txn_id | String | Transaction Id for the payment |
| status | String | Status of the transaction. See appendix. |
| payment.authentication.method | String | HTTP Method for authentication. Can be one of GET or POST |
| payment.authentication.url | String | URL to which the user has to be taken to for completing the authentication |
| payment.authentication.params | Params Object | Present only when the method is POST. Parameter map that has to be sent along with the URL for authentication. |
In case of Credit Cards, the charge is real time, so status can be CHARGED or AUTHORISATION_FAILED. In the case of e-mandate (netbanking / aadhaar), this might be PENDING_VBV, for which Merchant should poll after the appropriate time.