RANAPAY INDIA PRIVATE LIMITED
CUSTOMER GRIEVANCE REDRESSAL POLICY
POLICY NO. 09 | VERSION 1.0
EFFECTIVE DATE: 29 SEPTEMBER 2026
| Document Control | Details |
|---|---|
| Company | RANAPAY INDIA PRIVATE LIMITED |
| CIN | U72900UP2021PTC140275 |
| Registered Office | D30, Vibhuti Khand, Gomti Nagar, Lucknow, Uttar Pradesh – 226010 |
| Website | ranapay.in |
| Business Context | Gift Cards, Gift Vouchers & Virtual Gift Products through applicable authorised/regulated partners |
| Policy Owner | Customer Support / Compliance |
| Review Frequency | At least annually / event driven |
| Classification | Confidential – Controlled Compliance Document |
1. PURPOSE
This Policy establishes a transparent, accessible and documented framework for receiving, registering, investigating, resolving and escalating customer complaints and grievances relating to RanaPay's products and services.
2. ROLE & PARTNER PRINCIPLE
Where a complaint concerns a PPI issuer, bank, payment processor, merchant or other partner, RanaPay shall identify the responsible entity and coordinate resolution in accordance with applicable law, contractual arrangements and the relevant partner's grievance process.
3. OBJECTIVES
- Provide accessible complaint channels.
- Acknowledge and track complaints.
- Resolve complaints fairly and consistently.
- Provide clear customer communication.
- Escalate unresolved or material complaints.
- Identify recurring issues and improve controls.
- Maintain complete grievance records.
4. SCOPE
This Policy covers complaints relating to gift cards, vouchers, virtual products, purchase, delivery, activation, redemption, refunds, unauthorised transactions, payment issues, customer service and other RanaPay-supported activities.
5. GRIEVANCE CHANNELS
- Website/customer-support channel
- Email or other officially published channel
- In-app or digital support channel where available
- Partner escalation channel where applicable
- Written communication to the registered office where accepted
Current contact details and operating hours shall be published through appropriate customer-facing channels.
6. TYPES OF GRIEVANCES
- Transaction issue
- Gift card/voucher issue
- Delivery issue
- Activation/redemption issue
- Refund/cancellation issue
- Unauthorised transaction
- Fraud complaint
- Payment/settlement complaint
- Service quality complaint
- Privacy/data complaint
- Partner-related complaint
7. COMPLAINT REGISTRATION
- Receive complaint.
- Create complaint/ticket reference.
- Capture customer and transaction details as required.
- Categorise complaint.
- Assign responsible function.
- Acknowledge customer where applicable.
- Begin investigation.
8. CUSTOMER INFORMATION
Only information reasonably necessary to investigate and resolve the complaint shall be requested. Sensitive credentials such as passwords, PINs or OTPs shall not be requested except through approved secure processes where legally/technically necessary.
9. PRIORITY & SEVERITY
Complaints shall be prioritised based on customer impact, financial impact, fraud/security risk, regulatory sensitivity, service disruption and urgency.
- Critical – material fraud/security or significant customer impact
- High – substantial financial/service impact
- Medium – standard transaction/service issue
- Low – general information or minor service concern
10. INVESTIGATION
The responsible team shall review available transaction records, customer communications, product terms, system records, partner information and other relevant evidence.
11. PARTNER-RELATED COMPLAINTS
Where resolution depends on a PPI issuer, bank, payment processor, merchant or other partner, the case shall be routed through the documented partner escalation mechanism. RanaPay shall track the case until the responsibility is clearly transferred or the matter is resolved, subject to applicable arrangements.
12. FRAUD / UNAUTHORISED TRANSACTION COMPLAINTS
Complaints alleging fraud or unauthorised transactions shall be escalated under the Fraud Prevention & Transaction Monitoring Policy and Unauthorised Transaction Policy, as applicable.
13. REFUND / CHARGEBACK COMPLAINTS
Refund, cancellation and chargeback complaints shall be handled under Policy No. 08 and the relevant partner/payment process.
14. CUSTOMER COMMUNICATION
Customers shall receive clear and understandable updates appropriate to the case. Where a complaint cannot be accepted or resolved, the customer shall be informed of the reason and any available next step, subject to legal and security limitations.
15. RESOLUTION
Resolution shall be based on documented facts, applicable product terms, partner rules, applicable law and the customer's actual transaction circumstances. The resolution and supporting basis shall be recorded.
16. ESCALATION
- Complaint not resolved within applicable service timeline
- Material financial impact
- Fraud/security concern
- Repeated complaint
- Regulatory/legal notice
- Potential systemic issue
- Partner failure or delayed response
17. MANAGEMENT ESCALATION
Material or recurring grievances shall be escalated to Compliance and Management for review, root-cause assessment and corrective action.
18. ROOT-CAUSE ANALYSIS
Recurring or material complaints shall be analysed to identify process, product, technology, partner, communication or control weaknesses.
19. SERVICE LEVELS
Complaint handling timelines shall be defined based on complaint type, partner requirements, applicable law and operational capacity. Where a regulatory or partner-specific timeline applies, that timeline shall be followed.
20. COMPLAINT CLOSURE
- Confirm action taken.
- Record resolution.
- Communicate outcome where appropriate.
- Capture closure date.
- Record supporting evidence.
- Reopen/escalate if additional material information is received.
21. REOPENING
A closed complaint may be reopened where new material information is provided, the customer disputes the resolution or an internal review identifies a continuing issue.
22. DATA PROTECTION
Grievance records shall be protected and processed in accordance with applicable data-protection requirements and RanaPay's Data Protection, Privacy & Retention Policy.
23. RECORD KEEPING
- Complaint reference
- Date/time received
- Customer details as required
- Transaction reference
- Complaint category
- Assigned owner
- Partner communications
- Investigation notes
- Resolution
- Customer communication
- Closure/reopening history
24. MONITORING & REPORTING
- Complaint volumes
- Category trends
- Resolution time
- Pending/aged complaints
- Repeat complaints
- Partner-related complaints
- Fraud complaints
- Root causes
- Corrective actions
25. CUSTOMER SERVICE TRAINING
Relevant customer-support and operations personnel shall receive training on complaint registration, communication, escalation, privacy, fraud red flags and partner routing.
26. AUDIT & QUALITY REVIEW
Periodic sample reviews may be conducted to assess complaint classification, response quality, resolution accuracy, timelines, records and escalation.
27. NO RETALIATION
Customers shall not be disadvantaged merely for raising a genuine complaint. Appropriate controls shall be maintained against abusive, fraudulent or deliberately misleading complaints without restricting legitimate customer rights.
28. POLICY EXCEPTIONS
Exceptions shall be documented and approved by an authorised function. No exception may override mandatory legal or regulatory requirements.
29. RESPONSIBILITY MATRIX
| Function | Responsibility | Escalation |
|---|---|---|
| Customer Support | Receive, register, communicate and close complaints | Operations / Compliance |
| Operations | Investigate and resolve operational complaints | Operations Head |
| Compliance | Oversight, escalation and material grievances | Management |
| Fraud/Risk | Fraud/unauthorised transaction complaints | Compliance |
| Partner Management | Coordinate issuer/bank/merchant complaints | Management / Compliance |
| Technology | Technical issue investigation | Technology Head |
| Management | Material/repeated complaint oversight | Director / Authorised Management |
30. REVIEW & AMENDMENT
This Policy shall be reviewed at least annually and whenever there is a material change in applicable requirements, products, partner arrangements, customer channels or complaint trends.
31. APPROVAL
| Role | Name / Designation | Signature / Date |
|---|---|---|
| Prepared By | Customer Support / Operations / Compliance | |
| Reviewed By | Legal / Risk / Management | |
| Approved By | Director / Authorised Signatory |
