A user changes their phone number, switches to a new device, or stops receiving SMS verification codes and suddenly cannot complete a Revolut login. The app’s security model—built around phone number authentication rather than traditional passwords—works well for most daily transactions but creates a specific recovery problem when that phone number is no longer accessible. Understanding the restore pathways, preparing for common scenarios, and knowing which support channels actually resolve these issues can mean the difference between regaining access within hours and losing contact with funds for weeks.

Revolut’s multi-factor authentication system and device binding controls exist to protect accounts from unauthorized access, but they can also lock out legitimate users during legitimate transitions. The fintech platform serves over 70 million personal users globally across iOS and Android, making it a primary banking interface for many people. When access breaks, knowing the exact steps to follow—and which steps will not work—becomes essential. This guide covers the practical procedures for restoring Revolut access after phone number changes, lost devices, SMS delivery failures, and the recovery options available when standard authentication flows become unavailable.

How Revolut’s phone-based authentication creates recovery challenges

Revolut’s security architecture relies on phone number verification rather than the password-recovery mechanisms common in traditional banking. During a standard Revolut login, users enter their phone number, receive a one-time SMS code, and confirm their identity using biometric authentication (Face ID or fingerprint) or a PIN. This approach eliminates the need for users to remember complex passwords, reduces phishing exposure, and ties authentication to device possession. However, it creates a dependency: if the phone number changes, the SMS delivery chain breaks, and the account becomes temporarily unreachable through normal channels.

Device binding compounds this issue. Revolut registers each device during setup and associates it with the account. If a user logs out, loses a device, or switches to a new phone before updating their account details, the new device will not automatically be trusted. The app will still request SMS verification, but without access to the old phone number or the old device’s biometric data, the verification loop cannot be completed. The account remains functional—the funds and balances are not lost—but the application becomes inaccessible from the new device.

Multi-factor authentication also plays a role. Biometric verification on the original device can sometimes bypass SMS when the device is already recognized. If that device is lost or wiped, or if biometric data is unavailable for any reason, SMS becomes the only recovery path. Users who did not set up a PIN fallback or did not note their account’s registered phone number before making a change may find themselves unable to authenticate using any available method.

The critical lesson is that Revolut password recovery in the traditional sense—resetting a password through an email link—does not exist. Revolut does not store passwords and does not send recovery emails. Every restoration process must ultimately verify control of the phone number or involve direct contact with support. Understanding this distinction prevents users from waiting for email recovery links that will never arrive or attempting password resets that the platform does not support.

Steps to restore Revolut login after a phone number change

If a user has actively changed their phone number and wants to continue using Revolut, the process should begin before the old SIM card becomes completely inaccessible. Open the Revolut app on the device where it is currently working, navigate to the account settings (usually under “Profile” or “Security”), and locate the phone number verification section. Most accounts allow users to update their phone number directly through the app. Enter the new phone number, and Revolut will send a confirmation code to the new number. Complete this verification before discarding the old SIM card or deactivating the old service.

Once the new phone number is registered in the account settings, the next Revolut login from any device should use the new number for SMS verification. The user enters the new phone number, receives the code on the new phone, and completes authentication as usual. Device binding should transfer automatically; the account remembers the device fingerprint, and biometric verification will work once the user has logged in at least once and the device is recognized again.

Problems arise when the phone number change happens outside the app—when a carrier switches the number without updating Revolut first, when a user discards the old phone before updating the app, or when the transition happens across two devices simultaneously. In these scenarios, attempting to log in with the new phone number will still trigger the SMS code request, but the code will be sent to the old number, which the user no longer controls. The app may also show an error indicating that the phone number is not registered, or it may send the code but the user cannot receive it because the old SIM is no longer active.

The immediate recovery step is to contact Revolut support through an alternative channel. The in-app support chat may not be accessible if the account is locked, so the user should use the contact information available on the Revolut website or the official mobile app’s help section. Many users report success by explaining the situation (phone number changed, now unreachable) and providing account verification through other means: email address associated with the account, the last four digits of a registered card, personal details from verification during signup, or recent transaction history. Revolut’s support team can manually update the phone number in the backend and send a confirmation to the new number, allowing the user to resume normal logins.

Dealing with Revolut SMS verification failures and timeouts

Sometimes the phone number is correct, the device is right, but the SMS code simply does not arrive. This can happen due to network carrier delays, blocking rules on the user’s phone, or infrastructure issues on Revolut’s side. The first troubleshooting step is to wait. SMS delivery is not instantaneous, and codes can be delayed by 30 seconds to several minutes, particularly for users in regions with slower mobile networks or during carrier maintenance windows.

If the code does not arrive after five minutes, check for SMS filtering. Some phones automatically sort SMS messages into folders, and verification codes may land in a spam or filter folder rather than the main inbox. On Android, check the Messages app’s “Spam” tab or any custom filtering applied through the carrier. On iOS, verify that the phone number receiving the SMS is correct and that the phone has an active data connection (even though SMS does not require data, the phone needs to be active in the carrier’s network).

Revolut also implements timeouts on SMS codes. The code typically expires after 10 minutes, and requesting a new code invalidates the previous one. If a user receives a code but delays entering it, the code will no longer work. The solution is to request a new code immediately, which will send another SMS within one minute. If multiple attempts fail to deliver a code, the user should try requesting a code through the alternative method if available: some users report that switching between SMS and alternative verification (such as biometric if the device is already trusted) can sometimes bypass temporary SMS delivery issues, though revolut login consistently relies on phone verification as the primary method.

For persistent SMS failures, the user should verify that their phone number is correctly entered in the Revolut app settings and check with their mobile carrier that SMS from short codes (the number Revolut sends from) is not being blocked. Some carriers block international SMS by default, and Revolut’s SMS often originates from a service provider’s number rather than a local one. Enabling international SMS reception in carrier settings or contacting the carrier’s support may resolve the issue. If these steps do not work, the situation requires support intervention, and the user should reach out through alternative channels rather than repeatedly requesting SMS codes.

Accessing your account after losing your device

Losing a phone or permanently switching devices before completing an app reinstall creates a different recovery scenario. The old device is gone, so biometric authentication is impossible. The new device has never logged in, so device binding does not apply. The user enters their phone number into the app on the new device, receives the SMS code, and enters it correctly—yet the app still does not authenticate. This often happens because Revolut’s device binding mechanism considers the new device “untrusted” and requires additional confirmation that the user is making an intentional change rather than an attacker attempting to gain access.

When this occurs, after submitting the SMS code, the app may display a message indicating that the device cannot be authenticated or that support intervention is required. Some users are offered the option to approve the new device through a push notification on the old device (if it still exists and has power), but if the device is lost, this option is not viable. The user should immediately contact Revolut support, explain that they have lost their device and need to regain access through a new one, and provide verification details. Revolut will review the account and the login attempt, confirm the user’s identity through security questions or identity verification, and manually approve the new device for authentication.

This process typically takes between a few hours and one business day. Users should provide support with clear information: the phone number associated with the account, the approximate date the device was lost, the new phone number or device they are attempting to use, and any identifying details from the account (email address, date of birth, last card used, or recent transactions). The more specific the information, the faster the support team can verify identity and approve the new device. Once approved, the new device will be registered in Revolut’s backend, and future Revolut SMS verification attempts will complete normally.

Using biometric and PIN authentication as fallbacks

Revolut allows users to set a PIN as an alternative to SMS verification on recognized devices. This PIN—separate from any card PIN—can serve as a fallback when SMS is unavailable or when the device is already trusted. To set up a login PIN, go to the account settings, find the security section, and enable “PIN Login” or a similar option (exact labels vary by region and app version). The PIN must be between four and twelve digits and should be distinct from personal information or obvious sequences.

Once enabled, a PIN can sometimes bypass the SMS code requirement on a trusted device. However, this only works if the device was previously authenticated with SMS and is stored in Revolut’s device registry. A completely new device, even if the phone number is correct, will still require SMS verification for the initial login. After that first login on the new device, the PIN can be used for subsequent sessions.

Biometric authentication (Face ID on iOS and fingerprint on Android) works similarly. It speeds up authentication on trusted devices but cannot replace the initial phone number and SMS verification when logging into a new device or after a logout. Users should understand that biometrics are a convenience layer, not a backup authentication method. If biometric data is not set up or if the user switches devices, SMS and phone number verification remain the foundation of account access.

The practical recommendation is to set up both a PIN and biometric authentication on the primary device used for daily Revolut access. This provides options: if one method fails, another remains available. However, users should recognize that none of these methods replace proper backup practices. If a PIN is forgotten and biometric authentication is unavailable, SMS verification becomes mandatory, and losing access to the registered phone number will still require support intervention.

Account verification and identity confirmation during recovery

When support is required to restore Revolut access, the support team must verify that the person requesting access is the legitimate account holder. This verification process protects against unauthorized account takeovers but can sometimes create friction during legitimate recovery scenarios. The support team typically asks for several pieces of information that only the account owner would know: the email address associated with the account, the full name used during signup, the date of birth, the country of residence, details about registered cards, or recent transaction amounts.

Users should be prepared to answer these questions accurately during a recovery chat or call. Revolut may also reference the identity verification documents submitted during the original KYC (Know Your Customer) checks at signup. If the account was created years ago and personal details have changed (address, phone number provider, etc.), users should inform support and provide the details as they were registered at the time the account was opened, not the current details.

In rare cases where the account holder cannot provide sufficient information to verify identity—perhaps because the account was set up through a different email that is no longer accessible—Revolut may require additional steps. This could include re-uploading identification documents, providing copies of old transaction statements, or confirming details through additional security questions. This process exists to protect funds from unauthorized access, and users should cooperate fully rather than viewing it as obstruction. The verification typically completes within one to three business days.

Preventing future access loss through proactive security measures

The best recovery is the one that never becomes necessary. Users can reduce the likelihood of access loss by setting up multiple recovery options and keeping them current. First, ensure that the phone number registered in Revolut settings matches the SIM card currently in use. Before changing phone numbers or carriers, update this information in the app rather than waiting for an access failure to force the update. Second, enable both a login PIN and biometric authentication on the device. This creates redundancy: if SMS delivery fails, the PIN or biometric can still work on a trusted device.

Third, verify that the email address on file is one the user can access indefinitely. While Revolut does not use email for primary authentication, it may use email for support communication, password recovery communication (if the platform ever implements password-based login), or other account notifications. Ensure that this email is active and regularly checked. Fourth, consider writing down or securely storing information about the account: the registered phone number, email, and the last four digits of a primary card. This information is non-sensitive but can speed up support interactions if access is lost.

Fifth, before major life changes—relocating to a different country, switching phone providers, or upgrading devices—plan the Revolut transition. Complete any necessary account updates, verify that the current device can still log in using Revolut login credentials, and document the process. If the move will involve a phone number change, make that change in the Revolut app before the old SIM becomes inactive. Users who follow these steps are unlikely to encounter access loss, and if they do, the support team will have accurate information on file to accelerate recovery.

Understanding what support can and cannot do

Revolut support can update account phone numbers, approve new devices for authentication, verify account identity, and grant manual access in exceptional circumstances. Support cannot reset or recover SMS codes that have already expired, change the email address through the support channel alone (users should do this themselves in account settings), or restore access if the user cannot verify their identity through standard security questions. Support also cannot recover access to accounts where the holder has explicitly closed or frozen the account for security reasons or where there is a legal hold or compliance investigation.

Support response times vary by region and issue complexity. Issues related to Revolut account access are generally prioritized, but during high-volume periods or in less-served regions, resolution may take several days. Users should not delete the Revolut app or create a new account in an attempt to regain access; doing so can create duplicate accounts that complicate support resolution. Instead, users should contact support through the official channels listed on the Revolut website or within the app’s help menu, describe the situation clearly, and wait for the support team to investigate and resolve the issue.

The critical point is that Revolut support is the only reliable path to account recovery once standard authentication methods have failed. Third-party services, websites claiming to offer account recovery, or individuals claiming to represent Revolut outside of the official channels should not be trusted. Phishing scams frequently target Revolut users, posing as support and requesting account details, PINs, or card information. Legitimate Revolut support will never ask for a PIN, password (which does not exist), or full card details through unsolicited channels. Users should initiate contact through the official app or website, never through links or contact information provided by unknown sources.