Register for Dragon Tiger and Cleocatra
Dragon Tiger, Cleocatra and Rocket Crash sit behind one account, so registration gives you a single login for tables, slots and crash games with local wallet setup next.
Your Account Form Before Lobby Access
A complete registration takes the shortest route: username, mobile number, password, and a phone code before the lobby opens. We ask for these fields because the same record is used later for sign-in recovery, wallet matching, and identity checks if your access changes device. After the form is accepted, go to Profile > Account >
Verify Phone if the code did not load automatically. Keep your name format consistent; our team can resolve mismatches faster when your account details follow the same spelling.
-
Clear form path We keep the first form to username, mobile number and password, then show the verification step. That order helps you spot spelling errors before the account record is checked.
-
Recovery built in Your phone number becomes the recovery route if your password fails or a device changes later. We use the same number to confirm account ownership before adjusting login access.
-
Full lobby after approval Once the account is accepted, the lobby opens under one session for Dragon Tiger, Bingo, Fish Hunter and slot rooms. You do not need separate profiles for each category.
-
Profile edits handled If your name format needs correction after registration, send the request through Live Chat or WhatsApp. We check the account record first so future verification does not break.
Your details are protected with encrypted, secure access.
DANA, OVO, GoPay and QRIS Setup
Your wallet setup appears after you create your account, so we can match the account name, phone number, and transaction record before any deposit is credited.
DANA
OVO
GoPay
QRIS
Safety Checks Before You Enter
Registration security starts before you enter the lobby. We protect the form with HTTPS, store passwords in hashed form, and ask for verification when a new device or unusual sign-in pattern appears.
HTTPS form
The register page loads over HTTPS, so your username, phone number and password travel through an encrypted connection. If your browser shows a warning, pause and contact us before continuing.
Hashed password
We do not ask support agents to read or repeat your password. Passwords are stored in hashed form, and recovery uses verification steps rather than a direct reveal of your old password.
Phone verification
A phone code links the account to a reachable number. This helps us confirm access later if you forget a password, change device, or ask for account detail corrections.
Device check
When a new device appears, we may ask for an extra verification step before lobby access continues. The check is there to stop account changes that you did not request.
One-account record
We check duplicate signals during registration because overlapping accounts cause recovery and wallet matching issues. If your account is held, support will ask for details before releasing access.
Data edits
Personal detail changes are handled from the account area or support queue, depending on the field. We compare the request with existing records before updating anything tied to verification.
Register Questions We Hear Often
Registration should feel clear before you share details. The answers below cover the form, phone code, device handoff, and what we check when an account is held. We keep the language practical because these are the same questions our support team handles through Live Chat, WhatsApp and email during the 10:00 to 02:00 WIB service window. If your issue is urgent, include a screenshot without showing your password.