The FXBO Mobile App connects to the broker’s CRM through the same Client API used by the web Client Area, so the protections a broker sets in the CRM also apply to app users. Each broker can set these up to match their own risk policy:
- Two-factor authentication (2FA): Brokers can require 2FA for client logins, so a stolen password isn’t enough to get into an account.
- Login rate limiting and CAPTCHA: The number of login attempts can be capped, and the Client API can require a CAPTCHA. This blocks automated password-guessing and bot traffic.
- Session controls: Brokers can set an API session lifetime and auto-logout after inactivity, which limits the risk if a device is left unlocked.
- Transaction confirmation: Transfers and withdrawals can require extra confirmation. Time-based one-time passwords (TOTP) are the recommended method.
- Cooling-off period: After security-sensitive changes such as a password reset, withdrawals and transfers can be paused for a set time. This protects funds if an account has been compromised.
- New-IP login alerts: Clients can get an email when their account is accessed from an unfamiliar IP address.
- Restricted API access: Brokers can limit which domains are allowed to send requests to the CRM.
Our security recommendations guide rates each of these settings and gives the recommended configuration, so brokers can get the strongest protection while keeping the app easy to use.
Was this article helpful?
Yes
No