Account information fields
Check What Account Information Is Being Requested
Registration pages often request several kinds of information at once. Before entering anything elsewhere, separate identity details, the recovery channel, authentication secrets, consent and any later verification step. The visual here is not an interactive form.
Treat every field as a data decision
The mock fields below are diagrams, not inputs. Do not send personal details to this website.
Use accurate information only through a trusted account route and match required documents.
Use a contact method you control; do not borrow another person’s OTP channel.
Adults-only rules apply. Do not alter a date to bypass an age check.
Create a unique password and keep it outside messages, screenshots and issue summaries.
Enter a code only into the same trusted flow that requested it.
Check the purpose, route and redaction rules before uploading sensitive identity material.
Age, terms and duplicate-account checks come first
Before providing any information elsewhere, confirm the adults-only requirement, local eligibility, applicable terms and whether an existing account already uses the contact method.
A duplicate registration can create verification and recovery problems. If a prior account may exist, stop and use the appropriate recovery route rather than changing personal details to create another record. This guide does not decide legal eligibility and does not state that service is available throughout India.
When verification does not complete
Record the field name, time, device, browser and exact error. Do not repeatedly upload different versions of a sensitive document unless a verified process instructs you to do so.
Review mobile source checks in the App Guide, address and phishing signals in Account Safety, and concise account questions in the FAQ. The Support Guide helps prepare a redacted chronology.
Consent should be specific and readable
A checkbox should have nearby wording that explains the purpose. Do not assume that a pre-selected control or a general privacy link explains every use of identity information.
Before providing data elsewhere, read whether the field is necessary for account creation, age confirmation, payment verification or marketing. Optional marketing consent should not be confused with required account terms. Keep a copy of the relevant wording when sensitive identity information is requested.
Do not use another person’s email, phone or document to complete a step. That creates an ownership and recovery problem in addition to any eligibility issue. Accuracy and personal control of the recovery channel are both important.
Document handling needs a trusted route
Identity documents can reveal name, date of birth, address, photograph, number and machine-readable data. A copied upload screen is not enough to establish where the file goes.
- Read the complete hostname before opening an upload control.
- Check what document types and fields are required.
- Avoid a link sent by an unsolicited agent or social account.
- Do not send a document as an ordinary chat attachment.
- Use a watermark only if the verified process permits it.
- Retain the time and purpose of the request without storing copies on a shared device.
Registration and payment identity can interact
A name or contact mismatch may appear later when a payment record is reviewed. Changing details casually to fit a payment method can create a larger verification problem.
Use accurate, consistent information and correct an error through the verified process rather than opening another account. Payment availability and identity requirements can change, so this page does not state a fixed method or verification document. Use the Payments Guide to preserve only masked transaction records.