Some customers using Apple Safari browser may experience difficulties when entering the 6-digit verification code for two-factor authentication (2FA) when logging into the FXTRADING.com Client Portal.
Problem Overview
Checks before changing settings
Record the affected environment
A code-entry symptom alone does not identify a browser defect or a platform compatibility cause. Record the device, operating-system and browser versions, affected step and exact error before drawing a conclusion.
Separate AutoFill features
Try entering the current verification code manually on the official sign-in page. Contact-information AutoFill and verification-code AutoFill are different features; changing contact-information options is not a confirmed repair for verification-code entry.
Describe the input symptom
If the field does not accept digits or the keyboard does not appear, record which behavior occurs. A screenshot with private information hidden may help. Never share the verification code or password.
Solutions
Option 1: Use Alternative Browsers
As a troubleshooting step, try a current supported version of Google Chrome, Firefox, or Microsoft Edge through the official site. Compatibility depends on the browser and operating-system versions, device, settings, extensions, network, and current platform status, so changing browsers does not guarantee login success or a smooth session.
Option 2: Safari Browser Adjustments
If you prefer using Safari browser, you can try the following actions:
Update Safari: Ensure you are using the latest version of Safari browser, as Apple frequently fixes known compatibility issues in updates.
Review AutoFill settings:
On current iOS, inspect Safari’s contact-information AutoFill settings:
Select Settings.
Select Apps.
Select Safari.
Select AutoFill.
These controls concern contact information. Do not disable account verification to troubleshoot code entry.
On macOS:
Select Safari.
Select Settings…
Select AutoFill.
Then uncheck the related options.
Review browser data options:
On current iOS, inspect the available Safari data controls:
Select Settings.
Select Apps.
Select Safari.
Do not select Clear History and Website Data simply to troubleshoot code entry. That action removes browsing history, cookies and cache, can require signing in again, and does not change AutoFill information. Establish the exact need and scope before deleting data.
On macOS, if you decide to reset site data:
Select Safari.
Select Settings…
Select Privacy.
Select Manage Website Data…
Search for the official FXTRADING.com domain you are using, select only its entry, then choose Remove. This can sign you out and may affect related apps. Do not select Remove All or clear all browsing history just to troubleshoot code entry.
Review privacy and content-blocking settings: An extension or content blocker may interfere with the verification field. Test a private window or temporarily pause only a trusted extension for the official FXTRADING.com domain, then re-enable it after testing.
Do not disable browser or device security protections. If the issue continues, use another current supported browser or the official mobile app and record the browser, operating system, device, step, and exact error. Never share the 2FA code.
Option 3: Use the FXTRADING.com Trading App
You can also try the current official mobile app downloaded from the official Client Portal or app store. App behavior depends on its version, the operating system, device, permissions, network, and platform status; it does not guarantee login success or greater security.
Frequently Asked Questions
Q: Does this symptom prove that only Safari is affected?
No. A comparison requires the actual browser and operating-system versions and the device conditions. A code-entry symptom in Safari does not establish that other browsers are unaffected.
Q: Does FXTRADING.com plan to fix this issue?
FXTRADING.com reviews compatibility reports and may update guidance or platform behavior as browser releases change. A particular fix or date is not guaranteed; report the exact browser, operating system, device, step, and error through the current official support route if the issue continues.
Q: Is it safe to use other browsers?
Use only current official browser releases on a trusted device and connection. Security also depends on patches, extensions, the device, network, and session; a browser name alone does not make access safe.
Q: Will this issue affect my account security?
A code-entry symptom alone does not prove that the account is compromised, but it cannot rule out a security issue. If you see an unfamiliar login, unexpected 2FA prompt, changed details, or suspect access by someone else, stop and use the current official security support route. Otherwise, try the troubleshooting steps and check the current result.