Exness Account Types
Adding another account is four states rather than one action: the record is created, the list catches up, a platform is connected, and only then can the account hold a position.
Open Exness Account →Between pressing create and placing a first order on a new account there are four states, and only one of them is slow. The record itself appears immediately, the account list catches up a moment later, and connecting a platform to it takes as long as typing a few fields. Everything that feels like waiting sits in the last state, which depends on something outside the account entirely.
The four states a new account passes through
- Created — the record exists. This part finishes while the page is still open and is the only part that is genuinely instant.
- Listed — the new account appears alongside the others. A list is a view, and views refresh on their own schedule, so a short absence after creation is the view catching up rather than a failure.
- Connected — a platform has been given the account and its server. Nothing about the record changes here; what changes is which program can see it.
- Ready — the account can hold a position. This is the only state that depends on something outside the account, and therefore the only one with an unpredictable duration.
- The states are strictly ordered, and the third can be repeated as often as needed: one record, several programs, no new record each time.
- The first three together are usually the shortest part of the sequence; almost all of the waiting sits in the fourth.
What each state waits on
| State | Finishes when | Usual unit | What it does not wait for |
|---|---|---|---|
| Created | The form is accepted | Instant | Any check already completed for an earlier account |
| Listed | The account list next refreshes | Seconds to one refresh | Anything you type |
| Connected | A platform is given the account and its server | Minutes | The other accounts, which stay connected throughout |
| Ready | Funds arrive from wherever they started | Outside the account's control | The three states above, which are already finished |
Created is not the same as visible
The moment a new account record is written is the quickest event in the whole sequence: it is a single write, with nothing to check and nobody to consult. Anything already verified once belongs to the person rather than to the account, so it is not repeated for the second, third or tenth record.
What follows immediately afterwards causes more confusion than the wait itself. A list of accounts is a view built at a particular moment, and a view built a second before a record existed will not contain it. Reopening the view is what fixes that, and it is not the same as creating the record again.
The failure mode worth avoiding here is duplication. A record that has been created and is not yet visible looks exactly like a record that was never created, and the instinct to press create again produces two accounts where one was wanted — a mess that takes far longer to sort out than the second it saves.
Connecting is per program, not per account
Connecting is the state people mistake for part of the account creation. It is not: it is a separate act performed by a program, using an identifier and a server entry that the account already has. The same record can be connected on a desktop, on a phone and in a browser, and each of those is its own short act.
Because connecting belongs to the program rather than to the record, it is repeatable, undoable and harmless. Disconnecting a platform does not touch the account, and connecting it on a second machine does not disturb the first. This is the only state on the list that can be redone without consequence.
It is also the only one bounded by your own equipment. A slow connection or a machine busy with something else makes this step longer; nothing at the broker's end is involved once the identifier and server are correct.
Ready is the only state with an unpredictable clock
An account that exists, is listed and is connected still cannot hold a position until it has something in it. That last state is the only one whose duration is not the account's to determine, because it waits on whatever is moving the funds and on that party's calendar rather than on the trading account.
This is why the whole sequence feels slow when three quarters of it is instant. The three fast states are invisible in retrospect; only the slow one is remembered, and it gets attributed to account opening as a whole.
The practical consequence is about ordering. Doing the three fast states in advance, before the moment they are needed, moves the only unpredictable state to the front of the queue instead of the back, and leaves nothing but the wait itself.
Several accounts, one clock each
Additional accounts do not queue behind each other. Each one runs its own four states, and the fast states are fast regardless of how many records already exist. Creating a second account does not slow the first, and a first that is still waiting does not hold up a second.
What does not repeat is anything that belongs to the person rather than to the record. That work was done once, and it is the reason the second record takes a fraction of the time the first one appeared to take.
The one thing that genuinely accumulates is attention. Every additional account is another thing to keep track of, another list entry to read, and another connection to remember — a cost measured in later minutes rather than in the minutes it takes to create.
Getting a new account to ready without a wasted wait
- Create the record and stop. It is written the moment the form is accepted, and nothing further is pending on it.
- Refresh the list rather than creating again. An account missing from a stale view is a view problem, not a record problem.
- Note the identifier and server before leaving the account area — both are needed by every program that will connect to it.
- Connect the platforms you actually use, one at a time. Each connection is independent and none of them affects the record.
- Start the funding step first if it is the state you need most, since it is the only one whose finishing time you do not control.
- Treat the account as ready only when it can hold a position, not when it appears in the list — the two moments are usually far apart.
The order of the states is fixed; only the third can be repeated. Current details for any account are shown in the account area.
What is repeated for a second account and what is not
| Item | Repeated per account | Done once for the person |
|---|---|---|
| Creating the record | Yes — a moment each time | — |
| Being identified | No | Yes |
| Appearing in the account list | Yes — one refresh | — |
| Connecting a platform | Yes, and per program too | — |
| Getting funds in | Yes, on its own clock | — |
| Keeping track of it afterwards | Yes, and it accumulates | — |
The middle column is where the minutes go; the right-hand column is why a second account is quicker than the first.