Maple Casino DeskIndependent Canada guides22BET ↗
Partner offers · CanadaUpdated 28 October 2026Winshark · Welcome bonus300 free spins
Partner reviews (4,939)
5.0Partner rating
18+. Offer wording, rating and review count are reported by the partner and shown as received. Availability and terms depend on where you are. Gambling carries financial risk.
18+. Offer wording, rating and review count are reported by the partner and shown as received. Availability and terms depend on where you are. Gambling carries financial risk.
22Bet · Welcome bonus+250% on your deposit
Partner reviews (2,748)
5.0Partner rating
18+. Offer wording, rating and review count are reported by the partner and shown as received. Availability and terms depend on where you are. Gambling carries financial risk.
Offers, scores and review totals supplied by partners. Not an independent ranking. · IP Geolocation by DB-IP
PlayOJO verification concerns the operator's checks on account information and requested evidence. This publisher cannot approve an identity, review private documents, or remove a restriction from an account.
The Canadian help page describes possible automatic checks before uploaded documents are requested. That does not establish automatic approval, a universal review stage, or a fixed processing interval.
Follow the actual request shown by the operator rather than sending every document you possess. A focused submission should answer the stated requirement without exposing unrelated personal information.
This page explains public document guidance and careful preparation. No account was verified during research, and the current regional upload interface was not tested with a customer's documents.
Confirm the request inside the appropriate official account route or through a contact channel verified at the operator. A message using familiar branding is not sufficient proof of origin.
The dedicated document page identifies My Account and Upload Documents as the submission route. Check the current account controls rather than uploading evidence to an affiliate form or public discussion.
If you cannot sign in, describe that barrier to official support before seeking an alternative submission method. This publisher does not provide a substitute document mailbox or verification service.
Keep regional instructions distinct when reading guidance. A document article on the broad Canadian route does not prove every account uses the same controls as the separate Ontario-facing website.
The dedicated guide gives a passport, driving licence, and government identity card as examples. Your actual account request determines which evidence is appropriate for the particular check.
An example is not a guarantee that every version of a document will be accepted. Read the request carefully, especially if the issuing jurisdiction or document type needs clarification.
Use a valid document that belongs to the account holder. Do not submit another person's identity evidence, change identifying details, or borrow an image to complete an upload.
If your situation does not fit the listed examples, ask support which alternative is appropriate. Do not infer acceptance from a review website or another customer's unrelated experience.
The public document guidance asks for legible colour images showing complete edges. A cropped corner can hide context the reviewer needs, even when the main name appears readable.
Place the document against a plain surface and check the image before submission. Glare, motion blur, and shadows can obscure the same information that the request is meant to establish.
Make sure the complete document remains visible without shrinking it beyond readability. A screenshot of an already compressed message may be less useful than a clear original capture.
Improving image quality is different from editing document content. Do not alter text, dates, photographs, or identifying details to make evidence appear valid or match an inaccurate account.
The dedicated guide gives utility bills and bank statements as address-evidence examples. It describes matching the registered name and address and meeting a document-recency requirement stated in the current guidance.
Check that the submitted page actually contains the relevant name and address. A transaction screenshot without that context may not answer a request specifically concerning proof of residence.
If your address has changed, explain the mismatch and ask how to update the account. Do not present an old address as current simply because it matches an earlier registration.
Read the exact request before choosing a statement or bill. This guide does not substitute a blanket document list for the operator's case-specific instructions or guarantee acceptance.
| Evidence category | Public examples or guidance | Check before submitting |
|---|---|---|
| Identity | Passport, driving licence or government ID | Valid and requested for this case |
| Address | Utility bill or bank statement | Relevant name, address and recency |
| Card evidence | Dedicated masking instructions | No complete credentials or security code |
| Changed details | Account-specific request | Explain the genuine mismatch |
The help page notes that account details can be managed through Personal Settings and that some identity fields may require evidence. A change request and document approval are separate processes.
A typing mistake, an address move, and a legal name change have different explanations. Describe the actual situation accurately instead of treating every mismatch as a technical upload fault.
Ask which record needs correcting and what evidence supports the correction. Do not change a genuine document image to agree with information entered incorrectly into an account.
Keep the operator's explanation with the relevant request so that later communication follows the same issue. Mixing several unrelated account changes can make a straightforward evidence question harder to understand.
The dedicated document guide contains card-masking instructions that differ from a sentence on the broad help page. Use the dedicated guidance and the current account request, not contradictory summaries.
Conceal the card-number middle section and never expose the security code in an editorial screenshot or message. This guide does not ask you to display complete payment credentials anywhere.
Check that masking does not hide the information specifically required by the genuine request. If the instructions appear inconsistent, ask the operator to clarify before submitting the image.
Do not upload card images here or send them to an unknown recovery helper. Payment ownership evidence belongs only in the operator's authorised verification process when genuinely requested.
The dedicated guide says changed personal details or payment methods can lead to new requests. Previously supplied documents therefore do not establish that every later account review is complete.
Identify the exact method or account detail mentioned in the new request. A question about payment ownership should not automatically be answered with an unrelated address document.
Keep the ownership of the account and receiving method clear. Do not solve a mismatch by introducing somebody else's wallet, card, identity document, or account details into the process.
If an incoming-only product cannot receive a withdrawal, that is a payment compatibility issue as well. Consult the method guidance rather than assuming another identity upload changes the product.
Read the displayed rejection or upload message before resubmitting anything. A file-format problem, unreadable image, missing edge, and account-detail mismatch each calls for a different response.
Check the current interface for its actual file requirements. No universal format list or upload-size limit was verified during research, so this guide does not invent either specification.
Retake an unclear image rather than repeatedly sending the same unreadable file. If the reason is unclear, ask which information is missing instead of making speculative document changes.
Keep a private record of the message and submission stage. A support request is more useful when it explains whether upload failed locally or a received document was later rejected.
Before resubmitting a file, compare the rejection message with the image itself, checking whether the issue concerns readability, document relevance or account details rather than guessing that another format fixes everything.
| Problem | Appropriate next check | Do not assume |
|---|---|---|
| Blur or cropped edge | Retake a clear complete image | Resending fixes readability |
| File rejected by interface | Read actual format requirements | A universal upload limit exists |
| Account details differ | Ask about correcting the record | Editing evidence is acceptable |
| Uploaded but pending | Ask what requirement remains | Submission equals approval |
An upload confirmation establishes that a submission step was recorded, not that the evidence has been approved. Read any later account message before treating the review as finished.
If the account still shows a pending requirement, identify whether it concerns the same document or another requested item. Do not assume that all checks are identical or simultaneous.
No verification deadline is established by the sources used here. A promised review time copied from another country or a player's anecdote would not establish your account's outcome.
If an administrative question affects a withdrawal, keep the document and payment references connected in official communication. That context can clarify the issue without implying approval guarantees.
Store identity images where other people cannot casually access them, and avoid posting them in forums. A discussion about verification does not require making personal evidence public.
Use a narrowly relevant document when the operator asks for one. If a statement includes unrelated sensitive information, ask what may be obscured without invalidating the requested evidence.
Do not share passwords, recovery codes, bank login details, or complete card credentials alongside a document request. Those secrets are not needed by this publisher for any explanation.
The operator's privacy information governs its own handling of submitted documents. This publisher's separate privacy notice does not describe or control the operator's storage and review practices.
State the requirement shown, the kind of document submitted, and the exact response received. Avoid including the document itself in an initial message unless the official route specifically requires it.
Explain whether the difficulty is account access, file upload, document readability, or a mismatch in personal details. Clear categories help prevent support from responding to the wrong problem.
If you submitted evidence already, ask whether it was received and which requirement remains outstanding. Do not claim that an upload confirmation necessarily proves the operator approved the material.
Use a contact channel confirmed on the official help page and keep the case reference privately. This publisher cannot escalate a document review or promise a response interval.
First confirm that the request is genuine and belongs to your regional account. Then identify the requirement and prepare only the evidence the operator has actually requested.
Check image readability, complete edges, validity, and consistency with the account details. If a mismatch is genuine, explain it instead of altering evidence to make the discrepancy disappear.
If instructions conflict or your document is not among the examples, ask for clarification before submitting more material. A careful question can prevent unnecessary exposure of unrelated personal records.
Verification is an administrative review, not a reason to gamble or deposit again. You may stop and seek clarification without treating promotional pressure as part of the document process.
Verification is the operator's account-check process, which may involve automatic checks or requested evidence. This publisher cannot assess your identity, approve documents, or remove an account restriction.
The public guide gives passport, driving licence, and government identity-card examples. Your actual account request determines the appropriate evidence; an example list does not guarantee every document's acceptance.
The dedicated guide identifies My Account and Upload Documents. Confirm the genuine regional account route and current request before submitting evidence; this publisher is not a verification upload service.
Read the actual rejection reason. The public guide requires clear colour images and complete edges, but readability, account mismatches, and interface file requirements are different issues needing different responses.
No case-specific review deadline was established. Ask whether evidence was received and which requirement remains outstanding, rather than applying another customer's timing to your own account situation.
Yes, the dedicated guidance says changed personal details or payment methods can lead to new requests. Earlier submission or approval does not establish that every later requirement is satisfied.
Do not expose complete card credentials or the security code. Follow the dedicated masking guidance and genuine current request, asking for clarification if the instructions appear inconsistent.
No. Uploading and approval are separate events. Read the account response and ask which requirement remains pending rather than treating a submission confirmation as proof of accepted evidence.
Design preview only. The owner supplied this percentage offer, score and review count; none is verified. The public Canadian welcome information uses a different promotion format. No live offer or independent review rating is asserted. The partner destination is not configured. Adults only; provincial eligibility and the appropriate regional account rules apply.
Public-source review: · Maple Casino Desk
