<\/span>Step 1 – Before You Contact Support: The Pre-Ticket Checklist<\/span><\/h2>\nThe single biggest driver of faster resolution is walking in prepared. Most delays come from support asking for details you could have provided upfront. Gather these seven data points before you raise a ticket:<\/p>\n
\n- Transaction ID or Order ID<\/strong> – the unique reference tied to the payment attempt.<\/li>\n
- RRN or UPI Transaction Reference Number<\/strong> – the field banks use to trace funds.<\/li>\n
- Exact timestamp in IST<\/strong> – the precise time the transaction was attempted.<\/li>\n
- Payment method and amount<\/strong> – UPI, card, netbanking, or wallet, with exact value.<\/li>\n
- Error code or exact failure message<\/strong> – copy the precise text, such as PAYMENT_FAILED.<\/li>\n
- Customer’s bank or UPI handle suffix<\/strong> – the bank name or handle suffix like @okhdfcbank.<\/li>\n
- Steps already taken<\/strong> – settlement reports checked, refund initiated, status page reviewed.<\/li>\n<\/ol>\n
These India-specific fields are usually what support needs to trace a transaction. Razorpay’s Dashboard<\/a> surfaces transaction-level error codes and payment method details that you can copy directly into your support request, reducing back-and-forth.<\/p>\nThis preparation matters because 78% of service leaders say customers prefer self-service<\/a>.<\/p>\nPro-Tip:<\/strong> Before raising a ticket, check your gateway’s status page and transaction logs. Teams leaning on self-service and AI-assisted support resolve issues significantly faster, and your first ticket will be more actionable if you have ruled out known outages.<\/p><\/blockquote>\n