In the event that security or login codes do not reach your mobile phone while carrying out your transactions on the Arbitex platform, this disruption may generally be caused by instant congestions, GSM operator restrictions, or device settings.
Please check the following steps to resolve the issue:
Initial Controls and Transaction Steps
Instant Congestions: Please wait for a while after sending your code request. In the event that a large number of SMS requests are made consecutively, our system or your operator may temporarily suspend transmissions for security purposes.
Network Control: Ensure that your mobile phone's network signal is strong enough. To refresh your network, you can switch your device to airplane mode for a short period of time and turn it back on.
SIM Card/Operator Change: If you have recently changed your SIM card or ported your number to another operator, the security protocols (SIM Block) of banking and financial institutions may have been activated. You need to contact your GSM operator to enable SMS reception.
Device and Operator Settings Checklist
Number Blocking and Security: Ensure that anti-virus programs, firewalls, spam filters, or call/SMS blocking applications on your phone are not blocking Arbitex text messages.
Operator Restrictions: Having filters such as child locks, corporate restrictions, or family packages in your subscription may prevent bulk SMS reception. Confirm with your operator whether your number is subject to such restrictions.
International Roaming: If you are abroad, check that your line is open to international roaming and foreign short message reception.
Important Information: If your problem persists despite the above controls, you can try the process again from a different browser by clearing your browser's cookies, or through our mobile application.
If you still cannot receive the SMS verification code, you can contact our support team 24/7 via the info@arbitex.com e-mail address so that we can check your account and contact information.
Comments
0 comments
Article is closed for comments.