Exness account types: what is visible before you register — Namibia
The names and their published descriptions are readable by anyone. The rest of the decision only becomes visible in the creation form, and part of it only on the account screen itself.
Open Exness Account →A published account-type page and an account-type decision are not the same object. From outside, the names and their descriptions are readable by anyone and identical for every reader. The creation form is the first place the choice becomes concrete — platform, currency, label, practice or live — and the account screen is the first place a type is seen as a number and a server rather than as a paragraph.
Three layers of what a type tells you
- The published list is the same page for every reader: it names the types and describes them, and it says nothing about the person reading it.
- The creation form is where a type stops being a description and becomes a choice — it is filled in once per account, and it is the first screen that reacts to the profile in front of it.
- A list read from outside is a catalogue; the form is an offer, and only the second one is addressed to you.
- Some properties of a type appear only on the account screen: the account number, its server, and the instrument names as that particular account sees them.
- A practice account created in the same place shows both the form and the screen without money being involved at any point.
- A type is chosen per account rather than per person, so the decision is made again each time an account is created rather than once and for good.
What each door tells you about a type
| Door | What it shows about account types | What it still hides |
|---|---|---|
| Published pages, no account | The type names and the short description published for each of them, identically for every reader | Which of those types the profile in front of the screen is actually offered |
| The creation form, registered | The fields an account is created with — platform, currency, label, practice or live | How that account behaves once it is funded and connected |
| The account screen, profile completed | The account number, the server it answers on, and the instrument list as that account sees it | Anything at all about a type that was never created |
What a catalogue is and what it is not
A catalogue is a statement about what exists. It is written once, published to everyone, and it cannot know anything about the reader in front of it. That is a strength when the question is what the types are called and how they are meant to differ, and a limit when the question is which of them will be offered to one particular profile.
The limit is structural rather than a matter of detail. No amount of extra text on a public page can answer a question whose answer is a property of a profile that does not exist yet, which is why the sensible use of the public layer is to narrow a shortlist and stop there.
The form is the first screen that answers back
The creation form is the first place in the sequence where the interface responds to something specific. It presents the fields an account is built from and it presents them as choices, which is a different kind of information from a description: a field that has to be filled in tells you that the property is fixed at creation rather than adjusted later.
That makes the form worth reading as a document in its own right. Going through it once, even without finishing it, converts several open questions into settled ones — and it does so at the second level of access rather than requiring anything further.
What only the account screen can say
Once an account exists it stops being a type and becomes an object: a number, a server it answers on, and a list of instrument names as that account sees them. Two accounts of different types opened from the same profile are two different objects with two different lists, and neither list is visible from the public page that described them.
A practice account is the cheapest way to see this layer, because it produces the same kind of object — a number, a server, a list — through the same screens, and it does so without any money being part of the picture.
Getting as far as possible before registering
- Read the published descriptions and reduce the list of types to the ones that plausibly match the way you intend to work.
- Write down every remaining question and mark the ones that contain the word “my” — those cannot be settled at this level at all.
- Check the measured readings published on this site for the figures that are the same for every reader, so the public layer is fully used before it is left behind.
- Open the creation form and read it as a document: the fields it insists on are the properties fixed at creation.
- Create the account only when the remaining questions are the ones that need an account number to have an answer.
Reading the form is a second-level action, not a commitment: it becomes an account when it is submitted, not when it is opened.
Questions a catalogue cannot answer
| Question as asked | Level that can answer it |
|---|---|
| Which types exist and what are they called | Published pages — no account needed |
| What is fixed at the moment an account is created | The creation form |
| Which types are offered to this profile | The creation form, once registered |
| What is my account number and which server does it answer on | The account screen |
| What are the instrument names as my account sees them | The account screen |
| What will this account do once it holds money | The account itself, in use |
The rule of thumb: a question that would have a different answer for two different readers has left the public layer.