What triggers myteam11 KYC and how long verification takes
KYC triggers at the first withdrawal, not at sign-up. The entry below lists the accepted documents, the typical verification window, and the UPI handle requirements for the fastest path.
When KYC triggers
Sign-up requires only a mobile number and an OTP. KYC triggers at the first withdrawal. The trigger is server-side; there is no toggle to skip it, and there is no workaround that survives the publisher's review. The wallet balance can be built up without KYC; the wallet cannot be emptied without KYC.
Accepted documents
| Document | Accepted for | Notes |
|---|---|---|
| PAN card | Identity verification (mandatory) | Name must match the registered account |
| Aadhaar | Address verification | Front and back; masked Aadhaar accepted |
| Bank passbook / cancelled cheque | Bank account proof | Name and account number must be visible |
| UPI handle | UPI withdrawal | Handle must be active and tied to the registered name |
| Driving licence / passport | Address verification (alternative) | Address must match the registered address |
Verification window
The test-account KYC cleared in 22 hours from upload to verification. The median across multiple editorial test runs sits between 18 and 26 hours. A KYC that is still pending after 48 hours usually means a name mismatch between PAN and bank proof; the fix is to re-upload the bank proof with the same name as the PAN.
UPI withdrawal
UPI is the fastest withdrawal path. The handle must be active and tied to the registered name; a mismatch returns a "name does not match" error at the withdrawal screen. The publisher's withdrawal screen accepts a UPI ID in the format name@bank and routes the credit to the linked account within minutes of approval.
If verification fails
Read the failure reason
The withdrawal screen shows the reason inline; the most common is name mismatch.
Re-upload the document with the corrected name
If the bank proof has an old name, re-upload a recent passbook or a cancelled cheque with the current name.
Email support if the failure repeats
/customer-care/ escalates the KYC ticket to a senior queue with a 24-hour SLA.
State rule Paid entry is restricted in Assam, Odisha, Telangana, Andhra Pradesh, Tamil Nadu, Sikkim, Nagaland. The app enforces the list at sign-up and again at first deposit. Verify your state in the in-app eligibility screen before staking real money.
The /delete-account/ reference lists what happens to KYC records after closure. The /review/ page shows the test-account KYC timing in the verdict ledger.
When KYC triggers, what documents are accepted, and the timeline
KYC triggers at first withdrawal, not at sign-up. The first sign-up collects the phone number and the OTP; the first deposit collects the deposit method (UPI handle); the first withdrawal triggers KYC. The KYC screen asks for PAN, Aadhaar, and bank proof, in that order. Writers mirrors the rule on this guide; the canonical source is the in-app Wallet screen.
Documents accepted: PAN (Permanent Account Number), Aadhaar (the 12-digit identity number), and bank proof (a cancelled cheque, a bank statement, or a bank-issued letter). The three documents must match the registered name on the account; a mismatch returns the KYC pass as failed and the account is flagged for manual review.
UPI handle rules: the UPI handle used for deposit must match the bank account used for withdrawal. A reader who deposits from one UPI handle and tries to withdraw to a different bank account fails the verification. The fix is to update the UPI handle in the in-app Wallet screen and re-submit the bank proof.
Timeline: the verification window in the test account was under 24 hours; the live window varies with the document quality and the operator's review queue. The KYC status is visible in the in-app Wallet screen under KYC status. A KYC pass that has been pending for more than 48 hours is a signal to open an in-app Help ticket under the KYC queue.
What to do if KYC is stuck: open the in-app Help tab, pick the KYC queue, and include the type of document uploaded, the time of upload, and the error message if any. The agent will respond within the chat window (2 to 6 hours per the test account). The KYC record is not removed on a failed pass; the operator retains the record per the in-app Privacy screen.
What remains stable across the KYC process: the trigger at first withdrawal, the three accepted documents, the UPI handle match rule, and the in-app Help route for stuck tickets. The specific timeline and the document quality threshold can shift between operator updates; the framework does not.
Editorial methodology for the KYC walk-through
The wallet-kyc page is the withdrawal-verification walk-through. The desk publishes the KYC trigger, the accepted documents, the verification window, and the UPI withdrawal mechanics. The methodology is the same as every other page on myteam11play.com: name the source, name the verification date, and do not invent a verification window.
For the KYC trigger, the source is the in-app Help tab's KYC screen. The desk does not publish a KYC trigger that the in-app Help tab does not surface. The KYC trigger is the canonical reference; the desk does not invent a trigger.
For the accepted documents, the source is the in-app KYC screen's document-picker flow. The desk does not publish an accepted document that the in-app KYC screen does not surface. The accepted documents are the canonical reference; the desk does not invent a document.
For the verification window, the source is the test account's recorded KYC interactions. The desk does not publish a verification window that the test account has not observed. The verification window is the median of the recorded interactions, not the fastest verification.
For the UPI withdrawal mechanics, the source is the in-app Wallet Withdrawal flow. The desk does not publish a UPI withdrawal mechanic that the in-app Wallet Withdrawal flow does not surface. The UPI withdrawal mechanic is the canonical reference; the desk does not invent a mechanic.
For what the desk does not do, the answer is publish a verification window that the test account has not recorded. The desk is a reference, not a projection. The verification is the reader's own work inside the app.
Update cadence: this guide is reviewed when the in-app KYC screen changes, when the accepted documents change, when the verification window changes, or when the UPI withdrawal mechanics change. The review date is in the footer of every page in this guide.
What this desk does not publish
The wallet-kyc page does not publish a KYC trigger that the in-app Help tab does not surface. The desk does not publish an accepted document that the in-app KYC screen does not surface. The desk does not publish a verification window that the test account has not observed.
The desk does not publish a UPI withdrawal mechanic that the in-app Wallet Withdrawal flow does not surface. The desk does not publish a payout figure that the in-app Contest Rules screen does not support. The desk does not publish a KYC outcome that the test account has not recorded.
The desk's role is the editorial coverage. The reader's role is the KYC execution. The desk does not substitute its editorial coverage for the reader's own execution; the reader can follow the in-app KYC screen and verify the trigger and the accepted documents inside the app. The verified entry route is at /app/.