Prepare for the document request
Private by design: no login, PIN, document upload or transmission. Answers stay on this page and are not saved.
Wasafi Bet verification is not the same as receiving an activation SMS. The operator's terms separately require accurate identity details and allow requests concerning identity and the source of deposited funds.
Begin with the actual request: what information is missing, who is asking, where should it be submitted and what decision depends on it? This guide neither receives documents nor approves accounts.

What is established by the published rules?
| Requirement | Published scope | Do not infer |
|---|---|---|
| Name matches government ID | Account information requirement | That a nickname is sufficient for every stage |
| Mobile-money number matches account | Deposit identity condition | That a borrowed wallet is automatically accepted |
| Further documents may be requested | Identity and source-of-funds checks | An unlimited right for an unknown caller to collect documents |
| One customer account | Duplicate accounts may be reviewed | That another registration solves a verification problem |
The reviewed terms do not establish one universal document list or guaranteed review time for every customer. A precise request from the operator is more useful than an aggregator's fixed checklist.
Prepare a document response, not a public dossier
Read which document is requested and why. Check that the account name and relevant details agree before submitting anything, then ask for clarification if the requested information is unclear or inconsistent.
Do not alter documents, hide a requested field without agreement or submit an invented replacement. If the operator rejects a file, ask which requirement was not met rather than guessing through repeated uploads.
Use only the identified operator submission route. A social-media comment, this guide's contact page or a stranger's private chat should not become a repository for identity scans and payment history.
Photo quality and data exposure are separate checks
If a document photo is requested, make it readable without glare, blur or accidental cropping of required details. Read the operator's specific format instructions; do not assume that every document type is accepted.
Before sending a screenshot, check whether unrelated messages, account credentials or another person's details are visible. Provide the evidence actually requested rather than an entire gallery or unfiltered conversation history.
The illustrative photos on this guide deliberately do not show readable identity details. They are not examples of a real person's submitted documents or evidence that an account review was completed.
Source-of-funds questions need their own explanation
The terms allow enquiries about deposited funds. That is different from ordinary password recovery or the SMS activation step. Ask which transaction and which document the request concerns.
Retain the request reference and the answer. A support message saying only “send everything” is less useful than a documented explanation of the missing evidence and the secure route for supplying it.
If the name or number does not match
| Mismatch | Useful next step | Unsafe shortcut |
|---|---|---|
| Name differs from identification | Ask about correcting account details | Editing the ID to fit the account |
| Payment number differs | Explain ownership and seek operator instructions | Borrowing another wallet or creating a duplicate |
| Registered SIM no longer controlled | Address SIM ownership and operator recovery separately | Asking a stranger to receive account codes |
| File rejected | Request the exact rejection reason | Submitting fabricated or repeatedly modified files |
A correction to the mobile provider's record does not necessarily update the betting account. Keep track of which organisation controls each record and what confirmation it provides.
Verification and a delayed withdrawal
If a withdrawal is held, ask whether the document request is the current blocker or whether another payment stage is pending. Preserve the payout reference alongside the verification case.
Do not assume that submitting a document guarantees immediate wallet receipt. Account review, payment approval and provider settlement are different stages, and the evidence reviewed does not establish a universal time limit.
Turn an unclear request into a precise checklist
Before sending anything, identify what the operator wants to establish: identity, registered-phone ownership, account details or source of funds. A broad request for verification should not be interpreted as permission to send every private document you possess.
Ask which document type, which sides or pages and which secure submission channel are required. Where the request does not explain those details, obtain clarification rather than guessing from a different operator's tutorial.
This guide does not provide a universal accepted-document list because the reviewed Wasafi documents do not establish one for every circumstance. A preparation checklist is not an approval decision or a substitute for the actual request.
| Clarify | Why it matters | Do not substitute |
|---|---|---|
| Purpose of the request | Identity and source of funds answer different questions | A generic account screenshot |
| Required document or record | Prevents irrelevant disclosure | An invented universal document list |
| Secure recipient | Establishes where the evidence is meant to go | A stranger's forwarded chat |
| Case or submission reference | Connects the response to the request | Another customer's reference |

Name differences should be explained, not edited away
Compare the name in the account with the genuine document. If there is a spelling, order or other discrepancy, describe it accurately to official support and ask how it should be resolved.
Do not alter the document image to make the names appear identical. Changing the visible evidence would not correct the underlying account record and could create a different problem from the original mismatch.
If an account-detail correction is needed, ask for the operator's authorised procedure. This independent guide cannot perform the correction, determine acceptable evidence or promise that a particular explanation will satisfy the review.
Use the same existing-account reference when following up. A second registration does not repair the first record, and Wasafi's one-account condition remains relevant while the original identity question is being resolved.
Keep image quality separate from excessive disclosure
A document can be genuine but unreadable in a poorly lit photograph. Conversely, a clear image can disclose unrelated information unnecessarily. Ask the official recipient what is required before deciding what to include.
Do not assume that cropping, masking or watermarking is always accepted. Equally, do not send unrelated pages simply because a generic review recommends a full dossier. The applicable submission instructions need to settle the actual scope.
Avoid public posting as a way to speed up review. A public complaint does not need the same sensitive attachments as an identified private verification process, and search engines may retain material after a post is removed.
This website has no document uploader. The preparation helper only selects written guidance, stores no answers and cannot examine whether an image is sufficient. It is intentionally not an identity-verification service.
Source-of-funds evidence is a separate request
Ask which transaction or period the operator is reviewing and which genuine records are accepted. The purpose is not answered merely by repeating an account name or sending a photograph of an unrelated identification document.
If the requested record includes other people's private information, raise that issue with the official recipient before submitting it. Do not improvise an altered financial statement or create a false explanation for a transaction.
The reviewed terms allow such requests, but this guide has not verified a single universal format, approval time or outcome. Keep those missing details unresolved instead of presenting an attractive guaranteed processing period.
After submission, record the state rather than assuming approval
Keep the case reference and the confirmation that the material was received, if provided. Receipt is one stage; an acceptance decision is another. A later payment request may still have its own applicable checks.
When following up, ask whether further evidence is required and quote the same case. Do not repeatedly send documents through new channels merely because an earlier submission has not yet produced a decision.
Verification questions
Does SMS activation mean all checks are finished?
No. Activation confirms a specific communication step. The terms allow additional identity and source-of-funds enquiries after an account exists.
Is there a guaranteed list of accepted documents here?
No universal list was verified for every account. Follow the genuine operator request and ask for clarification about the document type or format.
Can I upload my ID to this guide?
No. This is an independent information site, not the operator's verification system. Use the identified secure submission route provided by the operator.
Should I send a password with the documents?
No. Account passwords, wallet PINs and current SMS access codes should not be included in a document-response message.
What if my name has a spelling error?
Ask the operator how to correct its account record. Do not alter a genuine identity document to make the two strings appear to match.
Can opening another account avoid a review?
The reviewed terms permit one customer account. A second registration can add a duplicate-account problem rather than resolve the original evidence request.
Does completing verification guarantee immediate withdrawal?
No universal timing guarantee is established. Ask which payout stage remains and compare the operator's reference with provider settlement records.
Where should I keep the case information?
Privately, alongside the request date, case reference, submission confirmation and rejection reason if any. Do not post identity documents publicly to prove that a complaint exists.
Sources and checking
Checked 22 October 2026. Published documents, not a tested deposit or withdrawal.
- Terms section 4.2 — Registered name must match government ID
- Terms section 4.4 — Mobile-money depositing number must match receiving betting-account number
- Terms sections 3.5 and 5.3 — Operator may require identity and source-of-funds documents
