What MFA does and does not protect
Multi-factor authentication (MFA) adds a second proof to password-based sign-in. It reduces the risk from a stolen password, but phishing and recovery weaknesses can still matter. Completed blockchain transfers generally cannot be reversed by a bank-style chargeback.
MFA protects account access, not every risk at the exchange. Provider compromise or insolvency requires separate consideration. Evaluate custody choices and your ability to secure recovery material before moving funds.
Compare three authentication methods
SMS
Prefer stronger options when available
SMS authentication relies on control of your phone number and can be exposed by a SIM swap. It is generally better than having no second factor, but use a stronger supported method where possible.
Authenticator app
A widely supported option
A time-based authenticator app generates rotating codes without receiving SMS. It avoids phone-number interception, but codes can still be phished and the app or its backup can be compromised.
Security key
Phishing-resistant where supported
A supported FIDO2 security key works through USB, NFC or another compatible connection and binds authentication to the legitimate service. Keep a backup and protect recovery paths.
If you currently use SMS: Switching from SMS reduces exposure to phone-number interception, but does not remove every account risk. Learn about SIM swaps and carrier protections in the SIM-swap guide.
Set up MFA step by step
Interfaces and supported methods vary. Use these steps as a general guide and follow the exchange’s current instructions.
Install a trusted authenticator
Install a supported authenticator from the verified publisher in the official app store. Decide whether you need encrypted synchronization or a local backup, and secure that recovery method.
Open the provider’s authentication setup
Open the exchange’s official security settings and choose its supported authenticator setup. The site will normally display a QR code or setup secret.
Scan the verified setup code
Scan the QR code with the trusted app and enter the current verification code when requested. The code format and interval depend on the service’s implementation.
Protect recovery codes
If recovery codes are provided, store them securely and separately from the phone. Follow the service’s instructions; not every exchange uses the same backup system.
CautionLearn the recovery process before relying on the second factor. Some services let you regenerate codes while signed in; losing all factors can require a lengthy identity-verification process.
Confirm with a current code
Complete the provider’s verification step and check that the method is listed as enabled. Do not assume scanning the QR code alone finished setup.
Review every sensitive account
Enable strong authentication on exchanges and linked email accounts, including accounts with small balances. Also review their recovery methods and active sessions.
Recovery codes: your alternative access
Recovery codes, where provided, offer an alternative when you lose access to an authentication device. Store them securely and learn the provider’s process. Without a working factor or valid recovery method, support may require identity checks and access can be delayed.
Paper
A secure offline record
Treat recovery codes as sensitive account credentials. An offline record can keep them separate from online account compromise; store it securely and follow the provider’s instructions.
Separate storage
Keep recovery material separate from the phone
Choose a secure separate location so one theft or incident does not remove both device and recovery material. Balance availability with the risk of exposing the backup to others.
Digital
Avoid casual screenshots and cloud copies
Photos or notes can be synchronized to other devices or cloud accounts. Understand that exposure before storing recovery material digitally, and prefer a carefully secured offline record.
About authenticator backups: An authenticator’s encrypted backup or synchronization can simplify device replacement, but creates another account and recovery path to protect. Review the app’s current security settings and disable unnecessary device enrollment.
Six practical rules
Review stronger supported methods
If only SMS is available, use it while reviewing the provider’s security and recovery options. Consider a service with stronger authentication, rather than disabling protection before a safe transition.
Protect the linked email account
Email often controls password-reset and recovery requests. Secure it with strong authentication and review forwarding rules, sessions and recovery details.
Consider a separate email address for crypto accounts
A dedicated address with limited exposure can reduce some unwanted contact. It can still leak or receive targeted phishing; use a unique password and strong authentication.
Review account activity periodically
Review whether MFA remains enabled, whether sessions are familiar and whether recovery details changed. Regular checks can reveal a takeover, but may not prevent a rapid loss.
Consider what must remain on the exchange
MFA protects account access; it does not protect against every exchange failure. Decide whether self-custody suits your needs and skills before moving long-term holdings.
Set an anti-phishing code
Enable an anti-phishing email code if your provider supports it. Check which messages include it and verify unexpected messages independently; it is not a universal authenticity guarantee.
MFA protects access to your account, rather than the provider’s solvency. If you choose self-custody, compare suitable devices and learn their backup requirements in the Wallet comparison. To compare exchange features and availability, use the Exchange comparison.
Checklist: set up MFA carefully
- Review supported alternatives to SMS — App-generated codes avoid SMS interception. They can still be phished; choose phishing-resistant authentication where supported.
- Protect recovery codes — Keep recovery codes in a secure offline record and protect access to that record.
- Keep recovery material separate — Store recovery material separately from your phone so losing one does not automatically remove both.
- Protect every sensitive account — Exchanges, email and cloud accounts all deserve strong authentication and secure recovery settings.
- Enable a supported anti-phishing code — If supported, enable the provider’s anti-phishing code and understand which messages include it.
