Register once, then reach the lobby
Open the form with a mobile number, password, and one-time code, and you can move from first entry to the account area in a few steps.
What we ask on sign up
When you sign up, we ask for only the details needed to create and return to your account: a mobile number, a password, and a code check. That keeps the first login clean and reduces form errors later. You can finish on a phone browser, then use the same login on desktop without rebuilding the
account. If a field fails, our team can check the exact step and help you continue. That makes it easier if you pause and return later.
-
Short setup The form asks for a mobile number, password, and code check first. That gives you a clean start and keeps the first login focused on the details that matter.
-
Same login on every device You can open the account from mobile or desktop with the same credentials. If you change browser later, the login flow still follows the same steps.
-
Faster support checks When you contact us, the team can trace the exact step that failed instead of asking for a long story. That saves time if the code, password, or browser causes trouble.
-
Full lobby access After the account is active, you move straight into the lobby without building a second profile. That keeps your settings, history, and help thread tied to one login.
Your details are protected with encrypted, secure access.
DANA, OVO, GoPay and QRIS
After you finish the register form, we show the local rails in one row so you can add funds without hunting through menus.
DANA
OVO
GoPay
QRIS
Checks that protect your account
Account safety starts at the form. We use encrypted connections, ask for a code check before sensitive changes, and keep login attempts linked to the device you used.
Encrypted form
Your password and mobile number travel over encrypted connections, so the details are not readable while they move between your device and our servers.
Code check
A one-time code confirms that the phone linked to the form is yours before we let you change access details or continue the session.
Device match
When you sign in from a new browser, we may ask for another code. That keeps the account tied to your login path instead of the device alone.
Data minimisation
We keep only the account fields needed for access and support, and we do not ask you to resend the same details every time you return.
Payout match
If you later ask for a payout, the name on the account must match the payment details you used at sign up. That check reduces delays when we look at the request.
Local access rule
Availability stays limited to places where local law permits it, so the register flow and later access both follow the same regional rule.
Register questions we hear most
These are the account questions we answer most often before the first login. They cover the form, the code step, device changes, and what to do if you cannot return to the same session. Each answer stays close to the register flow so you can finish without guessing which screen comes next. If you start on mobile, the same steps still work on desktop.