UPI Refund and Grievance Escalation Checklist for Merchants

Refund and grievance cases require two separate decisions: what happened to the payment, and what commercial remedy the merchant owes under its policy. Do not promise a bank outcome before the transaction is matched to authenticated evidence.

NPCI’s UPI FAQ directs merchants to raise transaction grievances with their acquiring bank and follow bank-defined refund procedures. Exact channels, documents, and timing can vary by provider and case. Source: NPCI UPI FAQ.

Classify Before Escalating

Choose one primary category:

Category	Initial question
Customer debited, merchant order pending	Is there authenticated success evidence?
Merchant received payment, order cancelled	Does merchant refund policy apply?
Amount mismatch	Which amount is verified and which was expected?
Duplicate payment	Are there two distinct successful payment records?
Refund initiated, outcome pending	Is there a provider refund reference and current state?
Unknown payment reference	Can the payment be mapped without unsafe guessing?
Customer-only claim	What official evidence is still missing?

Classification prevents a support team from treating a delayed confirmation, duplicate payment, and commercial cancellation as the same refund problem.

Collect Minimum Evidence

Create a tenant-scoped case containing:

• Merchant order reference
• Expected amount and order status
• Approximate payment time
• Gateway order and event references
• Verified payment amount and state
• Provider or UTR reference when available to authorized staff
• Refund reference and state, if already initiated
• Customer communication history
• Case owner and next follow-up time

Do not request a UPI PIN, OTP, password, remote device access, complete card or bank credentials, or provider login. Do not match by amount and time alone; common values are ambiguous. Use the UTR matching guide for the evidence order.

Follow the Authorized Channel

Use the connected merchant provider or acquiring bank’s official support and grievance process. Record the provider case ID, submission time, evidence supplied, expected next update, and accountable merchant owner.

VyaparGateway can help the merchant identify order, event, and delivery evidence inside its product boundary, but it should not be presented as the bank or as the authority that decides provider refund outcomes. Keep product support and bank/provider escalation responsibilities explicit.

If two verified payments relate to one purchase, stop duplicate fulfilment and route the financial decision through merchant policy and the authorized provider process. If no authenticated payment exists, keep the case unresolved rather than manufacturing a paid state to initiate a refund.

Communicate Without Overpromising

Tell the customer:

1. The case reference.
2. What the merchant has verified so far.
3. Which authorized party owns the next check.
4. What the customer should avoid, such as paying again while the result is uncertain.
5. When the merchant will provide the next update.

Do not guarantee a completion date unless the responsible provider process supports it. Avoid phrases such as “the money is definitely lost” or “refund completed” when evidence shows only that a request was initiated.

Track to Closure

Maintain opening date, aging, owner, latest evidence, provider status, customer update, and next action. Escalate cases that exceed your internal follow-up threshold even when an external provider owns the transaction review.

Close only when payment, order, refund, and customer communication states agree—or when an explicitly documented external outcome and merchant decision resolve the case. Review recurring categories every month. Repeated paid-but-pending cases need an engineering fix; repeated unclear cancellation cases need a policy or checkout-copy fix.

This checklist is operational guidance, not legal, banking, tax, or provider-specific advice. Merchant agreements and official acquiring-bank procedures govern each actual refund or grievance.

Use aging bands to prevent quiet abandonment:

Age band	Merchant control
New	Validate order and payment evidence
Awaiting provider	Confirm case ID, owner, and next review time
Internal threshold exceeded	Escalate through the documented provider channel
Customer update due	Communicate known state even when outcome is pending
Resolved	Verify payment, refund, order, and communication records agree

Thresholds should come from merchant policy and the responsible provider process, not from an invented universal promise. Report overdue cases by owner and category so recurring provider or integration issues become visible.