1 | Create/Amend/Cancel | (Mandatory) Mandate Type. The Default is ‘Create’. |
2 | Sponsor Bank Profile | The config. profile with the right Sponsor Bank Details as relevant to the Mandate being registered. |
3 | Template | A mandate template having the values of some fields saved. Used for commonly occurring scenarios. |
Mandate Details |
4 | instrument (debit/credit) | Define the type of instrument here, whether the recurring payment is a debit, or credit amount. |
5 | Category (management category) | Every NACH mandate contains a management category code, which defines the type of payment that is being made against a mandate. For example, the code I001 refers to an insurance premium payment, L001 a loan installment payment, and M001 refers to a Mutual Fund payment. Click here for a full list of management category codes. |
6 | Customer Ref Number | CRN. A unique id, where you can pass your internal unique ids. Eg- Loan Id or SIP id. |
7 | Scheme Ref Number | SRN. |
8 | Debit Amount Type (fixed/maximum) | The amount mentioned on the mandate can be of two types; fixed or maximum.
If the amount is fixed, it means only the specific amount mentioned can be debited, nothing more and nothing less.
On the other hand, if the debit amount is maximum, then the actual debit amount can be up to, or including, the value specified.
|
9 | Recurring (yes/no) | If the payment is to be debited more than once, then it is a recurring payment. If Yes is selected, the frequency of the debit has to be defined.
Mandates can have the following frequencies:
As and When Presented: Also known as ‘Ad Hoc’ frequency, this allows multiple payments to be taken everyday. It is permitted for all types of mandates.
Intra Day: Permitted only for eMandates, this allows for multiple payments to be taken everyday.
Daily: Permitted only for eMandates, this allows for a single payment to be taken every day.
Weekly: Permitted only for eMandates, this allows for a single payment to be taken every week.
Monthly: Permitted for all types of mandates, this allows for a payment to be taken once every month.
Bi-Monthly: Permitted only for eMandates, this allows for a payment to be taken once every two months.
Quarterly: Permitted for all types of mandates, this allows for a payment to be taken once every three months.
Semi-Annually: Permitted for all types of mandates, this allows for a payment to be taken once every six months.
Yearly: Permitted for all types of mandates, this allows for a payment to be taken once every year. |
10 | Start Date | The first payment collection date. |
11 | End Date | The final collection date. This is an optional field. If left blank, the recurring payments continue until cancelled. |
Customer Bank Details |
12 | Account Type | Whether the bank account is current, savings, cash credit, etc. |
13 | Account Number | Customer Bank Account number. If left blank, customer has to fill. |
14 | Bank Name | Customer Bank Name. If left blank, customer has to fill. |
15 | IFSC Code | Customer Bank IFSC. If left blank, customer has to fill. |
Authentication Details |
16 | eSign Request From | The mobile number or email ID of the customer in order to authenticate the mandate. |
17 | eSign Request Validity (days) | The number of days that the signature request is valid. |
18 | Mode (optional) | The nature of the mandate, whether eSign (default), Physical or API Mandate (Debit Card/Net Banking auth). |