Secure by design. Not by promise.
Broker credentials, staff access, and every API surface are engineered around one assumption: this platform holds things worth protecting.
Built for prop firms.
What you get. In detail.
Credentials encrypted at rest
Broker account passwords are encrypted in the database and decrypted only for authorized display, so a database leak alone does not leak trading credentials.
Isolated admin API
The staff API is not exposed to the public internet, and public requests are hard-refused at the edge. Trader and admin credentials are issued by separate OAuth applications and are not interchangeable.
Standard auth for every surface
OAuth2 with automatic refresh for client apps; SHA-256-hashed API keys for machine-to-machine integrations. No custom crypto, no shared passwords.
Granular permissions
Capability-level gating on sensitive actions, plus read-only mode for view-only roles.
Audit trails
Account state changes, challenge status changes, scheduled tasks, and bulk email sends are all logged for review.
Accurate IP handling
Real trader IPs are identified behind trusted proxies, so rate limits and login logs bind to the actual person, not to your own infrastructure.
Why firms switch. And what changes.
A prop platform is a target, not just a tool
This software holds broker credentials, controls which accounts may trade, and sits in the approval path for payouts: exactly the assets an attacker wants. Security bolted on after the fact shows up as shared admin passwords, staff panels reachable from the open internet, and no record of who changed what. For a business whose product is trust, that is an existential exposure.
How Fxward is built
Broker credentials are encrypted at rest and decrypted only for authorized display. The staff API is isolated from the public internet, and trader and staff tokens come from separate OAuth applications with disjoint scopes, so one can never be replayed against the other’s surface. Machine-to-machine access uses hashed API keys, sensitive staff actions are capability-gated with a true read-only mode, and account, challenge, task, and email events land in audit logs.
What changes for your firm
You can answer the questions brokers, partners, and serious traders ask: where credentials live, who can act on an account, and what happened when. Incidents that would be catastrophic with shared logins become contained and reconstructable, and security stops being a promise on a slide, because it is inspectable in the product.
The shared admin password vs. layered access. How firms actually get burned.
Credentials
Broker passwords in a shared sheet, or a plaintext database column.
Encrypted at rest, decrypted only for authorized display to permitted staff.
Access
One admin login passed around the team in a group chat.
Per-person seats, capability-gated, with a true read-only mode.
Attack surface
The staff panel on the open internet behind a guessable URL.
An admin API that public requests cannot reach, hard-refused at the edge.
Accountability
Who changed it? Nobody knows, because everyone is “admin”.
Audit trails naming who did what, and when, on every sensitive action.
Common questions. Straight answers.
Encrypted at rest in the database and decrypted only for authorized display to permitted staff. A copy of the database alone is not enough to obtain trading credentials.