Razorpay vs Cashfree vs PayU vs Pine Labs: Merchant Support, Escalation and Dispute Handling

A payment gateway’s support process only matters on the day something breaks: a settlement that has not landed, a stuck refund, a chargeback with a respond-by date, or a ticket gone quiet for a week.

This guide compares what Razorpay, Cashfree, PayU and Pine Labs publish about merchant support: the channels each offers, who may raise a ticket, the escalation ladder each documents, the external route after that, and the dispute tools in each dashboard. Figures checked October 2026.

Everything below is a published standard term. None of it is a contracted SLA, and none of it is a measured resolution time. This comparison raised no test tickets with any provider, and it does not rank anyone by support speed.

Quick answer: All four providers publish a grievance ladder, but the paths differ. Razorpay, Cashfree and PayU publish named escalation levels with day-count targets plus dashboard dispute tools with deadlines. Razorpay documents a 24-hour acknowledgement, a 2-working-day first response and a 10-business-day maximum before Level 2. Cashfree publishes the tightest dispute deadlines, 3 calendar days for a chargeback, and the clearest RBI Ombudsman route. PayU publishes two policy documents that disagree. Pine Labs publishes the most phone access and the least online-gateway dispute documentation.

What should a merchant compare in payment gateway support?

This article covers the moment after something goes wrong, not the sales pitch. Six criteria run throughout:

1. Channels, and which product each covers.
2. Hours: staffed hours as opposed to “24×7” marketing copy.
3. Ticket routes: how a case is raised, who may raise it, whether it stays visible.
4. Escalation levels: acknowledgement, first response and resolution targets.
5. Grievance and nodal officer contacts, and the regulatory route after them.
6. Dashboard tracking: status, deadline and evidence upload for settlements, refunds and disputes.

Which product and legal entity does each support route belong to?

Support routes follow entities and products, not brands, and the wrong queue is why many first tickets go nowhere.

Razorpay names Razorpay Payments Private Limited as the RBI-authorised payment aggregator, with Razorpay Software Limited as the registered office entity; Banking+ and lending sit under other entities with separate queues and are outside this comparison. Cashfree’s entity is Cashfree Payments India Private Limited, Bengaluru. PayU’s is PayU Payments Private Limited, Gurugram, and its June 2026 escalation matrix separates Model 1, online and cross-border, from Model 2, QR, POS and terminals; this article follows Model 1.

Pine Labs is the most layered of the four. The office page names Pine Labs Limited, formerly Pine Labs Private Limited. Its contact-support page and refund policy are written around the Plutus in-store terminal business and plutus.support@pinelabs.com. The online gateway, branded Plural, has its own dashboard at pluralonline.com and its own address, pgsupport@pinelabs.com; prepaid complaints go to pineperks.in, a separate PPI service. This article covers Plural. Your contracting entity also decides which obligations apply, so read this alongside the RBI’s payment aggregator authorisation requirements.

How do you reach each provider, and who is allowed to raise a ticket?

None of the four publishes staffed human hours beyond Razorpay’s chat window: Cashfree’s 24/7 reference is a chatbot, Pine Labs says “7 days a week” without stating hours, and Razorpay’s “24×7 Support” wording appears only inside a Subscriptions product block.

The role restrictions matter more than they look. If whoever notices the problem at 9 p.m. is not an Owner or Admin on Razorpay, or lacks PayU’s Chargeback role, nothing gets raised that night, so map escalation duties onto your payment gateway dashboard roles and access controls in advance.

How do the published escalation ladders compare?

Conditional wording, “shall attempt” or “may need more time”, is kept below.

Razorpay

Razorpay’s published grievance ladder requires a reason for any extension at Level 2 and lists 30 days as the maximum for every mode of complaint. Two versions of the policy sit on the same page and give the Level 3 trigger differently, 20 business days in one and 10 in the other. The two pages disagree; ask Razorpay which version governs your account. No email address or phone number is published for either officer.

The dashboard documentation adds an Escalate Now button, shown when Razorpay misses its committed turnaround time on a ticket: the ticket moves to a priority queue and a representative calls within two hours. That is a callback commitment, not a resolution commitment, and the committed turnaround time is not published.

Cashfree

Both of Cashfree’s escalation levels are framed as an attempt to respond, not a commitment. Its grievance policy says refunds usually take 5 to 7 working days with a 120-day request cutoff, while its refunds guide says about 90 percent are processed instantly and can be initiated within six months. The two pages disagree; ask Cashfree which version governs your account.

PayU

PayU’s two documents do not match, and the difference is not cosmetic. The grievance policy page puts the Customer Care Head at Level 2 and the Nodal Officer at Level 3, with timelines of 6, 5 and 4 business days. The June 2026 escalation matrix reverses those two levels and changes the units, to 10, 5 and 5 calendar days with a 24 to 48 hour acknowledgement. Only the matrix names the RBI Ombudsman, and only it names Vikram Rao as Principal Nodal Officer with a phone number. The two pages disagree; ask PayU which version governs your account. Failed-transaction complaints follow the RBI turnaround-time circular instead of either document.

Pine Labs

Pine Labs does not publish escalation levels or day counts for its online gateway on the pages reviewed. Its grievance policy page and its RBI Ombudsman Scheme pages returned only navigation and metadata when fetched, so whatever levels, officer contacts and timelines they carry could not be verified at the time of writing. What is documented sits on the contact-support page: escalation to the Customer Service Head aims for “a resolution within 7 business days”, a Nodal Officer request can be raised if that fails, and the contact form is answered within 24 hours. Those officers’ contacts are not published, so get them in writing at onboarding.

Four merchant scenarios traced step by step

Each scenario is illustrative: it shows the documented route, not an observed outcome.

Scenario 1: settlement not received

Gather the settlement ID, the expected credit date, the UTR if shown, and the bank statement for that date.

Razorpay’s settlements FAQ puts domestic settlement at T+2 working days from capture, excluding second and fourth Saturdays, Sundays and bank holidays, with the expected date and UTR on the dashboard; Razorpay emails the registered address about blocked or failed settlements and asks for a reply there, otherwise raise a support request. Cashfree also defaults to T+2, with statuses including PENDING_WITH_BANK and FAILED; a failed settlement returns to the nodal account and is reattempted next cycle, so fix the reason shown, raise an issue via the support form, and match the UTR against your statement, because Cashfree receives no real-time bank confirmation. PayU does not publish settlement-hold guidance on the pages reviewed, so the route is help.payu.in and then the ladder. Plural shows settled and “Yet to be Settled” batches with UTR search; holds arise from verification, risk, compliance or documentation checks, and the documented step is the account manager or pgsupport@pinelabs.com.

Scenario 2: refund delayed

Gather the payment ID, the refund ID, the dashboard status, the ARN where shown, and the customer’s statement if the refund already reads successful.

Razorpay’s refunds FAQ puts normal refunds at 5 to 7 business days and asks merchants to raise a support request with the transaction ID and a bank statement from the debit date if nothing lands within 10 days. Cashfree publishes bank-side maximums of 5 working days for UPI, 7 for cards and 7 to 10 for netbanking and wallets; if a refund is successful but not received, give the customer the ARN for bank follow-up. PayU says refunds take between 5 and 21 days to reach the customer and emails the outcome, with follow-up through help.payu.in. Pine Labs documents refund tracking for Plural but does not publish a refund timeline for the online gateway on the pages reviewed; the 30-working-day language on pinelabs.com applies to POS hardware returns.

Scenario 3: disputed card transaction (chargeback)

Here the customer’s bank complaint and the merchant’s support route separate. The cardholder complains to the issuing bank, the bank raises the dispute through the network, and the gateway notifies the merchant. The merchant’s job is representment: the right evidence, on time, through the gateway. The grievance ladder does not apply, because the decision belongs to the bank.

Gather the invoice, timestamped proof of delivery or service, the courier AWB, customer communication, refund proof where applicable, and your checkout terms, matched to the reason code on the notice. If the reason codes are unfamiliar, start with our explainer on how chargebacks and UPI disputes work in India.

Razorpay notifies by email on creation plus webhooks. The merchant can contest a dispute from Transactions > Disputes, choose a full or partial amount, write an explanation and upload PDF, PNG or JPG evidence; the issuing bank’s verdict is described as 15 to 30 days. Accepting marks the dispute lost and deducts the amount, and for fraud-type cases the merchant refunds directly. Razorpay does not publish the length of the respond-by window.

Cashfree sends emails and webhooks on creation, update and closure, and its dashboard has Action Required, Under Review and Closed tabs with a deadline column. The published windows are 3 calendar days for a dispute, retrieval or chargeback, 1 day for some fraud alerts, 2 for pre-arbitration and 1 for arbitration; no response means the case goes to the customer. Cashfree debits the disputed amount on creation and returns it on a win.

PayU gives dashboard and email notice with the amount, the reason code and a Reply Before date; miss it and the acquirer closes the case in the customer’s favour. Contesting requires a reason, delivered, partially delivered, customer withdrawn or already refunded, with courier name, AWB, signed proof of delivery and invoice, up to 5 MB per upload in PDF, Word or image format. PayU may return an insufficient pack before forwarding it, later stages often take 45 to 60 days each, and its documentation does not describe a hold on the disputed amount.

Pine Labs’ Plural dashboard documentation lists chargebacks only as a settlement deduction. It does not publish a dispute workflow, a response deadline or an evidence-upload path for the online gateway on the pages reviewed, so confirm all three in writing before you sign.

Scenario 4: unresolved support ticket

Gather the ticket or reference number, the date lodged, prior responses, and the commitment that was missed.

On Razorpay, reply inside the ticket, use Escalate Now if the committed turnaround time is missed, then after 10 business days lodge at Level 2 and Level 3; only the last three open tickets are visible, so keep your own log. On Cashfree, after the 10-business-day support window, go to escalations@cashfree.com, then grievances@cashfree.com, then the RBI Ombudsman after 30 days. On PayU, use nodalofficer@payu.in and then carehead@payu.in per the June 2026 matrix, with the Ombudsman after 30 days. On Pine Labs, request the Customer Service Head, then a Nodal Officer; those contacts are not published, so ask your account manager.

Where does the RBI Ombudsman fit?

The RBI Integrated Ombudsman Scheme, 2021 applies after a complaint to the regulated entity has had no reply within 30 days or an unsatisfactory one. Cashfree and PayU both publish the route with the CMS portal address, and Cashfree adds the 14448 helpline and crpc@rbi.org.in. It sits after the internal ladder and does not replace the card-network dispute process, which runs on its own rules and deadlines.

Where should each problem go?

Which provider’s documentation suits which merchant?

On documentation rather than performance, Razorpay is the most explicit on the ticket side, with role limits, the Escalate Now trigger and a stated chat window, but publishes neither the respond-by window length nor an Ombudsman route. Cashfree publishes the tightest dispute deadlines and the clearest external route, with the softest internal wording. PayU publishes the most detailed evidence checklist and the only officer phone number, but its two policy documents disagree. Pine Labs publishes the most phone access, oriented to its in-store merchants, and the least online-gateway dispute documentation. That compares what each provider commits to paper, not how quickly any of them answers.

What to confirm before you sign

1. Get the legal entity and product named in writing, especially with Pine Labs, where Plural online, Plutus POS and Pine Perks are separate routes.
2. Ask for the current grievance policy as a dated document, and which version governs your account if the site carries two.
3. Record the channels with staffed human hours, separately from chatbot availability.
4. Confirm which dashboard roles can raise tickets and which can respond to disputes.
5. Confirm the length of the dispute response window and whether the disputed amount is debited on creation.
6. Ask whether your agreement includes a contracted SLA, and what the committed turnaround time is.

FAQs

1. Which payment gateway has the fastest support in India?

Not answerable from published material. The four publish targets such as a 2-working-day first response or a 7-business-day Customer Service Head aim, but these are policy targets, not measured results, and this comparison raised no test tickets. Treat any speed ranking without a stated methodology as unverified.

2. Can I escalate a chargeback through the gateway’s grievance officer?

No. A chargeback is decided by the issuing bank under card-network rules, and the gateway only relays your evidence by the respond-by date. The grievance ladder and nodal officer handle complaints about the gateway’s own service, a missed settlement or an unanswered ticket, not a bank’s dispute decision.

3. When can a merchant go to the RBI Ombudsman?

Cashfree and PayU publish the condition: after complaining to the provider and either getting no reply within 30 days or being dissatisfied, a complaint can be filed at cms.rbi.org.in under the Integrated Ombudsman Scheme, 2021. Razorpay’s grievance page does not mention the route, and Pine Labs does not publish a readable scheme page.

4. How long do I have to respond to a dispute?

Cashfree publishes 3 calendar days for a dispute, retrieval or chargeback, 2 for pre-arbitration and 1 for arbitration. Razorpay shows a respond-by date and PayU a Reply Before date on each case, but neither publishes the window length. Pine Labs does not document a dispute deadline for its online gateway.

5. Are these timelines contractual?

No. They are standard published terms, and most carry conditional wording such as “shall attempt” or “may need more time”. A contracted SLA, where one exists, sits in the merchant agreement and is not published. Ask for it in writing before you sign.