Authenticator code keeps getting rejected? Check the phone clock before anything else
You enabled two-step login on your new exchange account, everything worked, and a week later every six-digit code is rejected. It feels as if the account is broken or someone changed your settings. Far more often the cause is mundane: authenticator codes are calculated from the current time, and if your phone's clock has drifted by more than a short margin, the code it shows no longer matches the one the exchange expects. Fixing the clock usually fixes the code within a minute.
Why the clock matters
Authenticator apps generate a new code every thirty seconds from a secret shared during setup and the current time. The exchange does the same calculation on its side. If the two clocks disagree, the codes differ. Phones normally set the time automatically from the mobile network, but this can be switched off, confused after travel across time zones, or broken by a battery that ran completely flat. Dual-SIM phones and some budget models are particularly prone to small drifts.
Fixing it on Android and iPhone
On Android, open Settings, find Date and time and switch on automatic date and time and automatic time zone. Google Authenticator also has a time correction option in some versions under its settings menu. On iPhone, go to Settings, General, Date and Time and turn on Set Automatically. Restart the authenticator app afterwards and wait for a fresh code before typing it. Enter the code as soon as it appears instead of in its last few seconds.
If the time is right and codes still fail
Check that you are reading the entry for the right account. Many people have several entries with similar names after setting up more than one exchange, or a leftover entry from a deleted account. Look at the label and the email shown under it. If you recently reinstalled the authenticator or moved phones without transferring entries, the old secret is gone and the codes cannot match; use the backup key you saved at setup or the exchange's two-step reset process in its help centre.
Prevent the next lockout
When you set up any authenticator, store the setup key or backup codes offline, somewhere other than the phone. Label each entry clearly with the exchange name and your email. Consider adding a passkey as well where the exchange supports it, since passkeys do not depend on matching clocks. And never send a code to anyone who contacts you claiming the account needs fixing; a real support agent does not need your codes.
Risk boundary: Safe Crypto Signup
Digital assets are volatile and derivatives can amplify losses. This website has no login, wallet connection, deposit form or customer-support chat. A referral link only records attribution; it does not guarantee access, pricing, rewards, approval or investment results. Availability can differ by residence, legal entity and product, so no regional access is assumed from language or branding alone.
Scenario checkpoint
- Turn on automatic date, time and time zone on the phone that runs your authenticator.
- Wait for a fresh code and enter it immediately rather than in its last seconds.
- Confirm you are reading the authenticator entry with the right exchange name and email.
- Store your setup key or backup codes offline in case the phone or app is replaced.