Security is a settlement problem
On a trading platform, security is not only about keeping intruders out. It is about proving that every contract settled the way it said it would. Here is how we do both.
Segregated client funds
Client balances sit in accounts separate from our operating capital. They are not lent, invested or used to cover company costs, and they are reconciled daily.
Auditable tick feed
Every index publishes its seed and full tick history. Any settled contract can be replayed against the feed it settled on, by you or by a third party.
Two-factor sign-in
Authenticator apps and hardware keys are both supported. Enabling a second factor also arms a confirmation step on every withdrawal to a new destination.
Encryption in transit and at rest
TLS 1.3 on every connection, including the tick socket. Identity documents and payment details are encrypted at rest with keys held in a managed HSM.
Withdrawal address locking
A newly added payout destination is held for 24 hours before it can receive funds, and the hold is announced by email so an unauthorised change is visible immediately.
Isolated settlement
The settlement service runs apart from the web tier with no inbound public route. A compromise of the front end cannot reach contract outcomes or balances.
Found something? Tell us.
We read every report and we do not threaten researchers who act in good faith. Send details to security@wandafx.example — a proof of concept and the account or endpoint involved is enough to start.
Please do not test against live client accounts, run denial-of-service traffic, or access data that is not yours. A demo account gives you the full surface with none of those risks.