Accessible redressal
A simple, transparent and digitally encrypted way to register a complaint, open to every user on the platform.
The same sequence runs for a five-rupee recharge and a fraud report. What changes is the priority it enters at, and who picks it up.
Through the form here, email, the helpline or WhatsApp — with the transaction details and proof attached. The more complete the first message, the fewer rounds it takes.
The intake system records it and issues a Complaint ID straight away. Quote that ID in every follow-up and you come back to the same file rather than starting again.
Category, service involved, the money in question, priority, and whether the proof is complete. If something is missing you hear about it here, not three days later.
Server metrics, the request and response payloads, API gateway codes, Bharat Connect network logs and the banking clearing receipts — the record of what actually happened, not what either side remembers.
Root cause identified, then a written resolution: what was done, what changed on your ledger, and what refund was settled if one was owed.
A file closes only when every adjustment has cleared on the external networks and nothing is outstanding. A closed case can still be reopened if new facts come up.
The framework is engineered around these mandates, and every part of the process below serves one of them.
A simple, transparent and digitally encrypted way to register a complaint, open to every user on the platform.
Every registered grievance evaluated systematically, investigated alongside partner banks, and resolved equitably.
A permanent, fully auditable digital trail of complaints, kept so operational quality and system health can be measured.
Seasonal complaint trends analysed to remove technical bottlenecks, application crashes and gateway routing latency.
These carry specific meanings throughout the policy, so it is worth knowing what each one covers.
Priority is set from the facts of the ticket, not from how loudly it is raised. Anything touching money or account safety goes high or critical on its own.
General information requests, feedback, product suggestions, interface and language settings.
A slow mobile top-up, a DTH renewal not reflecting, a cashback dispute, a gift card that did not arrive.
Account debited with a failed transaction, duplicate clearing, a pending refund, a KYC block, OTP not arriving.
Suspected fraud, unauthorised access, device hijacking, large-scale exposure or a gateway outage. These skip the queue entirely.
Acknowledgment is within 24 business hours for every category. Resolution depends on who else is in the loop — where a bank, a biller or a carrier has to answer, we say so rather than promise a date we do not control.
Different desks answer at different speeds. Use the one that suits how urgent it is.
Target windows are suspended during events outside our control — a natural disaster, a country-wide internet or power outage, a change in banking law, a gateway failure or a security incident at a partner. In those cases the clock extends automatically, and we say so on the ticket.
Filing a complaint also does not by itself create a right to a refund. Outcomes follow the transaction records, the evidence, the bank's response and the regulator's rules.
Escalating does not restart the case. Quote the same Complaint ID and the next level opens the file you already have.
Where every complaint starts. Most are settled here, and this is the level with the transaction tools to hand.
If Level 1 has not resolved it, or the answer does not address what you raised. The officer reviews the file independently of the desk that handled it.
Unresolved high-impact disputes go to the management board for a final internal decision, checked against the regulations that apply.
Industry-standard cookies, web beacons and tracking pixels help recognise your browser on a future visit. The app asks for device permissions only where a feature needs them.
Individuals, registered users, B2B merchants and enterprise partners — the same policy, the same ladder.
Each ticket is stamped with one of these on arrival. It decides which desk sees it first.
A recharge dispute is settled against operator clearing archives; a KYC block is settled against RBI master directions. The route a ticket takes depends on where the truth lives.
Covers network failures, pending timeouts, incorrect circle routing and duplicate card debits. Your parameters are matched against API logs and operator clearing archives, and delivery is confirmed before any balance adjustment is authorised.
Electricity, water, broadband and gas are governed by NPCI guidelines. Where a payment succeeds here but is not updated in the biller's ledger, we file an official dispute directly into the central Bharat Connect infrastructure, creating a legal audit trail.
Anpay is a secure booking interface between you and the carrier. Ticket changes, flight cancellations, lodging adjustments and fare refunds follow the airline, hotel or bus operator's terms, and carrier cancellation penalties apply.
Investigated with the issuing brand network. Where an asset is confirmed unactivated, or delayed by a system timeout, we coordinate a code re-generation or a complete token reversal, whichever the case calls for.
Where a failure is verified, liquidity is pushed back to the originating card, UPI handle or bank node. We track missing funds with the gateways, but the speed belongs to the destination clearing house.
Onboarding problems, PAN mismatches and document upload blocks are assessed under RBI master directions. Where Aadhaar verification is legally permitted, encrypted masking gates replace raw numbers with placeholders across our logs.
Unauthorised access, account compromise and phishing reports go to incident control immediately: temporary account locks, Anpay Coin movement halted, login telemetry checked, and logs shared with cyber law enforcement where required.
Through the investigation you are updated by automated alerts over corporate email, verified SMS, WhatsApp and push notifications. In return we ask you to keep the channel open and your tracking details accurate.
A complaint moves to closed only when all of these are true. Until then it stays open, whatever its age.
The helpdesk or the system has supplied the complete information the complaint was about.
Server, gateway and operator logs have all been examined — not sampled, and not left half-read.
Database alignments, ledger adjustments or account recoveries have actually been carried out.
Eligible refunds are pushed to the original source instrument, in line with the Refund Policy, before the file can close.
The resolution and the root cause are sent to you over a verified channel — email, SMS, WhatsApp or a push notification.
You confirm you are satisfied, or a reasonable request for data goes unanswered within the operational window, or the ticket duplicates one already open.
If fresh facts turn up, a hidden failure surfaces, or a separate situation arises later, you can register a new grievance. Closure is administrative — it does not forfeit anything.
The grievance officer bureau reports here. Level 3 reviews are signed off at this level.
"A complaints process is worth something only if it can rule against us. Ours has to, and does."
Most payment problems are somebody's bad day made worse. The point of this policy is that the person handling it has the logs to see what actually happened, a deadline to work to, and a named person above them if they get it wrong.
Every SLA on this page is a target we measure ourselves against monthly, alongside complaint volumes and platform error rates — because a rising ticket count is a product problem before it is a support problem.
These are the details the engineers need to pull the right logs. Sending them all at once is the single biggest thing that shortens a case.
Quote the Complaint ID in every follow-up. If Level 1 does not resolve it, send the same ID to info@anpay.in and the grievance officer opens this file rather than a new one.
The clauses that define the limits of the framework, stated as plainly as their wording allows.
Nothing here guarantees that filing a ticket results in a refund, reversal, credit or service adjustment. Each outcome depends on the transaction records, the evidence, the banking node's response and the regulator's rules. To the extent the law allows, we disclaim liability for financial disruption caused by server downtime, clearing bank errors or third-party network outages outside our control.
Target SLAs are suspended where delays are caused by events beyond reasonable control: natural disasters, flooding, fire, earthquake, civic disturbance, military action, changes in banking law, country-wide internet outages, power grid failure, gateway timeouts or a security incident at a partner. Resolution timelines extend automatically during such events.
Anpay may modify or amend sections of this policy at any time to stay aligned with changing national laws, banking rules or new product features. The latest active version is always available on the official web domain and in the app dashboard. Continued use of our payment systems implies acceptance of the updated terms.
This policy is interpreted in alignment with the laws of the Republic of India. Any unresolved dispute, legal disagreement or court action arising out of the complaint process shall be filed exclusively before the competent courts at Dakshin Dinajpur, West Bengal, India, to the exclusion of all other benches.
Read alongside the Terms & Conditions, Privacy Policy, Refund Policy and Cancellation Policy, this document is the complete grievance handling agreement between the user and Anpay. If any clause is held invalid or unenforceable by a court, that portion is severed and the rest continues in full force.
By maintaining an active account or using the payment features, you confirm that you have read, understood and accepted the terms of this policy framework. Filing a grievance does not by itself create a right to a refund — reversals are approved only where an internal system audit confirms a permanent transaction failure.
Suspected fraud or unauthorised access does not wait for a form. Call the helpline and it goes straight to the incident desk.
Grievance Redressal Policy · effective 5 July 2026 · the current version always lives here and in the app