Verification request matrix
| Check | Typical evidence | Safety question |
|---|---|---|
| Identity | Government-issued photo ID | Is the upload route on the verified domain? |
| Age | Date of birth and photo ID | Is the service restricted to adults? |
| Address | Recent accepted address document | Which fields are actually required? |
| Payment ownership | Bank or wallet evidence | Can unrelated transactions be masked? |
| Liveness | Selfie or short camera check | Which vendor receives biometric data? |
What this page can answer
The table sets the scope for account verification. It separates the useful conclusion from facts that still need a current source, an account record or qualified advice.
| Question | What this page establishes | Evidence boundary |
|---|---|---|
| Primary subject | account verification | The visible page and its dated sources |
| Safe use | Understand the issue and preserve a verifiable record | No account, payment or operator action is provided |
| High-risk facts | Legal, payment, identity and availability claims need current evidence | Unknown or stale details remain labelled |
| Next step | Follow a related guide, comparison or Help Centre checklist | Use a verified source rather than an intermediary |
Why accounts are verified
Verification can support age checks, anti-fraud controls, account recovery and payment ownership. A valid purpose should be named; “security” alone is too vague for an unlimited document request.
Try the account verification check with the relevant screen in front of you. Write down the exact label used for why accounts are verified, where it appears and what the interface asks for next. That small record is often enough to spot a missing step or an unexpected request.
Documents that may be requested
Public brand guides commonly mention passports, driving licences, PAN, Aadhaar, voter ID, address evidence and payment records. Exact accepted documents vary, and WM Guide does not advise sending any document until the recipient and upload route are verified.
Do not compress account verification into “worked” or “failed”. For documents that may be requested, capture the visible status, the time and any reference number. If the next screen asks for money, an OTP or a new download, pause and verify the route first.
Prepare clear but limited files
Use colour, readable images with all required edges visible. Remove unrelated pages and mask unrelated transactions where policy allows. Keep originals offline and store submitted copies in an encrypted location.
Could another person repeat this account verification check from your notes? Record the page address and the relevant account state, but leave passwords, full document numbers and payment credentials out of the record.
Name and address mismatches
Differences in initials, transliteration, old addresses or bank-account names can trigger review. Explain the mismatch once with supporting evidence rather than repeatedly uploading different documents.
Try the account verification check with the relevant screen in front of you. Write down the exact label used for name and address mismatches, where it appears and what the interface asks for next. That small record is often enough to spot a missing step or an unexpected request.
Secure upload and privacy
Prefer an authenticated account portal. Avoid email or messaging attachments unless the verified policy explicitly uses them. Check retention, deletion and third-party vendor information.
Do not compress account verification into “worked” or “failed”. For secure upload and privacy, capture the visible status, the time and any reference number. If the next screen asks for money, an OTP or a new download, pause and verify the route first.
Rejected or looping verification
Ask for the exact rejection reason: blur, glare, expiry, unsupported type, mismatch or liveness failure. A precise reason is actionable; repeated “try again” messages are not.
Could another person repeat this account verification check from your notes? Record the page address and the relevant account state, but leave passwords, full document numbers and payment credentials out of the record.
When to stop
Stop if a contact asks for an OTP, password, PIN, seed phrase, remote access, payment or an unrelated identity document. Preserve the request and use a formal reporting route.
Try the account verification check with the relevant screen in front of you. Write down the exact label used for when to stop, where it appears and what the interface asks for next. That small record is often enough to spot a missing step or an unexpected request.
A working notebook for account verification
Use these prompts when account verification is part of a real research or support question. They turn the information into a short record without asking you to register, pay or disclose credentials. You do not need to complete every prompt. Choose the ones that match the decision in front of you, keep the notes together and remove personal details before sharing the record. The aim is a trail another person can follow, not a larger collection of screenshots. Write in ordinary language and preserve the original status wording beside your summary, so a reviewer can separate what the source said from your interpretation.
Write the question first
Reduce account verification to one question you can actually answer. “Is this safe?” is too broad; a question about the wording in Why accounts are verified, a visible account status or the owner of a payment reference is workable. Add the date and the screen or document in front of you. This keeps a later search from drifting towards whichever page sounds most certain.
Keep the source attached
For account verification, save the URL or document name beside the claim rather than in a separate pile of tabs. Note whether it came from law, a government notice, first-party help, an account screen or an unaffiliated page. That label changes how much the claim can establish. It is especially useful when reading Documents that may be requested, where similar wording may hide a different entity, region or publication date.
Read exact status words
Copy the exact term used around Prepare clear but limited files. “Submitted”, “pending”, “approved”, “processed” and “completed” describe different stages; none should be silently replaced by a more reassuring word. In a account verification record, quote the short status, add the time and keep the associated reference. If a support reply uses different wording, ask which account state it corresponds to.
Separate the interface from the outcome
A neat screen can make account verification easier to navigate, but it cannot prove the result of Name and address mismatches. Treat design, documentation and outcome as three separate observations. A feature may be easy to find while its conditions remain unclear. Likewise, a long help article may describe a standard process without resolving what happened in one account. Keeping those observations apart produces a more useful conclusion.
Limit sensitive material
Before sharing anything connected with Secure upload and privacy, identify the recipient and the minimum field needed to answer the question. A screenshot can expose names, balances, document numbers, QR codes or recovery details outside the area you meant to show. Crop only for your own record; when a verified process needs an original document, follow its stated format and ask whether unrelated information may be masked.
Record the gap honestly
If the available material does not settle Rejected or looping verification, write “not confirmed” and name what is missing. For account verification, that missing item might be a current terms page, a matching legal entity, a transaction reference or a dated policy. A visible gap is actionable: it tells the next reviewer what to find. A confident guess removes that trail and can turn an old description into a false current claim.
Choose a reversible next step
The next move on account verification should create information without creating a second problem. Reading a primary source, exporting account history, changing a unique password through a known route or calling a bank from its official app leaves a record and can be controlled. Another transfer, an unknown installer, an OTP shared in chat or remote access to the device is different. Stop when the proposed fix depends on one of those.
Close with a dated summary
End the account verification check in four lines: what is established, what remains open, which source was last checked and who owns the next action. Link that summary to When to stop if it is the point most likely to change. This is quicker to revisit than a folder of screenshots and makes contradictions obvious. If nothing new appears, keep the limitation rather than reopening the same question through an unverified intermediary.
Put the guide to work
Apply the account verification guide to one real screen, message or record at a time. Match its wording to the relevant section, note what you can prove and circle the next reversible step. Reading a policy, saving a reference or using an official recovery page can be checked; sending another payment or sharing an OTP cannot be taken back.
Finish the account verification check with a short note: current status, evidence date and who owns the next action. That makes the guide useful again if the issue returns or a support answer changes.
Frequently asked questions
Is PAN or Aadhaar always required?
No universal document rule applies across every platform and account. The verified policy should state accepted alternatives and purpose.
Can I send documents over WhatsApp?
That is high risk unless a verified policy explicitly names the channel. An authenticated upload portal is safer.
Why was a clear document rejected?
Common reasons include glare, cropping, expiry, unsupported format, mismatched name or automated liveness failure.
Should I show my full bank statement?
Only provide fields required for the stated check. Ask whether unrelated transactions may be masked.
What if support asks for another payment to verify me?
Do not pay. Verification should not require a transfer to a new beneficiary or an unlock fee.
How long should I keep evidence?
Keep the request, submitted-file names, timestamps and ticket reference until the matter is resolved and any dispute period has passed.