What to prepare before contacting support
- Account ID or masked identifier.
- Date and time of the event.
- Exact error or status wording.
- Amount, recipient and UTR for a payment issue.
- One clear screenshot with sensitive data hidden.
- Steps already attempted.
- A case or complaint reference, if one already exists.
What should never be included
Do not send OTPs, passwords, recovery codes, UPI PINs, card PINs, banking passwords, full identity bundles or an unlocked remote-control session. A screenshot may also expose notification previews, QR codes, account numbers and wallet balances; crop or mask them.
Keep one clean case timeline
Write down when the issue began, every status change, the route contacted and the reply received. Keep original screenshots unchanged and use redacted copies for sharing. A single timeline makes it easier for a bank, platform or authority to understand what happened.