Delete Mandate
Delete mandates created for a specific customer
1. Introduction
Scenarios where in the end customers of the merchant might request to delete mandate that were created. Delete mandate API allows merchant to delete the mandates.
Note that in certain scenario, where in some card networks (like RuPay, Amex) require the customer to complete an additional AFA using the payment method linked with the mandate to approve the deletion process. Through this action, the mandate set to a ‘deleted’ status at the issuer.
2. API Orchestration
The orchestration of the API/s workflow has been explained below:
| API Reference | Description |
|---|---|
| Delete Mandate | Merchant can delete the mandate using the mandateid. |
| Delete Mandate Update | Merchant needs to call delete mandate update post delete mandate. Only applicable for RuPay & AmEx. |
2.1 Delete Mandate request attributes
Here are some of the attributes required to initiate retrieve mandate request. For more details click here.
Attribute | Description |
|---|---|
mandateid | Unique mandateid created by BillDesk. |
mercid | Unique mercid assigned by BillDesk for the merchant. |
payment_method_type | Payment method type - allowed values are card, upi.
|
For payment method card and network schemes, the required attributes are mentioned in the table below:
| payment_method | Attributes in the payment object | Update Mandate API |
|---|---|---|
| card (Visa, Mastercard, Diners cards) | None | Do not call |
| card Amex, RuPay cards | Refer the Create Mandate request (for Payment details) | Call Update Mandate API |
| upi | None | Do not call |
Updated 6 months ago