Payment, verification & safety

KYC and verification

KYC stands for “Know Your Customer”. It is the platform’s process for confirming the player’s identity and the source of funds. The platform is required to collect and verify a small set of documents before withdrawals. The most common KYC gap is the document set being incomplete; the most common fix is a clearer re-upload.

Payment rails

UPI is the fastest deposit rail; cards can take a few minutes to reflect. Withdrawal time-bands vary by rail and by the platform’s queue. The platform’s help center is the most reliable source for the most recent published time-band.

Phishing and fake support

Phishing pages copy the visual design of legitimate platforms and operate under similar URLs. The single most useful habit is to bookmark the platform’s official domain and only reach it through that bookmark. Real support does not ask for your password, OTP, or full card number.

• Verify the official URL before any login. Bookmark the official domain.
• Never share OTP, password, or full card number with any “support” chat.
• Verify HTTPS and the lock icon, but treat the lock icon as a baseline, not a guarantee.
• Check the app publisher name on the official app store before installing.
• Never download an APK from a Telegram link or a forwarded message.
• Use the platform’s in-app complaint route for any suspicious contact.

Encrypted connections

The platform uses HTTPS for all in-app and web traffic. Treat the lock icon as a baseline, not a guarantee. Phishing pages can also have lock icons.

The eight-row safety checklist

1. Bookmark the official domain and only reach it through the bookmark.
2. Verify the app publisher name on the official app store before installing.
3. Never share OTP, password, or full card number with any “support” chat.
4. Set a deposit limit before the first deposit, not after the first spike.
5. Set a session time-band and stop when the time-band is reached.
6. Use the platform’s in-app complaint route for any suspicious contact.
7. Read the T&C withdrawal time-band before the first deposit.
8. End the session immediately if the platform’s behaviour changes unexpectedly.

Safety questions

The full safety desk

The safety desk is the platform’s binding source for KYC, payments, and anti-phishing. The desk is staffed 24/7; the response time-band is published in the help center. The desk is the binding source for the platform’s safety commitments.

The desk is also the binding source for any update to the KYC requirements. The desk publishes the update in the help center; the player should verify the published date before submitting any document.

A closer look at the payment rails

UPI is the fastest rail for deposits. The published deposit time-band is the binding source; the player should expect the deposit to reflect within seconds. The withdrawal time-band is longer; the player should expect the withdrawal to reflect within the published window.

Cards are a useful fallback for banks that do not support UPI. The deposit time-band is typically a few minutes; the withdrawal time-band is typically a few hours. The published time-bands are the binding source.

Netbanking is the most reliable fallback. The deposit time-band is typically a few minutes; the withdrawal time-band is typically a few hours. The published time-bands are the binding source.

More safety questions

The full safety desk

The safety desk is the platform’s binding source for the KYC, payments, and anti-phishing. The desk is staffed 24/7; the response time-band is published in the help center. The desk is the binding source for the platform’s safety commitments.

The desk publishes the update in the help center; the player should verify the published date before relying on any safety guidance.

A closer look at the KYC documents

The KYC documents are the binding source for the platform’s verification. The KYC documents include PAN, address proof, and a face-match (where used). The documents are the binding source for the player’s verification.

The KYC documents are the binding source for the platform’s compliance. The documents are the binding source for the player’s compliance; the player should always complete the KYC documents before the first withdrawal.

A closer look at the anti-phishing checklist

The anti-phishing checklist is the binding source for the platform’s anti-phishing commitment. The checklist includes: bookmark the official URL, verify the publisher name, verify the file size, never share the password or OTP. The checklist is the binding source for the player’s safety.

The anti-phishing checklist is the binding source for the player’s safety. The player should always follow the checklist; the following is the binding source for the player’s commitment.

The full safety desk

The safety desk is the platform’s binding source for the KYC, payments, and anti-phishing. The desk is staffed 24/7; the response time-band is published in the help center. The desk is the binding source for the platform’s safety commitments.

The desk publishes the update in the help center; the player should verify the published date before relying on any safety guidance.

The full safety archive

The safety archive is the binding source for the platform’s safety record. The archive lists the prior safety advisories with the publication date and the trigger. The archive is the binding source for the platform’s safety record.

The archive is the binding source for the platform’s safety commitment. The player should verify the archive; the verification is the binding source for the player’s safety.

The full KYC walkthrough

KYC is a one-time verification step. The platform collects three documents: PAN, address proof, and a face-match (where used). The PAN is requested at the first deposit above the regulatory threshold. The address proof is requested at the first withdrawal. The face-match is requested at the KYC stage.

The platform’s help center lists the full document set and the acceptable formats. The published list is the binding source; the player should verify the list before submitting any document.

The payment rail decision

UPI is the fastest rail for deposits; cards can take a few minutes to reflect. Netbanking is a useful fallback for banks that do not support UPI. Withdrawals typically return through the same rail as the deposit.

Each rail has a published minimum and maximum per transaction. The platform’s wallet screen shows the rail’s limits before the player confirms. The published limits are the binding source.

A second safety checklist

1. Verify the official URL from the bookmark before any sign-in.
2. Verify the publisher name on the official app store page.
3. Verify the file size on the official app store page.
4. Never share the password, OTP, or full card number with any support chat.
5. Set a deposit limit before the first deposit.
6. Set a session time-band before the first table.
7. Use the platform’s in-app complaint route for any suspicious contact.
8. End the session immediately if the platform’s behaviour changes unexpectedly.
9. Re-verify the published terms every 90 days; the platform may update them.
10. Use the responsible-play controls as a baseline, not a fallback.