Put RocketPlay KYC Evidence in the Order the Withdrawal Review Uses

Freeze the account facts before uploading

Compare the legal name, birth date, residential address, email and payment owner with the profile. If the profile is wrong, request a documented correction; altering a document to fit an incorrect field creates a second problem.

Save the request ID, balance type and bonus state before verification starts. This baseline shows whether the withdrawal existed before any document decision.

• Profile identity
• Residential address
• Payment owner
• Withdrawal ID

Classify the requested evidence

Ask whether the outstanding item is identity, address, payment ownership, source of funds or an account-security check. Record accepted document types, age limits, image requirements and the secure upload location.

Do not send a full archive of unrelated personal files. A targeted submission reduces unnecessary exposure and makes a rejection reason easier to isolate.

• Evidence category
• Accepted alternative
• File rule
• Review deadline

Protect sensitive fields

Follow the live masking instruction for cards and bank evidence. Never expose a PIN, CVV, online-banking password, recovery phrase or one-time authentication code, even if a person claiming to be support asks for it.

Upload from the signed-in site rather than a social-message link. Preserve the confirmation screen, filename category and submission time without storing unnecessary document copies in shared locations.

• Allowed masking
• Secure upload
• Submission receipt
• No secret codes

Close the review loop

Wait for the stated review window and reply in the existing case. If rejected, request the exact failed field and one accepted alternative instead of repeatedly resending the same image.

After approval, confirm that the original withdrawal returned to processing and record its new stage. Verification approval and payment release are separate events, so retain both timestamps.

RocketPlay payment and status questions