Import Mandates

Applicable only for eNACH & Physical NACH mandates]

You can move any historical NACH mandate data from other providers to Telr and manage those subscriptions in Telr going forward. 1. This can be done without getting additional authorization from your customer. 2. It will help you use a single interface or a single payment gateway to control all the mandates. 3. It also provides a seamless experience for end customers even if you switch from one gateway to another.

Initiate Porting Process

Telr will assist you throughout the mandate porting process.

Contact Telr Support

Reach out to the Telr support team to initiate the porting process. Nominate Telr as your preferred payment processing partner for your Utility Code or mandates.

Partner Bank Coordination

Once you’ve initiated the process, our team will guide you through the necessary steps to share the list of mandates with your partner bank. This ensures their systems are updated to reflect the change.

Import Mandates into Telr

Import the updated list of mandates into Telr’s system.

Start Processing Payments

With the mandates successfully imported, you can begin processing payments through Telr.

Import Mandates to Telr

To import the mandates, you must upload the file with all the details in the NPCI file format or in the Telr-specified format. Once the file is uploaded, you can check the status of the import by downloading the mandate file. The file also includes the reason for rejection for cases where Telr is unable to import the mandate.

We reject the files -

If the file format is wrong (only csv & xlsx formats are supported), headers are different or all records have invalid data.
If some of the records are wrong, we show a popup asking whether mandates should be imported for the valid records or cancel the whole file.

We will process the file only for the valid records. After the processing is complete - you can see the imported subscriptions in ACTIVE state in the subscriptions page.

The Subscription object of Telr determines how the customer has to be charged. The mandates would be the payment method by which the customers are charged. You can now import mandates from the Subscription Dashboard. You can utilize Telr’s format, with a convenient sample file that is available for download from the Subscription Dashboard. You can now import mandates from the Subscription Dashboard. Merchants can utilize the CF Format, with a convenient sample file that is available for download from the Subscription Dashboard.

File Format

Required Fields	Description
UMRN_NO	UMRN number of the mandate (should be 20 characters).
PAYMENT_TYPE	Import mandates is applicable only for NACH. The value for this should be E_MANDATE.
DEBIT_ACCOUNT_NUMBER	Account number of the customer (should be a maximum of 35 characters). Ensure leading zeros are not trimmed.
DEBIT_ACCOUNT_HOLDER_NAME	Name of the customer (should be maximum of 40 characters).
DEBIT_BANK_ID	Bank ID. It should be the same as the first 4 characters of the UMRN number (should be same as first 4 characters of the UMRN number).
DEBIT_ACCOUNT_TYPE	Account type. Possible values - SAVINGS or CURRENT.
MAX_AMOUNT	Maximum amount of the mandate.
FREQUENCY	Debit frequency. Possible values: • ADHO-Adhoc • WEEK-Weekly • MNTH-Monthly • BIMN-Every 2 months • QURT-Every 3 months • MIAN-Every 6 months • YEAR-Yearly
START_DATE	The date on which the mandate was authorized. (This should ideally be before current date).
END_DATE	Expiry date of the mandate (should be a future date).
SUBSCRIPTION_ID	A unique ID for the subscription. It can include alphanumeric characters, underscore, dot, hyphen, and space. Maximum characters allowed is 200.
CUSTOMER_EMAIL	Email ID of the Customer (should be a valid email address, a maximum of 250 characters are allowed).
CUSTOMER_PHONE	Phone number of the customer (should be a valid phone number, with or without +91).

Conditional Fields

Required Fields	Description
FIXED_AMOUNT	This will be the recurring amount for mandate for the given FREQUENCY. Mandatory field if FREQUENCY is not ADHO.
FIRST_CHARGE_DATE	The first charge date for mandate after importing. Mandatory field if FREQUENCY is not ADHO.

Optional Fields

Required Fields	Description
MAX_CYCLES	The number of charge cycles that is needed before moving the subscription to COMPLETED state.

​Initiate Porting Process

​Import Mandates to Telr

​File Format

Initiate Porting Process

Import Mandates to Telr

File Format