Recovering an Account After Losing Your Phone

Exchange account recovery after a lost phone is a race between your paperwork and a stranger’s SIM swap. The account still exists, the balance is still there, and the only missing piece is a second factor that lives on a device you no longer have.

What decides the outcome is what you prepared before the loss. Exchange account recovery is fast when a recovery code or a second registered device exists, and slow when it depends entirely on a support queue and identity documents.

• Recovery codes are the fastest path back in. One unused code usually restores access without a support ticket.
• Get the phone number back first if it was also lost. A number in someone else’s hands is an account takeover in progress.
• Expect a security hold after any reset. Withdrawals are commonly frozen for hours or days, which is a feature.
• Never route recovery through a third party. No legitimate recovery requires your password, your seed or a remote session.

What exchange account recovery can and cannot restore

A venue can restore access to your account because it holds your balance on its books. It cannot restore a self-custody wallet, because there is no account to reset, only a key.

That distinction decides which process you are in. If the phone held an authenticator app for a venue account, you are dealing with a company that has an identity record and a support process. If the phone held a wallet app with keys, the venue is irrelevant and only your seed backup matters.

Within a venue, recovery can restore login, trading and eventually withdrawals. It cannot restore a code you never saved, and it cannot shorten a hold that exists to protect you from exactly the situation you are in.

The three paths back in, and which applies to you

There are three practical routes, and they are not equally fast. Identify which one your setup allows before you open a ticket.

Path one: a recovery code

Recovery codes are single-use strings issued when you enable two-factor authentication. They bypass the authenticator, not the password, so you still need your login credentials.

Most people save them to the same phone they later lose. The fix is to store them offline in a second location, on paper, and to check once a year that the paper still exists.

Path two: a device that is already enrolled

If you registered a tablet or an old phone, its authenticator still generates valid codes, because the shared secret is stored locally and does not depend on the lost handset. Turn off the old device’s notifications remotely, but do not wipe the authenticator until you have used it to regain access.

Path three: the support ticket

This is the slow path, and it is the one that works when nothing else does. Expect identity verification against the details on file, a review period, and a temporary restriction on withdrawals after access is restored.

Submit from an email address you still control and can prove, attach clear images of the document requested, and answer questions precisely rather than quickly. A mismatch between your current address and the one on file is a common cause of delay.

Exchange account recovery, step by step

Work in this order. The first two steps protect the account while you are still locked out of it.

1. Secure the phone number if it was lost with the device. Contact the carrier, suspend the line and ask what is required to restore it to you rather than to a new SIM.
2. Change the password on the email account linked to the venue, from a device you control, and check its recovery settings.
3. Try the fastest path first: a saved recovery code, then a second enrolled device, then any synced authenticator backup.
4. If none work, open a support ticket from the verified email, describing the situation as a lost device rather than a forgotten password.
5. Complete identity verification with documents that match the details on file, and respond to follow-up questions in one message rather than several.
6. Once access returns, re-enrol two-factor authentication on the new device, generate a fresh set of recovery codes and store them offline.
7. Remove the lost device from the trusted device list, and review active sessions and API keys before withdrawing anything.

Making the next loss a non-event

The goal is not to avoid losing a phone; it is to make losing one cost an hour rather than a week. Three habits cover almost all of it.

Enrol two devices, deliberately

Register a second device with the same authenticator secret at setup, and store it somewhere it will still be reachable when your main phone is gone. An old handset kept in a drawer is a legitimate backup if it is charged occasionally and not used for anything else.

Keep recovery codes out of the phone

Paper, in two places, is still the most reliable format for something you use once every few years. A code photographed into the same photo library that syncs to the cloud is not a backup; it is a copy in the same failure domain.

Treat the phone number as a liability

A number attached to an account is a recovery path, and every recovery path is an attack path. Where a venue allows it, remove SMS as a fallback once an app or hardware key is enrolled, and keep the number on file only where regulation requires it.

Recovery is not a feature you enable after a loss. It is a set of artefacts you created months earlier and then forgot about, which is exactly why they still work.