Open the correct account page
Use the LN7 navigation or this guide library to reach the current device compatibility page. Avoid old bookmarks or copied links if the screen looks different from what your account shows.
LN7 PRACTICAL GUIDE
Check Whether Your Phone Is Ready for LN7
A phone can install an app and still struggle to run it well, so compatibility is more than the download button.
This LN7 guide stays focused on device compatibility, especially Android version, browser support, storage, memory and network requirements. On a phone, read the current status first, then work through OS version, free storage, available memory and current browser version and whether your device vendor blocks background activity or unknown-source installs before changing anything unrelated.
18+ only. Availability and eligibility can vary by location.
FocusAndroid version, browser support, storage, memory and network requirements.
Check firstOS version, free storage, available memory and current browser version.
KeepThe model number and OS version if support needs to reproduce the issue.
BEFORE YOU START
What to confirm before dealing with device compatibility
A phone can install an app and still struggle to run it well, so compatibility is more than the download button.
LN7 account actions are easier to troubleshoot when the basic facts are written down first. In particular, review OS version, free storage, available memory and current browser version. Then make sure you understand whether your device vendor blocks background activity or unknown-source installs. Those two checks prevent many avoidable retries.
- Read the current device compatibility status and any timer, limit or validation message attached to it.
- Confirm OS version, free storage, available memory and current browser version before you submit or retry the action.
- Review whether your device vendor blocks background activity or unknown-source installs if the first check looks correct but the result still does not move.
- Save the model number and OS version if support needs to reproduce the issue until the device compatibility status reaches a clear final state.
INDIA CHECK
What matters on an Indian mobile account
For device compatibility on an Indian mobile account, separate the account-side check from anything handled by your SIM, identity record or payment provider. Begin with OS version, free storage, available memory and current browser version; after that, verify whether your device vendor blocks background activity or unknown-source installs. That sequence makes it easier to tell whether the next step belongs inside LN7 or outside it.
That does not mean every device compatibility question needs KYC or payment work. It means you should check the part actually mentioned by the status message. If the screen only asks for a profile update, do that first instead of changing unrelated settings.
Keep the details used for device compatibility consistent while the status is being processed. If LN7 requests identity confirmation, match the spelling on the accepted document to the account. Keep the model number and OS version if support needs to reproduce the issue; it is more useful for a follow-up than changing several profile or payment fields at once.
STEP BY STEP
A five-step way to handle device compatibility
Check the details on screen
Before tapping confirm, review OS version, free storage, available memory and current browser version. A mismatch here can make a normal rule look like a technical failure.
Make one change or request
Complete one device compatibility action at a time. Keep the page open long enough to see whether LN7 returns a confirmation, status change or validation message.
Wait for the status to update
Do not repeat the same request every few seconds. Check whether your device vendor blocks background activity or unknown-source installs, refresh once, and allow the account status to catch up before submitting again.
Escalate with useful evidence
If the issue remains, contact support with the model number and OS version if support needs to reproduce the issue. Never send a password, OTP or full payment credential in a support message.
WHEN IT DOES NOT MATCH
Common device compatibility problems and the next useful check
The option is missing
The device compatibility control is not shown, or it is present but cannot be selected.
Recheck OS version, free storage, available memory and current browser version, then read any eligibility, timing or verification notice attached to the account.
The status is not moving
The device compatibility request remains in the same state after a normal refresh.
Review whether your device vendor blocks background activity or unknown-source installs. Avoid duplicate submissions and keep the model number and OS version if support needs to reproduce the issue while the status is pending.
The result looks inconsistent
The device compatibility result does not match the account history, balance or screen you expected.
Compare the before-and-after state, note the time and include the model number and OS version if support needs to reproduce the issue in one concise support request.
GOOD RECORDS HELP
Keep the details that explain what happened
For device compatibility, the most useful record is usually the simplest one: the time, the account status, the exact message and the model number and OS version if support needs to reproduce the issue. This gives support enough context without exposing private credentials.
If device compatibility changes a balance, reward, score or payment state, note the value before the action and again after the final status appears. Pair that comparison with the model number and OS version if support needs to reproduce the issue. A dated, topic-specific record gives support something concrete to trace instead of a vague report that the feature failed.
Do not send
- Passwords or one-time passwords.
- UPI PINs, card PINs or full card numbers.
- Unredacted identity documents through unofficial chat channels.
- Several duplicate tickets for the same issue.
COMMON QUESTIONS
Questions people usually ask
Start with the current account screen and verify OS version, free storage, available memory and current browser version. That usually explains whether you are looking at an eligibility rule, an account-review step or a genuine error.
One retry after checking the message is reasonable, but repeated submissions can make the history harder to read. Check whether your device vendor blocks background activity or unknown-source installs and wait for the status to settle first.
Send the error text, time, device or app version, and the model number and OS version if support needs to reproduce the issue. Do not share passwords, OTPs, PINs or full card credentials.