LolaJack Verification: Documents, Review Time, and Status Checks

Verification can begin before a payout request is submitted, so the review should not be read as a withdrawal-only step. The account may ask for proof of identity, proof of residence, proof of payment-method ownership, and transaction history, and the request should be answered within 30 days.
The timing also has two layers. Practical guidance points to around 24-48 hours after the full document set is received, while the formal terms allow up to 10 days once the request has been answered in full.
The fastest useful distinction is between a file that was uploaded and a review that was actually completed. If the account already opens normally, first access your account and check whether the review prompt or the current review state explains what is still missing.
What Verification Is and When It Starts
Verification is an account check, not only a payout step. The review can start before any withdrawal is placed, which is why some users see a document request even when the immediate question is still about access, bonus use, or account readiness.
The practical consequence is simple: a payout can stay blocked if the account review is still open. Ignoring the request is riskier than delaying it, because payments may be withheld and the account can be suspended or closed if the requested documents are not provided within the stated window.
- Do not wait for a failed payout before reading a review request.
- Treat a document prompt as an account condition, not as a cosmetic message.
- Use the current review state as the first checkpoint before repeating other actions.
- Count the 30-day response window from the request itself, not from the next login attempt.
Required Documents for Verification
The request can cover four different proof groups, and each of them answers a different question. Proof of identity confirms who owns the account, proof of residence confirms the current address, proof of payment-method ownership confirms control over the route used, and transaction history supports the money trail when another layer is needed.
One proof group does not replace another when the request is broader. Sending identity proof alone does not complete the review if the account also asked for address confirmation, payment ownership, or transaction history.
- Proof of identity
- Proof of residence
- Proof of payment-method ownership
- Transaction history
How the Verification Process Works
The normal flow is submission first, review second, result third. The account receives the files, the review begins after the full set is in place, and only then does the state move toward a usable outcome.
This is why a partial upload often creates confusion. A user may send one file and expect movement, while the account is still waiting for another proof group before the real review can begin.
- Read the request carefully and identify every proof group it mentions.
- Upload the full document set instead of one file at a time when the request is broader.
- Wait for the review state to change after the full set is received.
- Recheck the account if the state does not move within the expected window.
Verification Time and Delays
The practical estimate is around 24-48 hours after the full set has been received in full, but the formal allowance is longer. Terms can extend the review up to 10 days once the request has been answered completely, so a delay is not always a sign that something went wrong.
The most common reason for longer handling is not the review itself but the file set behind it. Missing documents, unclear images, the wrong proof category, or another unresolved account condition can all keep the review from reaching a final result.
Verification Status and Where to Check
The most useful place to read progress is the account itself, not the original upload attempt. After successful submission, the account may show the review state as (Under review), and a pop-up can also appear when verification is required.
| Status | What It Usually Means | Next Check |
|---|---|---|
| Under review | The files were received and the review is still active | Wait within the stated window and recheck the document set |
| No movement after upload | The full set may still be incomplete or unclear | Review the requested proof groups again |
| Returned or rejected | One or more files failed the review criteria | Correct the failed item before resubmitting |
The table helps separate waiting from a real document issue. To understand the effect on money actions, review payout conditions before sending a request that the account may not yet be ready to process.
Common Reasons for Rejection
Most failed reviews come from file quality or a mismatch between the request and the upload. An ID can fail because it is expired, address proof can fail because it is too old, a modified file can be rejected, and a low-quality image can stop the review even when the correct document type was chosen.
The other common problem is category mismatch. Identity proof does not replace address proof, and payment ownership does not replace transaction history when the request asked for both.
- Expired identity document
- Outdated address proof
- Modified or non-original file
- Unreadable image or incomplete document
- Wrong proof group submitted
What to Fix After Rejection
The best response is correction, not repetition. Re-uploading the same weak file usually adds another delay instead of moving the review forward, so the safer path is to identify the exact failure point before sending anything again.
- Check whether the rejected file was expired, outdated, unclear, or incomplete.
- Confirm that the replacement belongs to the proof group that was actually requested.
- Upload the corrected version as part of the full required set when the review asked for more than one item.
- Recheck the review state after the corrected submission is complete.
What to Send to Support
Support becomes useful when the local checks are finished and the review still does not move, or when the account keeps rejecting files without making the reason clear. A short message is rarely enough on its own, because the support team still needs the account identity and the timeline behind the issue.
If documents are repeatedly rejected, use contact support with the core account details and a clear description of what was already uploaded and when.
- Registered username
- Full registered name
- Relevant dates and times
- Which proof groups were requested
- Which files were uploaded and what happened after that
Verification and Withdrawals
The connection between review and payout is direct. A payout request can stay blocked while verification is still open, which is why the review state matters before money leaves the account.
This also explains why a successful login or a funded balance does not guarantee payout readiness. The account can be active for some actions while still waiting on identity, address, payment ownership, or transaction-history checks.
FAQ
What documents are required for verification?
The request can include proof of identity, proof of residence, proof of payment-method ownership, and transaction history. The exact mix depends on what the account asked for, so one document does not automatically finish the review.
How long does verification take?
Practical guidance points to around 24-48 hours after the full document set is received, while the formal terms allow up to 10 days once the request has been answered completely.
Why was verification rejected?
The most common reasons are expired documents, outdated address proof, modified files, unreadable images, or the wrong proof category. A rejection usually means the review needs correction, not just another identical upload.
Where can the review status be checked?
The status should be checked inside the account after submission. A pop-up can appear when verification is required, and the review state may show as Under review after the files are received.
Can a payout request be made before verification?
Verification can begin before a payout request, and an unfinished review can still block withdrawals. That is why payout readiness and account access are not always the same thing.
What should be sent to support?
Send the registered username, full registered name, relevant dates or times, the proof groups that were requested, and a clear note about what was uploaded and what happened next. That gives support a usable case instead of a generic delay report.
