Download Exness — app, MetaTrader and the account area that carries funding · United Arab Emirates

How to download Exness

Download guides by device

What the download decides, and what it leaves alone

A desktop terminal, the mobile app and the browser terminal all sign in to the same account number and all read the same balance. None of them is a channel for money: funding lives in the account area, which is why someone who installs nothing at all can still add funds from a browser, and why four installs on four machines do not create four routes to the account.

The practical consequence is that the route survives whatever you do on the device. A transfer already under way is held against the account, not against the copy of MetaTrader on one laptop, and moving from the desktop build to the phone neither speeds it up nor resets it. The platform simply reports the outcome once the balance figure changes.

The currency the account keeps and the currency that travels

An account is opened in one base currency, and every figure read afterwards — balance, free margin, the value of an open position — is expressed in it. A transfer that starts in some other currency has to be restated in that base currency somewhere along the way, and the conversion belongs to the boundary between the two institutions rather than to the client you downloaded.

That is why a credited figure can differ from the figure that left without anything having gone astray: the two numbers are denominated differently. Exness charges $0 for deposits and withdrawals; the institution carrying the transfer sets its own terms on its own side, and no build of the terminal changes them.

A working calendar that belongs to the transfer, not to the screen

A request can be created at any hour, because the account area does not close. The leg between institutions is counted differently: the parties that carry it keep working days, observe local public holidays, and apply a cut-off — a point in the day after which an instruction is picked up on the following working day.

For a trader in the UAE this mostly shows up around the local weekend and public holidays, when an instruction created late is taken up on the next working day at the receiving end. Reinstalling a client, switching devices or clearing a cache does not move that boundary, because it was never held on the device.

Keeping a transfer readable from whichever device you sign in on

1. Note the base currency the account was opened in before sending anything — every later figure, on every install, is quoted in it.
2. Create and follow funding in the account area rather than in the installed terminal: the terminal carries the balance, the account area carries the request.
3. Keep the reference the sending institution issues; it is the identifier that follows the transfer across the leg no screen displays.
4. Write down the amount as it left and the currency it left in, so the credited figure can later be read against it instead of guessed at.
5. Allow for the receiving side keeping working days: an instruction created after its cut-off is taken up on the next one.
6. Read the balance line to confirm arrival, not the order screen — a change in balance is the point where the route ends and trading begins.

Exness charges $0 for deposits and withdrawals; the institution that carries a transfer applies its own terms, and restating the sum in the base currency of the account can also move the figure. Timings described here are general practice rather than a promise for any single transfer.

Where each part of the route actually happens

Downloading a different client changes the last row of this table and nothing above it.

Related Exness pages