Independent Exness partner guide
Deposits and withdrawals when the account is open on more than one screen
A payment is usually begun in one window and finished in another, and the two are rarely the same object. Underneath them is a single record of what has been asked for and what stage it has reached. This page follows a payment through that arrangement: which of the open windows can move money at all, why one of them can be wrong about the balance for a minute without being broken, and why a confirmation that turns up on the wrong screen is not a signal to start over.
Two lists worth keeping apart
What belongs to the account, and what belongs to one window only
Nearly every puzzle on this page dissolves once these two lists are separated. Almost everything that matters sits on the first, which is why the arrangement is far less fragile than it looks from a machine that has just been switched off mid-payment.
Held by the account, read by every window
The balance. The transactions and the stage each has reached. Anything saved earlier for paying with, and whether the identity check has been completed. None of it is stored on a machine, none of it is copied between machines, and all of it reads identically from a laptop opened today and a handset opened tomorrow.
Held by one window and nowhere else
The tab that is open and where it has scrolled to. The moment of its last refresh. Whatever that particular browser was allowed to keep about signing in. Closing the window costs the whole of this list and nothing whatever from the other one, which is the reason a dead battery mid-payment is an inconvenience rather than an incident. Where each sign-in is held →
The line between the lists explains the odd cases too. A window opened for the first time this year already knows everything on the upper list, because it was never the window's to know; and a window that has been sitting open all afternoon may be wrong about exactly one thing, which is the figure it last asked for.
Where the answer comes back to
The confirmation travels to the account, not back to the screen that asked
A confirmation step is addressed to the account's own contact details — the address and number registered with it — rather than to the window the request was typed into. A payment begun in one place is therefore finished wherever the confirmation lands, and the two need not be the same object at all.
-
Start it wherever the Personal Area is already open
Signing in on the official exness.com, opening the deposit or withdrawal section and choosing an option and an amount. Nothing about this step is affected by what else is signed in elsewhere at the same time.
-
Expect the confirmation on the account's channel
It arrives at the registered contact details for the account. The window that asked for it does not receive it and does not need to; it waits, and it does not have to be closed.
-
Finish it in the window that is still waiting
The request is one request. Filling in a fresh form somewhere else because the confirmation appeared on something else is how one payment becomes two, and the record in the Personal Area is where that is checked before anything is repeated.
Three arrangements that are perfectly normal
- Started in a browser, confirmed from a message elsewhere. The account owns the channel; the browser owns nothing but the form.
- Requested in the Trade app, checked afterwards in a browser. Both read one record, so both show the same request at the same stage.
- Two windows open on the same account while a payment runs. Nothing is duplicated by that. Only a second submitted form creates a second payment.
Why two windows can disagree for a minute
A new balance reaches each signed-in program at its own next refresh
A credited deposit does not travel outward to the programs; the account is updated, and each signed-in program picks the new figure up when it next asks. Those moments are not synchronised, so a laptop terminal and a handset can show two different numbers briefly. That is a difference in reading times, not a difference in accounts.
What to do about it
Very little. The window on the newer figure is the one that has asked more recently. A terminal that has been left idle catches up on its own, and reconnecting it is enough where patience is in short supply — nothing is corrected by signing out and back in.
What settles the question
The record kept by the Personal Area. It shows each deposit and withdrawal with the stage it has reached, and it is the version to read when two windows disagree — not because the terminals are unreliable, but because they were built to show prices, not to explain payments.
Trading is risky and may not be suitable for everyone.
Money out, seen from anywhere
A withdrawal requested on one screen can be followed from any of them
The request belongs to the account, which means it survives the thing that made it. A machine can be shut down, an app closed, a browser tab abandoned; the withdrawal continues and can be looked at from something that had nothing to do with sending it.
The majority of withdrawals are processed automatically, providing quick, 24/7 access to funds.
Processing times may vary depending on the chosen payment method.
What that changes in practice
- Nothing has to stay open. The window that submitted the request has no further part in it. Leaving it running does not make anything happen sooner.
- Following it is not a new request. Opening the Personal Area somewhere else and reading the entry is a read, not a resubmission — a distinction worth being sure of before anything is filled in twice.
- An idle window is not a stalled request. A terminal left open beside the payment shows what it last asked for; the entry in the record moves on whether or not anything is watching it.
Looking for the software rather than the money screens? The platform board routes each device from the home page.
Quick answers
Where the payment is, and which window can see it
Two windows show different balances. Which one is wrong?
Probably neither. Each signed-in program shows the figure from its own last refresh, and those moments are not synchronised, so a gap of a minute between a laptop and a phone is ordinary. A terminal that has been idle catches up without any intervention.
The confirmation appeared on something that had not started the payment. Is that a fault?
It is the expected behaviour. Confirmations are addressed to the contact details registered against the account, not to whichever form submitted the request, so the two routinely sit on different objects. The waiting form is finished as it stands.
Do payment details added during one payment have to be added again on the next screen?
No — they sit on the upper of the two lists above. Whatever was saved earlier is offered again regardless of what is being used to look at it, and no window has to be set up before it can be useful.
Can a withdrawal be followed from a window that had nothing to do with sending it?
Yes, and that is the practical point of the arrangement. The request lives on the account, so it is visible from any signed-in window — including one opened after the request was already in flight, on a device that was switched off at the time.
One account, one Personal Area, as many windows as suit
Add screens freely: the count changes nothing on the upper list above, and everything it changes belongs to windows that can be closed without consequence. Full registration walkthrough →
Open Exness AccountThe button opens the official exness.com through this site's partner route, on whichever screen it is tapped. Trading accounts, login, and support all live there.