Skip to content
NewinZora in your browser
Zora in your browser

Uploading an account document from a phone

When Zora requests an account document, start with the exact request in the verified account flow.

4 min read
01

Read the exact account request before preparing a file

When Zora requests an account document, start with the exact request in the verified account flow. The document type, required sides and accepted file rules should come from that request. A general review cannot determine which evidence a particular account will need or promise that one upload completes verification.

Identify which document is requested, what purpose the account message gives and whether particular sides or details are required. A proof-of-identity request and a payment-source request are not interchangeable. Do not send an unrelated collection of files in the hope that one will satisfy the review. The account’s specific instruction should guide preparation. If a term is unclear, ask about that requirement before uploading. A general website guide cannot decide that a particular account has completed verification or predict which further evidence may be requested.

02

Check the image for legibility and completeness

Prepare a readable image in good light, with the requested information and document edges visible where required. Check focus, glare and accidental cropping before upload. Do not alter identity details, fabricate missing fields or add filters that make the document harder to assess. Follow any explicit masking instructions from the secure process rather than guessing what can be hidden.

Inspect the image on the phone before choosing it. Text should be in focus, glare should not cover required fields and the framing should follow the request. Retaking an unclear photograph is different from editing document information. Do not invent missing details or alter the content to make it appear to satisfy a condition. Where masking is explicitly requested, follow the secure process’s instructions rather than concealing fields arbitrarily. The objective is a readable representation of the requested evidence, with no unnecessary transformation that makes assessment harder.

03

Verify the selected file and stated upload requirements

On the phone, verify the selected file in the preview. Similar filenames and recent photos can make it easy to choose the wrong image. Check the stated format and size limit in the upload screen, without assuming a universal limit. If the system rejects the file, read the reason before taking several more photographs.

The phone’s file picker may show recent images with similar thumbnails, so open the preview and verify the actual file. Read the accepted format and size limit displayed by the upload form; do not assume one universal requirement across documents. If the form rejects the file, capture the reason without exposing the document publicly. A format error, an oversized file and an unreadable image require different corrections. Repeatedly selecting the same rejected file without understanding the message does not make the submission more complete.

04

Track submission separately from review approval

After submission, distinguish received, under review, accepted and further information required. Upload completion is not the same as approval. Keep the submission reference or status and avoid sending duplicate documents through several channels unless asked. A support message can refer to the upload without reproducing the sensitive image.

After sending, look for a receipt or status showing that the file reached the account process. Received, under review, accepted and further information required describe different stages. An upload progress bar reaching the end does not itself establish approval. Keep the reference and check the designated status area rather than resending through several channels. If support needs a question, refer to the existing submission and exact message. This keeps the review traceable and avoids creating multiple inconsistent copies without a clear connection to the original request.

05

Use the private route and minimise unnecessary copies

Use the designated private route and remove unnecessary copies from shared locations once no longer needed. If the request arrived unexpectedly outside the account, verify it before supplying anything. The aim is a clear, relevant submission with a traceable status, not a larger collection of personal files sent without context.

Use the verified account’s private route, especially when an unexpected message asks for a document elsewhere. Keep only the copies needed for the legitimate process and avoid leaving them in shared albums, public folders or screenshots posted for troubleshooting. If the request cannot be verified in the account, clarify it before supplying sensitive information. A good submission is relevant, readable and associated with a specific status. Sending more documents than requested does not guarantee faster approval and can expose information that was never necessary for the review.