The documents, the channel, and the time bound the platform states.

What the platform states about identity verification

The betnow platform's public help-desk content names the documents required for identity verification: a government-issued ID (Aadhaar, PAN, passport, voter ID or driving licence), an address proof (Aadhaar, utility bill, bank statement or rental agreement), and a recent photograph for liveness matching where the platform requires it. We verified the existence of the document list on the help-desk content but did not register an account to verify the actual list on a real verification flow.

The platform's help-desk content also names the upload channel, the in-app KYC flow on web and mobile web, accessed from the account menu. We verified the existence of the in-app upload path on the betnow web and mobile web surfaces. The help-desk content names the verification time bound: "up to 72 hours" for first verification, with a note that first-time verifications may take longer.

When KYC is required

KYC is typically required at the point of first withdrawal, not at the point of registration. A reader who registers and explores the lobby without making a deposit may not yet be asked for KYC documents. The platform may also request KYC before the first deposit if the deposit triggers a risk-based threshold check.

We verified that KYC is part of the platform's published help-desk content but did not register an account to verify the exact trigger on a real account. A reader should treat the published trigger as a target, not a guarantee, the platform may ask for KYC earlier than the help-desk content states, depending on the deposit pattern and the jurisdiction.

The documents in detail

A government-issued ID is the primary identifier. Aadhaar, PAN, passport, voter ID and driving licence are the documents most platforms accept. The platform's help-desk content names the accepted documents. The reader should use the document they can produce in a clean, legible scan, a folded or low-contrast scan is the most common reason for a first-attempt rejection.

An address proof is the secondary identifier. Aadhaar, a recent utility bill (typically within 90 days), a bank statement (typically within 90 days) and a rental agreement are the documents most platforms accept. The platform's help-desk content names the accepted documents and the time bound for the document's age.

A recent photograph is required where the platform uses liveness matching. The photograph should match the photograph on the government-issued ID. The platform's help-desk content names the photograph requirement.

The upload channel in detail

The upload channel is the in-app KYC flow on web and mobile web. The flow accepts one document at a time, in a single image or a single PDF. The platform's help-desk content names the accepted file formats and the maximum file size. We verified the existence of the in-app upload path but did not register an account to verify the file format list or the maximum file size on a real account.

A reader who uploads a document should keep a copy of the uploaded file and the upload timestamp. The record is useful if the platform's verification rejects the document and the reader needs to escalate.

The verification time bound

The platform's help-desk content names the verification time bound: "up to 72 hours" for first verification, with a note that first-time verifications may take longer. We verified the existence of the time bound on the help-desk content but did not register an account to verify the actual turnaround on a real account.

A reader who submits KYC documents and does not receive a verification decision within the stated time bound should file an in-app help request with the ticket number convention. The escalation path is on the customer-care page.

What happens if a document is rejected

If a document is rejected, the platform sends a rejection notice with the reason, illegible scan, expired document, name mismatch, address mismatch. The reader can resubmit a corrected document through the same in-app upload channel. We verified the existence of the rejection notice on the help-desk content but did not register an account to verify the rejection reasons on a real account.

A reader who receives a rejection notice should keep the notice, correct the document according to the stated reason, and resubmit through the in-app upload channel. Repeated rejections can trigger a manual review, which adds time to the verification.

The wallet in detail

The wallet is the platform's internal balance record. A deposit adds to the wallet; a withdrawal subtracts from the wallet. The wallet is not a bank account and does not earn interest. The platform's help-desk content names the wallet's role and the relationship between the wallet and the payment-method picker.

We verified the existence of the wallet on the help-desk content but did not register an account to verify the wallet's actual behaviour. A reader who needs to understand the wallet's role should read the help-desk content directly.

Deposit methods

The platform's published deposit methods are on the help-desk content and the in-lobby payment-method picker. We verified the existence of the deposit-method picker on the lobby but did not register an account to verify the methods available in a specific jurisdiction.

A reader who needs to know the deposit methods available to them should open the lobby's payment-method picker from a registered account. The picker shows the methods available to the reader's account; the methods available to a different reader in a different jurisdiction may differ.

Withdrawal methods

The platform's published withdrawal methods are on the help-desk content and the in-lobby payment-method picker. We verified the existence of the withdrawal-method picker but did not register an account to verify the methods available in a specific jurisdiction.

A reader who needs to know the withdrawal methods available to them should open the lobby's payment-method picker from a registered account. The picker shows the methods available to the reader's account; the methods available to a different reader in a different jurisdiction may differ.

Limits in detail

The platform's published limits are on the help-desk content and the in-lobby payment-method picker. We verified the existence of the limit display but did not register an account to verify the limits on a real account. The limits include the minimum deposit, the maximum deposit, the minimum withdrawal, the maximum withdrawal and the per-period limits.

A reader who needs to know the limits should open the lobby's payment-method picker from a registered account. The picker shows the limits that apply to the reader's account.

Processing time in detail

The platform's published processing time is on the help-desk content. We verified the existence of the processing time statement but did not register an account to verify the actual processing time on a real account. The processing time stated is "up to 48 hours" for the first withdrawal, with shorter times for subsequent withdrawals.

A reader who needs to know the actual processing time should measure it on a real account. The published time is a target, not a guarantee.

Where to go next

For the four trust gates, account, payment, table integrity, dispute, the safety desk is the place to start. For the review ledger that scored the platform against five criteria, the product ledger is the place to verify what is and what is not measured. For the support path We verified, the customer-care page is the place to start.