Status, identity, sister sites and cashout evidence

Cocoa Payments: Make the Account and Payer Match

Withdrawal friction often begins with a deposit that was accepted even though its payer name or wallet ownership did not match later verification rules. Deposit success is not approval of the full return path.

Open the verified play route

This page is a decision worksheet built around a specific search task. It separates observable records, first-party wording and unresolved claims so the conclusion can be checked again after a material change.

01

Map every named party

Compare casino account, identity document, card or bank holder, wallet or exchange owner and intended withdrawal recipient.

02

Read the closed-loop rule

Confirm whether funds must return to the original source and how joint accounts, expired cards or unavailable methods are handled.

03

Use the verified upload route

Submit proportionate evidence only inside the authenticated account. Never provide passwords, security codes, OTPs, seeds or remote access.

04

Preserve payment traces

Keep merchant descriptor, bank reference, wallet ID or TXID, currency, fees and final destination without exposing credentials.

Accepted deposit does not settle ownership

Ask for written pre-transaction guidance where names differ. Stop if an unsolicited message supplies a new recipient or asks for a release payment.

Questions this page resolves

Can a third-party card cause a withdrawal hold?

Yes, if account and payment ownership rules do not match.

Does crypto eliminate KYC?

No; ownership and verification can still apply.

What should never be uploaded?

Passwords, OTPs, full security codes, wallet seeds or private keys.