Wallet and KYC: PAN, masked Aadhaar, bank proof

The KYC document set on myteam11app.com comprises three standing requirements: PAN (Permanent Account Number), masked Aadhaar (the 12-digit unique identity number with the first eight digits masked), and a bank proof (cancelled cheque, bank statement or a bank-issued passbook scan showing the account holder's name, account number and IFSC).

Each document is uploaded in the operator's KYC surface inside the wallet. Document files are accepted as JPG, PNG or PDF; the standing size limit is 5 MB per document. Documents that exceed the limit are rejected at upload and require resizing before retrying.

The KYC chain is gated to first deposit eligibility, withdrawal eligibility, the welcome bonus eligibility and the refer and earn eligibility. Failing any document voids all four gates regardless of which gate the user was trying to satisfy.

PAN is the operator's primary identity check. The PAN upload requires the full ten-character alphanumeric string on the front of the card, the cardholder's full name as it appears on the card, and the date of birth. Documents that are torn, smudged or otherwise unreadable are rejected; the operator's KYC queue will send a replacement request through the in-app help.

PAN is one per verified mobile number. The operator does not allow two verified accounts to share a PAN. Attempting the registration with a PAN already on file cancels the registration on the second account. Visitors who need to manage a shared PAN across accounts should contact customer care through /customer-care/.

PAN expiry is not in scope; the PAN card does not carry an expiry date, and the operator's verification checks against the issuing authority's standing register.

Masked Aadhaar is the Aadhaar variant where the first eight digits are masked and only the last four digits are visible. The masked version is downloadable from the UIDAI portal. The full 12-digit Aadhaar is not accepted by the operator because the masked variant satisfies the verification need without exposing the full identifier.

Uploading the full Aadhaar does not accelerate the KYC chain and may trigger a security flag. Visitors who upload the full Aadhaar should re-upload the masked version through the in-app help to clear the flag.

Aadhaar file format is PDF; image-only Aadhaar cards are rejected at upload. The standing reading is that the masked Aadhaar download from UIDAI is a PDF.

The bank proof is the link between the wallet and the withdrawal destination. Three variants satisfy the operator's standing requirement:

• Cancelled cheque. The cheque leaf with the cancellation mark, showing the account holder's name, account number, IFSC and bank branch. The cancellation mark is required and signals that the cheque has been voided for KYC use.
• Bank statement. A recent statement of one to three months, downloaded from the bank's own portal, showing the account holder's name, account number and at least one transaction. The statement must be PDF; image-only statements are rejected.
• Bank-issued passbook scan. A scanned page of the passbook showing the account holder's name, account number and IFSC. Passbook scans must be at least 300 DPI to clear the OCR layer.

The account holder's name on the bank proof must match the name on the PAN and the masked Aadhaar. Mismatched names are the most common cause of KYC rejection at this step.

Rejected KYC documents trigger an in-app notification. The notification carries the rejection reason and a request to re-upload the matching document. Common rejection reasons include: torn document, mismatched name across documents, expired or out-of-date statement, file size over the 5 MB limit, wrong file format, illegible scan or photo.

The standing correction flow is to read the rejection reason in the in-app help, fix the matching document, and re-upload. The re-uploaded document restarts the KYC queue, and the previous rejection is cleared on re-upload success. myteam11app.com does not publish the KYC queue SLA because it is operator-controlled.

Users who cannot clear KYC after the second attempt can reach customer care through /customer-care/. Customer care will either escalate the queue position or provide the third-attempt correction surface.