Define the system
Namibia payment journey: Public lists cannot confirm what is enabled for one profile. Use the authenticated Personal Area (PA) as the live source for methods, limits, fees and processing estimates.
| Metric | Record |
|---|---|
| Orders/requests per second | Measured peak/average |
| Round-trip latency | Request, acknowledgement and fill |
| Holding period | Distribution, not label |
| Cost per trade | Spread + commission + slippage |
| Failure behavior | Timeout/reject/restart handling |
| Infrastructure | PC/VPS location and monitoring |
Compliance review
- Read current Client Agreement.
- Describe legitimate market hypothesis.
- Set request/order caps.
- Reject stale prices and abnormal spreads.
- Keep immutable logs.
- Test overload/disconnect.
- Ask Support Hub about ambiguous behavior before live use.
EA overload warning
Exness notes an EA can be disabled when aggressive settings create excessive submissions or irrelevant requests. If it cannot be re-enabled, open Support Hub ticket. Do not create new accounts to evade a control.
Funding economics
High turnover magnifies commission, spread and conversion leakage. Select account/currency only after a same-session cost study; fund no more than the tested margin and drawdown plan permits.
Kill conditions
| Condition | Action |
|---|---|
| Latency outside band | Stop entries |
| Duplicate/state mismatch | Reconcile server |
| Daily loss/commission cap | Stop system |
| Log/clock failure | Disable trading |
| Request rejection spike | Throttle and investigate |
Official source
EA support and excessive-request warning
Frequently asked questions
Does EA support mean any HFT behavior is allowed?
No. Strategy behavior and current agreement still control.
Is scalping automatically HFT?
No. Measure rate, latency and holding time.
What if an EA is disabled?
Review funds/settings/request behavior and use Support Hub if it cannot be enabled.
Should I fund before latency testing?
No. Test demo infrastructure and after-cost feasibility first.