Account access

Sign in, KYC and the first deposit, in the order a reader actually hits them

An adult reader who wants to play a real-money rummy session opens the platform, signs in, completes KYC, and funds the wallet. The login step is the simplest. KYC is the slowest. Funding is the most variable.

Account access

A reader's account, in three steps, with a focus on what to do before the first deposit

An adult reader who wants to play a real-money rummy session opens the platform, signs in, completes KYC, and funds the wallet. The login step is the simplest. KYC is the slowest. Funding is the most variable. The page below walks through each step in the order a new reader will hit them, with realistic time estimates and a note on what to do when something goes wrong.

Step 1 - open the platform

The desk recommends opening the platform in a desktop browser the first time. The mobile app is faster on the second visit, but the desktop flow is the most forgiving for a reader who is also doing KYC. The platform URL is on the app page; the login is at the top of the home page.

Step 2 - sign in

Sign in is by email, mobile number, or platform-issued ID. The desk recommends the email route because it survives a phone change. The mobile route is faster to set up but tied to a number that may change. A platform-issued ID is for the most privacy-conscious reader.

Step 3 - KYC

KYC is a one-time check. The reader submits a government-issued ID, a proof of address, and a bank account that matches the ID. The platform's automated check takes 4-26 hours in the desk's testing. A manual review can take longer if the document image is unclear or the names do not match.

Step 4 - the first deposit

The first deposit is the moment a reader becomes a player. The desk recommends setting a deposit cap, a loss cap, and a session timer before the first deposit. The settings are on the responsible-play page; turning them on takes a few minutes, and the few minutes are worth the time.

What to do if a step fails

If sign in fails, the most common cause is a forgotten password or a recent device change. The platform's password reset covers the first; a contact-support form covers the second. If KYC fails, the most common cause is a name mismatch between the ID and the bank account. The desk recommends resolving the mismatch with a different document, not a third re-submission of the same one.

What the desk is honest about

The desk does not have access to a reader's individual account. The platform holds the data. The desk writes about the steps based on the platform's published materials and the desk's own test accounts. If a step does not match what the reader sees, the reader should contact support and the desk will publish an update.

Before the first deposit

A pre-deposit checklist, in five lines

  1. Set a deposit cap. Match it to your weekly discretionary budget.
  2. Set a loss cap. Half the deposit cap, by default.
  3. Set a session timer. Forty-five minutes is a good default for a first session.
  4. Write the pre-session routine on paper. Time, money, format, table stake.
  5. Read the responsible-play page once. The tools work; the habits make them work.
Reader follow-up

A reader's sign-in playbook, in three steps

Step 1: open the platform. The desk recommends opening the platform in a desktop browser the first time. The mobile app is faster on the second visit, but the desktop flow is the most forgiving for a reader who is also doing KYC. The platform URL is on the app page.

Step 2: sign in. Sign in is by email, mobile number, or platform-issued ID. The desk recommends the email route because it survives a phone change. The mobile route is faster to set up but tied to a number that may change. A platform-issued ID is for the most privacy-conscious reader.

Step 3: complete KYC. KYC is a one-time check. The reader submits a government-issued ID, a proof of address, and a bank account that matches the ID. The platform's automated check takes 4-26 hours in the desk's testing. A manual review can take longer if the document image is unclear or the names do not match.

The reader does not share the sign-in credentials. The credentials are personal. The desk recommends a password manager for the password and biometric for the second factor. A shared credential is a privacy risk and a security risk.

The reader turns on two-factor authentication. The platform supports 2FA through an authenticator app, SMS, or email. The desk recommends an authenticator app. SMS is the second-best option; email is the third. The reader enables 2FA in the account settings.

The reader signs out of devices that are not in use. The platform's account settings show a list of signed-in devices. The reader signs out of devices the reader no longer uses. A signed-in device on a shared network is a privacy risk.

The reader does not save the password in a public browser. A public browser is a shared browser; a saved password is a shared password. The reader uses a private browsing session or a password manager with a per-session unlock.

Desk follow-up

A reader's sign-in troubleshooting walkthrough, in three steps

If the sign-in fails, the reader checks the credentials. The reader uses the password manager, not the browser's saved password. If the credentials are correct, the reader resets the password through the platform's reset flow.

If the sign-in still fails, the reader checks the platform's status page. A platform outage is rare but possible. The reader waits the published timeline and tries again.

If the sign-in still fails, the reader contacts the platform's support line. The reader uses the in-app chat or the email channel. The reader includes the platform's account email, the date and time, and any error message.

The reader does not share the sign-in credentials. The credentials are personal. The desk recommends a password manager for the password and biometric for the second factor. A shared credential is a privacy risk and a security risk.

The reader turns on two-factor authentication. The platform supports 2FA through an authenticator app, SMS, or email. The desk recommends an authenticator app. SMS is the second-best option; email is the third. The reader enables 2FA in the account settings.

The reader signs out of devices that are not in use. The platform's account settings show a list of signed-in devices. The reader signs out of devices the reader no longer uses. A signed-in device on a shared network is a privacy risk.

Reader FAQ

Reader questions, in plain language

Do I need an account to read this guide?

No. The guide is open. An account is only required to play a real-money session.

Can I sign in on more than one device?

Yes. Most platforms allow multiple devices. The desk recommends using the same email address across devices and signing out of devices that are not in use.

What is the difference between KYC and a deposit?

KYC is a one-time identity check. A deposit is a transfer of money into the platform wallet. The two are independent - KYC can succeed without a deposit, and a deposit can succeed without KYC up to a small limit.

Why was my KYC rejected?

The most common reason is a name mismatch between the ID and the bank account. The second most common is a low-quality document image. The desk recommends a high-quality scan and a re-submission with a different document if the first attempt fails.

Can I delete my account?

Yes. The desk's deletion page walks through the steps, including what data the platform retains after deletion.

Ready to compare options?

The desk keeps the same five filters on every review.