IN999 problem library
IN999 Blog
Focused troubleshooting for the issues that usually appear after login, deposits, withdrawals and reward-code use.
Updated 5 Sep 2026 · IN999 screenshots reviewed
Focused troubleshooting for the issues that usually appear after login, deposits, withdrawals and reward-code use.
Most account problems become easier when the symptom is assigned to the right layer. A login failure is usually about the route, credentials, verification or app state. A deposit issue is about the payment reference and wallet credit. A withdrawal issue is about the destination, request status and receiving account. A gift-code issue is about campaign validity, eligibility and reward history.
Start with the exact symptom instead of changing several things at once. Preserve the first error message, time and relevant reference before reinstalling the app, resubmitting a payment or creating another account.
Blank screen, old route, wrong password, verification delay or session loop.
Open login problem →Pending wallet credit, UTR mismatch, duplicate payment or reversal.
Open deposit problem →Pending request, bank mismatch, failed status or delayed receiving credit.
Open withdrawal problem →Invalid, expired, already-used or account-limited gift code.
Open gift-code problem →Temporary error messages, payment references and route redirects can change after a refresh. Capture only what is necessary and mask personal details. Never include a password, OTP, UPI PIN or full card/bank information in a screenshot.
The fastest route is usually the one that preserves the original evidence. A password problem, payment problem and reward-code problem can all feel like “IN999 not working,” but each needs a different reference and a different first action.
Preserve the exact error, current route and registered mobile context.
Login problem details →Keep UTR/reference, amount, time and wallet status together.
Deposit problem details →Compare request status with the receiving bank or wallet.
Withdrawal problem details →Check exact characters, campaign state, eligibility and reward history.
Gift-code problem details →For an account problem, capture the error and time. For a payment problem, record the transaction reference and amount. For a reward problem, record the exact code result. Mask account IDs, bank details and phone numbers before sharing a screenshot, and never include a password, OTP or payment PIN.
If you reinstall the app, change networks, reset the password and create another account at the same time, the original symptom disappears and the cause becomes harder to isolate. Make one controlled change, observe the result, then move to the next step.
Separate password, network, app and old-route problems.
DepositPayment reference, duplicate payment and wallet-credit checks.
WithdrawalLinked bank details, status, processing and safe escalation.
RewardsExpired, used, mistyped and account-limited codes.
Separate password, verification, route and account-state problems.
Open login issue →Use UTR/reference, amount and wallet state to trace one payment.
Open deposit issue →Track order/reference, status and destination details without duplicating requests.
Open withdrawal issue →Check code state, account eligibility and reward history separately.
Open gift-code issue →A login error, pending deposit, delayed withdrawal and rejected gift code can look similar when the only visible result is “not working.” Treat them as separate account layers. Access issues belong to credentials, verification and route state; wallet issues belong to transaction references and final status; reward issues belong to code state and eligibility.
Do not create duplicate accounts or repeat payments just to test whether an issue has cleared. Confirm the original account or transaction first, then take the next action only after its final state is visible.
| Problem | Evidence to keep | Do not start with |
|---|---|---|
| Login failure | Error text, route, registered mobile context | Creating another account |
| Deposit pending | UTR/reference, amount, time, wallet state | Repeating the payment immediately |
| Withdrawal pending | Withdrawal reference, destination, receiving status | Submitting duplicate requests |
| Gift code rejected | Exact code result, campaign context, reward history | Trying random generated codes |
Before opening a support case, confirm that the symptom still exists and gather the smallest evidence set that proves it. A clean timeline is more useful than many screenshots. Mask personal details and never share passwords, OTPs or payment PINs.
If one controlled step resolves the problem, stop there. Do not continue changing account settings simply because a checklist contains more steps. The purpose of the diagnostic flow is to isolate the failing layer with the least disruption to the account.
Use the current access buttons, then keep your registered mobile number and password private.