Separate a Rocket Returned Request From Verification Approval
A live complaint describes requests returning to the account before verification finished. A returned balance is not a completed payout. Keep the request, document review and later resubmission as distinct events so the chronology survives even if funds become playable again.
Open Rocket and review verification statusFreeze the original request
Record payout ID, amount, method, creation time, status and balance movement when it returned. Do not delete the row or treat the returned amount as new winnings.
Index verification decisions
List requested evidence, upload acknowledgement, rejection reason and final approval. An upload receipt or empty panel does not establish a compliance decision.
Protect the returned funds
Pause play while the cashout route is unresolved. If account controls are available, use an authenticated cooling-off or limit setting rather than accepting a new promotional wager.
Create a linked resubmission
After the issue is resolved, give the new request its own ID and reference the returned one. Ask whether the pending period and account limit restart, then trace dispatch to the destination.
Frequently asked questions
What begins the rocket verification and returned withdrawal timeline?
Record payout ID, amount, method, creation time, status and balance movement when it returned. Do not delete the row or treat the returned amount as new winnings.
What is the second check for rocket verification refund loop?
List requested evidence, upload acknowledgement, rejection reason and final approval. An upload receipt or empty panel does not establish a compliance decision.
How is this separate a rocket returned request from verification approval closed?
After the issue is resolved, give the new request its own ID and reference the returned one. Ask whether the pending period and account limit restart, then trace dispatch to the destination.
Last reviewed: 3 August 2026