Grievance Redressal Policy


The objective of our grievance redressal policy is to provide timely and comprehensive resolution to customer complaints, queries and grievances.

The policy encompasses the following key aspects:

  • Registration and Acknowledgement of complaints
  • Handling of Grievances
  • Complaint resolution

Registration and Acknowledgement of complaints

Complainants may raise a Complaint / Grievance request through the following modes:

a) Chatbot

Chatbot offers instant support in resolving the queries.

b) Get-Help

Get-help provides service for raising a ticket for any complaint.

c) Website

Complainants may write to the following Email IDs mentioning all the required details for lodging the Complaint , at HelpDesk contact details :-

TeamContact detailsTAT
Help Desk TeamE-mail ID:
3 to 7 business days
Customer Grievance Redressal Officer

Sandeep Goyal
E-mail ID: NDPS.grievanceredressal@nttdata.com

Address :- Plot No, 4th Floor, Suraksha Ace Building, CST No. 34/3 Village Chakala, 2-A, Andheri - Kurla Rd, Andheri East, Mumbai, Maharashtra 400059

12 business days from the date of escalation
d) Helpline number

Complainants may reach out to the number: 18602664959 between business hours i.e. 8 AM to 8 PM every working day of the week.

e) Mobile application (App)

Complainants may lodge a Complaint / Grievance on the App “mGalla” launched by the Company.

All the complaints received via the above-mentioned modes will be registered on the Complaint Resolution Management (“CRM”) system of the Company and will be addressed by the Customer Service team which will consist of trained employees experienced to handle such complaints. A Unique Ticket Number (“UTN”) will be generated in the Company’s CRM system for all types of complaints.

Handling of Grievances

For Transaction based complaints, the Complainants are required to share the below details for registration of complaints:

  • Transaction reference number;
  • Complainant’s registered name;
  • Complainant’s email Id;
  • Complainant’s contact number;
  • Complainant’s ID (MID / TID / Agent ID as applicable);
  • A brief description on the issue;
  • Copy of supporting document, if any; and
  • Any other relevant information as required by the Company for complaint resolution.

Please find below type of grievance with regards to PA business and estimated Turn-Around-Time (TAT) for resolution :

Sr. No. Type of grievanceEstimated TAT for resolution
1Transaction/ Onboarding3 - 5 business days from the date of complaint
2Service Enable/ Disable3 - 5 business days from the date of complaint
3Refund5 - 7 business days from the date of complaint
4Settlement5 - 7 business days from the date of complaint
5Any other business operations5 - 7 business days from the date of complaint
Note: - TAT may be higher if grievance redressal has dependency on external teams like banks or other parties, serviceability due to far off locations and other external factors.

Complaint resolution

A complaint will be considered as closed in any of the following instances:

   a. When the Company has resolved the query / complaint of the complainant;

   b. Where the Complainant has indicated in writing, its acceptance of the response of the Company; and

   c. Where the Complainant has not responded within 3 business days of the receipt of the written response of the Company.

The Customer Service team will reach out to the Complainant to confirm that the Complaint has been resolved once the concerned function marks the complaint as “resolved” in the system. Post confirmation, the Complainant will be intimated via email that their Complaint has been resolved. The intimation of resolution will contain the UTN, the solution / explicitly mention that the issue has been resolved, the escalation matrix and TAT in case the resolution is not per the expectations of the Complainant, etc. In case of rejection of the complaint, response will be sent to the Complainant with reasons thereof recorded in writing.

Please note, PA related complaints will be resolved within a period of 30 business days of its receipt as per the prescribed regulations.

Disputes / Chargeback Management

Disputes/Chargebacks can be associated with unsatisfactory customer services or product or poor service delivery experience from the merchant. Chargebacks can also be filed if the customer suspects any fraudulent activity on their card. Once a cardholder files a complaint with the issuer Bank, the dispute is forwarded by the associations to the acquirer who in turn raises the dispute/Chargeback to the service provider to initiate an investigation. NDPS further shares the chargeback with the Merchant.

Disputes/Chargebacks cases are considered high priority due to the involvement of Disputes/Chargeback handling team of both the customer’s bank as well as our partner banks. There could be several reasons for a chargeback against a particular transaction. A list of the most common reasons for chargeback are as below :-

Dispute Reasons

  • Transaction amount is different
  • Request is made for the copy of the receipt
  • Merchandise is defective or damaged
  • Alleged fraudulent transaction investigated by the acquiring bank
  • Multiple charges for the same order
  • Merchant agreed to issue refund on merchandise returned or for any other reason
  • Merchandise not as advertised
  • Customer did not engage in or authorize this transaction
  • Merchandise has not been delivered
  • Cardholder is not in possession of the card used for the transaction
  • Service not received from merchant
  • Order was cancelled
  • Customer paid for order by other payment method

Process to resolve Disputes/chargebacks

  • NDPS will notify Merchant by email about the dispute, with the common transaction details along wjth the payment ID and the reason of chargeback, which is provided by the bank.
  • In order to represent the chargeback, Merchant needs to review the Disputes/chargeback and provide documentary evidence to contest or defend the dispute with the stipulated time
  • NDPS may request for additional documents for cases that need further investigation. These documents could include based on the merchant business or  Authorization Letter from the customer, Cancellation Policy, etc.
  • Merchants needs to respond by sharing all the required documents as per the requirement of the bank along with a clarification/explanation in email. NDPS shall be check the documents and represent the dispute.
  • Merchant needs to revert within the turn-around-time with the required document, in case non receipt and non-available of the documents merchant is liable for disputes.

Most of chargebacks arise due to miscommunication between Customer and Merchant, the following are the best practices for merchants when processing payments/ settlements to avoid chargebacks or disputes.

  • Transparent Return Policy – Merchants should ensure that all refund/ return policies are clearly stated on their website.
  • Clear and Constant Communication - Merchants must keep their customers informed about the status of orders/delivery.
  • To avoid any uncertainty, merchants should share reference numbers, invoices details, and other order/services related documents with customers.

Refund Management

Refund Processing Timelines

NDPS has a very stringent mechanism to deal with refunds of failed transactions (transactions charged to customer but not returned to Payment Aggregator and, in turn, to merchant, hence no services are rendered). As per the merchant's line of business, they can opt to configure their account to reverse such transactions or get it updated as a successful transaction post reconciliation, and continue to provide services.

We can reconcile dropped transactions in 2 ways:

  • We initiate server-to-server API calls with banks on periodic basis throughout the day to fetch the status of transactions. Such cases are sent to bank for reversal on T+1.
  • For banks who do not provide the API-based reconciliation mechanism, we reconcile with the offline files received from the banks on the next working day. Thus refunds for such transactions are sent the next day post reconciliation or T+1 post reconciliation.

Refund Reasons

  • Merchant has initiated the refund to the customer because he is unable to provide goods or services or due to a customer complaint about the service to merchant.
  • There are duplicate transactions and one of the duplicate transactions has to be refunded.

Once a refund has been initiated, NDPS refunds to the source account as follows –

  • Merchant is provided with a refund API or batch mechanism to initiate complete or partial refund in portal.
  • Batch file is processed by the payment team at NDPS to acquiring bank to initiate refund to the source account.
  • Refund is processed from the acquiring bank to the source account. Daily reconciliation of the files is done to check on refund RRN and the same is reflected on merchant dashboard and payout file on the merchant’s portal.
  • In case there are issues or queries related to any of the details related to refund, then the merchant can reach out to the Customer Service Team