Start with the exact symptom, preserve evidence, and test one change at a time.

Use symptom, evidence and one controlled test

Start with what you can observe. “Login broken” is too broad; “OTP arrives, but the screen returns to login after submission” is useful. Write the exact message, time, device, app or web address, and the last action that worked.

Before deleting data, changing credentials or reinstalling, capture the current state. Then perform one low-risk test. If the result changes, record it. If it does not, restore the setting where possible and move to the next step.

Site does not open, redirects or shows a different brand

1. Copy the full address before closing the screen.
2. Check whether the domain changed after a redirect.
3. Try a different trusted network only to separate DNS or connection problems.
4. Check device date/time and certificate warnings.
5. Do not enter credentials on a substitute domain merely because the design looks familiar.

If the destination changes repeatedly or a message pushes a new “working link,” treat identity as unresolved. A temporary outage does not justify sending a password to an unverified replacement.

OTP missing or verification delayed

Confirm the masked mobile number or email, signal, message blocking and device time. Wait before requesting another code; repeated attempts can trigger rate limits or make it difficult to tell which OTP is current. Never forward an OTP to someone claiming they will complete verification for you.

If the OTP message describes a different action, such as password reset or payment approval, stop. The wording can reveal that someone is attempting another operation.

Login loop after password or OTP

• Capture the error and address.
• Confirm cookies and JavaScript are not blocked for the destination.
• Close duplicate tabs and retry once.
• Check the app or browser for updates.
• Try the same account on one other trusted device without sharing the password.
• Do not keep resetting the password unless the system confirms the credential is wrong.

App will not install or update

Check storage, Android version, file completeness, Play Protect status and whether an older package with a different signature is installed. Do not turn off all security settings. If an update comes from a different source or requests new high-impact permissions, treat it as a fresh installation decision.

App crash, freeze or blank screen

Record the app version, Android version, available storage and the action that triggers the crash. Restart once, close overlays, update Android System WebView where relevant, and test without battery restriction only if needed. Clearing data may remove a session, so confirm you have safe recovery access first.

Payment left the bank but not the wallet

Use the transaction evidence sequence on the payment safety page. The key distinction is whether the bank status is pending, successful or reversed. Do not repeat the transfer while the first state remains unclear.

Withdrawal remains pending or is rejected

Save the request ID, amount, submission time, status history and exact reason. Check whether account ownership, limits or destination details are incomplete. Do not assume a delay proves fraud, but stop immediately if a personal contact demands another payment to release funds.

Account details changed unexpectedly

1. Use a clean device and end any remote-access session.
2. Change email and account passwords through trusted routes.
3. Review linked payment details, recovery information and active sessions.
4. Capture unfamiliar activity before it is removed.
5. Contact verified support with one case reference.
6. Contact the bank and cybercrime channel if money moved without approval.

Support asks for money, an OTP or screen control

End the interaction. A support case can be described using an account ID, error, timestamp and masked evidence. It should not require a UPI PIN, banking password or remote control. CERT-In specifically warns against installing remote-access apps on the instruction of unknown contacts; see its cyber-safety material.

Preserve evidence before a destructive fix

Clearing app data, resetting a phone, deleting messages or reinstalling can remove timestamps, version information and the exact error. Before a destructive step, capture the page address, app version, visible status, device time, recent transaction record and the contact route involved.

Keep the original files unchanged. Work from copies when redacting personal details. If the problem may involve malware, avoid transferring an unknown APK to another phone simply to “test” it. Record its name and hash where possible, then seek a safer analysis route.

What troubleshooting cannot establish

A successful login test cannot prove that a platform is financially reliable. A clean security scan cannot prove that every future app update is safe. A bank debit cannot prove that a platform credited the correct wallet. A support reply cannot prove the identity of the person unless the route itself is verified.

Keeping these boundaries separate prevents one positive sign from being stretched into a broader claim. Use each piece of evidence only for the fact it actually supports.

Escalation ladder