FXTRADING.com may ask you to complete an additional security step before allowing account access, a profile change or a transaction. This helps confirm that the action is being completed by the account holder.
Why might I be asked to verify again?
Customers registered and verified before 2025-09-08 may be asked to complete one or more verification steps again when the current official flow shows an action required. A request may also follow login or account activity that does not match the Profile’s usual usage pattern.
Depending on the current request, this can include the registered email, mobile number, identity, face or liveness check, and Proof of Address. This does not mean that every earlier customer must re-verify or that FXTRADING.com has concluded there was wrongdoing or unauthorized access. Follow only the steps shown in the official Client Portal.
For security, FXTRADING.com does not disclose device, IP, location, risk-score, threshold or detection-rule details. If the flow shows duplicate identity and you own two legacy Profiles, use Client Portal → Service Hub → Create Ticket → Account Verification → Other to request a merge.
What should I do?
Read the message shown in the Client Portal.
Complete the verification method offered, such as email, SMS or an authentication app.
Use the newest verification code and enter it before it expires.
Return to the original action and confirm whether it is now available.
Complete verification only through the official FXTRADING.com Client Portal or application.
Why might the verification method be different from before?
The security step available can depend on the action and the verification methods currently connected to your profile. Follow the method shown for the current action.
What if the mobile-number step says the number already exists?
Before 2025-09-08, mobile-number verification was not part of registration, so the same number may be linked to more than one historical Profile. If a current official re-verification step says the number is already registered or in use, stop retrying. The message alone does not confirm who owns any other Profile.
Sign in to the Profile you are verifying and submit one secure ticket through the path below.
Include the complete message and affected verification step, the mobile number with country code, and the registered email for the current Profile.
List every other registered email that you personally own or remember using with that same number. If you do not remember another email, state that instead of guessing.
State whether you recognize every Profile or email you list. Do not try to obtain or provide another person’s email address.
Client Portal → Service Hub → Create Ticket → Account Verification → Other
Mobile number already exists during re-verification
Provide the actual mobile number and registered-email list only in the signed-in Service Hub ticket—not in ordinary Messenger, Live Chat or email. No attachment is required by default. An optional redacted screenshot of the complete error is allowed. Never attach an identity document, passport, Proof of Address or selfie, and never send a password, one-time code or payment/security secret.
The team must review number ownership and Profile association before deciding the next step. This does not guarantee that the number will be released or moved, that Profiles will be merged, that verification will be approved, or that the case will finish by a fixed time. If you do not recognize an association, say so in the ticket so it can be handled as a security matter rather than an assumed merge.
I cannot access the verification method
For account-specific help, sign in to the Client Portal, open Service Hub from the left navigation menu, select Create Ticket, and choose the category and issue that best match your request.
The verification step keeps appearing or does not complete
Confirm that your device date and time are correct.
Use the newest code received.
Wait until the resend control becomes available before requesting another code.
Sign out, reopen the official Client Portal and try the action again.
Record the exact message and time if the problem continues.
Contact support if the step is unavailable, unclear or continues after successful verification. Never provide a password, one-time code, authentication-app setup key or complete payment credentials.