Quick answer: Common checks cover identity and age, address, ownership of the payment method and sometimes source of funds or wealth. Use current, readable documents through the authenticated portal. Redact unrelated data only where the instructions permit; never fabricate or alter evidence.

CheckPossible evidenceProtect
Identity and ageGovernment-issued IDDocument number where masking is permitted
AddressRecent statement or official letterUnrelated transactions
Bank ownershipAccount letter or redacted statementBalances and unrelated entries
Card ownershipMasked card evidenceCVV, full number, PIN
Source of fundsPayslip, sale or account history as requestedSend only via secure channel

Why checks can occur at withdrawal

A deposit may use automated authorisation and not complete all account checks. Regulated providers must manage age, identity, fraud and money-laundering risk. Best practice is early verification, but later triggers can still occur.

Ask for a complete request

A useful request states the document type, acceptable date, required visible fields, file format and secure upload route. If the request is vague, ask for one consolidated list before uploading.

Ask for the outstanding requirements as a list tied to the current case. For each item, request the document type, the relevant fields, the acceptable age or format where specified and the secure submission route. Separate an identity check from a payment-ownership check and from a question about a particular transaction. This makes it possible to see whether one document answers several requirements or whether a genuinely different record is needed.

Keep the provider's wording rather than rewriting it into a broader demand. If the instructions conflict, ask which version supersedes the other before sending more information. Record each completed submission and its confirmation. If another agent starts the checklist again, provide the existing case number and ask which item remains incomplete. A complete request does not guarantee approval, but it reduces unnecessary disclosure and gives both sides a common record of what has been asked, supplied and still needs a decision.

Security boundaries

No legitimate verification needs your banking password, card PIN, CVV or one-time login code. Beware of calls or messages asking you to approve a login so that a withdrawal can be “released”.

Authenticate the recipient before uploading sensitive evidence. A request that mentions your withdrawal amount can still be untrustworthy if it arrives through an unfamiliar channel. Open the account independently and confirm the request there or through established support. Do not provide banking passwords, authentication codes or remote access to a device as part of a document check. Those actions grant control rather than demonstrate the facts a reviewer needs.

Ask whether unrelated statement entries may be masked and which identity-document fields must remain visible. Do not make unapproved edits that change genuine information. Keep originals privately and submit only the version the provider has agreed it can review. After the case, remove unnecessary copies from shared folders and retain a secure record of what was disclosed. If you believe documents reached the wrong recipient, contact the relevant institution's security or privacy channel promptly with the facts. Continuing to send information to the same questionable route will not resolve the exposure.

Timing record

Save the request time, upload receipt and acknowledgement. If a file is rejected, request the precise reason—expired, cropped, unreadable, name mismatch or missing page—before replacing it.

How to use this page

Use the table to identify the observable state first, then follow the five-step check in order. Keep amounts in their original currency and write down timestamps with the time zone. Where a rule or product behaviour is date-sensitive, use the primary sources at the end of this page rather than a search snippet. This page is not a recommendation to gamble or a promise that a payment will succeed. It is a framework for asking a precise question, protecting sensitive data and deciding when a stated deadline has actually passed.

A practical five-step check

  1. Identify the fact being verified.
  2. Request the accepted-document specification.
  3. Use the authenticated secure upload.
  4. Save submission acknowledgement.
  5. Ask for a precise rejection reason if needed.

Avoid these common mistakes

  • Emailing high-risk documents casually
  • Over-redacting required fields
  • Sending altered documents
  • Sharing passwords or one-time codes

Gambling is entertainment with a real risk of loss. Set a limit before play and never use money needed for essentials.

Frequently asked questions

Is verification normal?

Identity, age and payment ownership checks are normal in a regulated payment context. The request should still be specific and secure.

Can I refuse documents?

You can protect your privacy, but refusal may prevent lawful account or withdrawal checks. Ask about alternatives and data handling rather than submitting unsafe evidence.

Why was my document rejected?

Common reasons are expiry, glare, cropping, unreadable fields, address age or name mismatch. Ask for the exact reason.

Should verification happen before play?

Early checks reduce later friction, but additional lawful checks can arise when risk or payment circumstances change.

Continue the task

Sources and review note

Checked 2026-11-14. Rules and transition notices can change; open the primary source before relying on a deadline or provider status.

CashNotes NZ is an independent, editorial guide. It does not rank, recommend or link to gambling operators.