Signing In: Web Terminal and App Side by Side — Indonesia
You log in to Binomo with the email and password you set at sign-up, on the web platform or in the mobile app. Binomo uses its own platform, so there is no separate terminal to install.
Open a Binomo demo →Signing in to Binomo is a change of state on one address rather than a move to somewhere else. While you are signed out the platform draws a form and the public reading material around it; once the credentials are accepted it draws the working screen on that same address, with your account behind it. There is nothing to download and no second window opens. What the platform keeps afterwards is a session - held by the browser you used or by the installed app, created separately on every device, and ended by signing out rather than by closing anything. The balance, the verification state and the record of settled contracts sit on the platform side of that session, so a session ending costs nothing but the next sign-in.
How to log in to Binomo
- Open the Binomo web platform or the mobile app (Android or iOS)
- Enter the email address you registered with
- Enter your password and confirm the sign-in
- Enable two-factor authentication (2FA) if you want an extra layer of security
- Forgot it? Use ‘Forgot password’ to reset it by email in a few minutes
Security & password reset
Never share your password. Reset it from the email you signed up with if you lose access, and be cautious of look-alike pages that are not run by Binomo.
One address, two states of the same screen
The sign-in form is not a lobby you pass through on the way somewhere. The address you open while signed out and the address you work on while signed in are the same address, and what changes between them is only how much of it the platform is willing to draw. Signed out, it is a form. Signed in, it is a working screen with an account attached to it, reached without a download and without anything taking over the window. What that working screen actually contains is a separate subject and belongs to the terminal page.
Reading it as two states rather than two places sorts out the commonest confusion here, because a reader who cannot get past the form has one of two unrelated problems and they are settled in different places. Either the credentials are not being accepted, which is a mailbox question before it is a password question, or the address itself is not loading, which has nothing to do with credentials at all. In Indonesia the second one is worth naming plainly: Binomo is not licensed by the Bappebti, Indonesian authorities have issued warnings and access restrictions, and the legal status page sets out where that stands before any sign-in is worth attempting.
The session belongs to the device; the account does not
Credentials are checked once. What lasts afterwards is the session - the platform's standing permission for this browser, or this installed app, to show you the account. It is created on the device that signed in, and three consequences follow from that which tend to surprise people in the wrong order. A second device signing in receives a second session, never a second account. Closing a window ends nothing by itself. And signing out in one place leaves every other place signed in.
Everything of consequence sits on the far side of that arrangement. The balance, whether identity verification has been cleared, and every contract that has already finished are stored by the platform rather than by the machine in front of you, which is why an ended session takes nothing with it. A contract that is still running is not attached to a session either: it reaches its stated moment and settles there whether or not a screen is open on it, and it is waiting in the record when one is. The device holds a view; it never holds the account.
A browser holds a session differently from an installed app
In a browser the session lives with the stored data that browser keeps for the site. Clearing that data signs you out. A private or guest window begins with no session and leaves none behind when it closes. Several tabs of the same browser share one session, so a second tab is one account seen twice rather than a second sign-in. On a shared or borrowed computer that is the whole story in one line: closing the tab is not signing out, and whoever opens the same address next may land inside the session you left behind.
An installed app keeps its session between launches instead, which is why reopening it usually arrives at the account with no form in the way. A screen that sleeps, a call that interrupts, or a phone that loses signal suspends your view of the account and not the session behind it - the connection is picked up again when the app returns, and nothing on the platform side was waiting for it. Where each front end is installed from is covered on the app page.
The registered mailbox outranks the password
One credential here cannot be reset from inside the platform, and it is not the password. Recovery runs through the address the account was registered with, so whoever can open that mailbox can reach the account regardless of what the password is. That makes the mailbox the stronger of the two things to protect, and it makes losing access to it a support matter rather than a form you fill in - the help panel is where anything of that kind goes, because this guide holds no account data and cannot act on one.
Two-factor authentication is offered as an option and sits in the same part of the picture: it adds a second step at the moment a session is created, not to the screens that follow it. The habit that pairs with it costs nothing at all. End a session deliberately on any machine that is not yours instead of trusting a closed window to have done it, and rehearse the whole sequence on the practice balance first, where an unended session on a borrowed computer is a lesson rather than an exposure.
Opening and closing a session so it does what you think it does
- Open the platform and read which state you are looking at: a form means this device holds no session, while a working screen means one is already open here.
- Type the registered email address - it is the identifier the account is filed under, and the only one this form is looking for.
- Confirm the sign-in and let the screen finish loading before pressing anything on it; the form is replaced in place rather than handing you on to another address.
- Complete the second step if two-factor authentication is switched on, remembering that it guards the creation of the session and not the work done inside it.
- Decide the exit before you start on a computer that is not yours: the plan is to sign out, because closing the tab leaves the session open behind you.
- Finish with the sign-out control rather than the window control - one ends the session, the other only hides it from view.
- Treat the password as the first thing to change if a device is lost, and take anything the form itself cannot do to the help panel, which can see the account this guide cannot.
- Keep the registered mailbox reachable and protected, since every recovery route on the account runs through it.
Sign-in options as published by the platform; confirm the current ones there. Fixed-time trading carries a high risk of losing money.
Where each piece of state is actually kept
| What it is | Kept by | What an ended session does to it |
|---|---|---|
| The balance and the funds in it | The platform, on the account | Nothing - it is waiting at the next sign-in |
| Whether identity verification is cleared | The platform, on the account | Nothing |
| Contracts that have already settled | The platform, on the account | Nothing - the record is there again next time |
| A contract that is still running | The platform, on the account | Nothing - it reaches its stated moment unattended |
| Being signed in on this device | This browser, or this installed app | That is the part that ends |
| Being signed in on your other device | That other device, separately | Nothing - sessions end one at a time |
Described from the way the front ends behave; confirm current details on the platform. Fixed-time trading carries a high risk of losing money.
Two ways of holding one session
| Question about the session | In a browser | In the installed app |
|---|---|---|
| Where it is stored | With the stored data the browser keeps for the site | By the app itself, on the phone |
| Does closing the window end it? | Usually not - a closed tab reopens into the account | No - relaunching arrives at the account |
| What clears it | Signing out, or clearing the browser's stored data | Signing out, or removing the app |
| A second tab, or a second launch | One session seen twice, not a second sign-in | The same session resumed |
| Losing the network for a while | The page reconnects; the session is not the casualty | The app reconnects when the signal returns |
| A private or guest window | Starts with no session and leaves none behind | No counterpart - the app is the signed-in state |
Front-end behaviour as published by the platform; confirm current details there. Fixed-time trading carries a high risk of losing money.