We keep this generic: codes can be email/SMS/app-based. We don’t claim Megapari’s exact OTP mechanism unless you see it in your flow.
Invalid code loop
Invalid codes are often caused by time drift, delays, or rate limits, as the codes can be time-sensitive and multiple requests can throttle.
Example: “Invalid code” even when you typed quickly after multiple resends.
Action plan:
- Stop resending
- Wait 2–5 minutes
- Ensure device date/time is Automatic
- Retry once and screenshot the result
Code not Arriving
Delivery delays happen (email latency / network / carrier), because not every delay means the account is compromised.
Example: The code arrives late, but you requested a new one and now both are confusing.
Action plan: request once → wait → check spam/promotions → switch network once → capture evidence.
If you see X, do Y
- If you see “Too many attempts / try later” → stop attempts; prepare Evidence Pack; contact support
- If you see “Wrong email/ID” repeatedly → confirm you used “E-mail or ID” correctly (Table 1)
- If the login page is missing “E-mail or ID” / “Forgot password” UI → stop and re-verify route.
Account locked / too many attempts
Lock messages are security events, not “try again” events, as more retries can extend locks or trigger extra checks.
Example: You keep retrying and the lock persists.
Action plan: stop attempts, capture screenshots, escalate with a clean ticket.