Skip to content

Account and support

Send a useful support report without exposing customer or payment secrets

A precise report helps distinguish a screen problem from a saved-state problem. Collect the smallest evidence that demonstrates the issue.

Source checked · 26 September 2026

What to do

  1. Write the screen name, action, actual result and expected result.
  2. Include the time, app version and relevant product, order or document reference.
  3. Redact customer contact details, full addresses and sensitive financial information from screenshots.
  4. Use the official support route and say whether a retry, refresh or state-changing action has already occurred.

What you should see

Support receives a reproducible description without needing your password, OTP or complete account export.

If it does not work

Never share secret keys, session tokens, bank credentials or UPI PINs. For an uncertain order, stock or payment update, pause repeated submissions and explain that the outcome is unknown. Do not let a troubleshooting step silently become a second business transaction.

For support, include the screen name, time, app version and a redacted error. Never share passwords, OTPs, payment PINs or secret keys.