revolut login<\/a>, the app must send a request to Revolut’s servers to generate a one-time code. That code is then delivered via SMS to the phone number associated with the account. In airplane mode or any environment where the device has no internet access, this handshake cannot occur. The initial request itself fails because the app cannot reach the server, and SMS delivery is impossible without the user’s device having at least temporary connectivity to the cellular network.<\/p>\nDevice binding compounds this requirement. Revolut stores a record of which devices have been authenticated, along with cryptographic identifiers and trust states. When a user attempts to log in from a new or unrecognized device, the system must contact the server to verify the device against stored records. Without internet connectivity, the app cannot retrieve that information or validate the new device’s credentials. This is an intentional security measure: it prevents a compromised or stolen device from authenticating itself offline, assuming it somehow captured the correct cryptographic material.<\/p>\n
Biometric authentication\u2014fingerprint or Face ID\u2014operates differently. The biometric scan happens entirely on the device and does not require internet during the scanning phase itself. However, biometric authentication alone is not sufficient for Revolut login. It must be paired with the server-side verification of the device and the code delivery step. A user cannot complete a full authentication cycle using only biometrics while offline. The biometric is one factor in a multifactor system, not a standalone authentication method.<\/p>\n
The security implications are deliberate. If Revolut allowed offline login using only cached credentials or biometrics, a lost or stolen device could be accessed indefinitely without alerting the account owner or triggering fraud detection. By requiring a live server connection, Revolut ensures that each login attempt can be checked against current account status, device blocklists, and fraud signals. A user who reports a device as lost can have it remotely logged out immediately; offline authentication would circumvent that protection.<\/p>\n
What works offline once you are already logged in<\/h2>\n
The critical distinction is between logging in for the first time and maintaining an active session. If a user successfully completes Revolut authentication while connected to the internet, the app stores a session token on the device. This token represents proof that the user has recently passed all authentication checks. As long as that token has not expired and the session remains valid, the app can display certain information and functions without requiring the internet.<\/p>\n
The scope of offline access is narrow. A logged-in user can typically view their balance, transaction history (to the extent it was cached), card details, and account settings that are stored locally on the device. The app may also allow users to browse investment portfolios, crypto holdings, and savings vaults if that data was recently synced and is still available in the device’s local storage. Some spend controls, such as disabling a card or checking fraud alerts, might be accessible depending on how Revolut’s offline mode is implemented.<\/p>\n
What absolutely requires internet is any action that modifies account state or moves funds. A user cannot send money, initiate a card payment, transfer between accounts, or change security settings while offline. These operations require real-time communication with Revolut’s servers to verify sufficient balance, check fraud rules, record the transaction, and settle it against Revolut’s payment rails. Even simple account changes such as updating an address or phone number require server confirmation.<\/p>\n
Session timeouts further limit offline access. Revolut implements automatic logouts after periods of inactivity, typically ranging from 15 to 30 minutes depending on the user’s security settings. If a user is offline for longer than the timeout period, the session token expires and the next action that requires authentication will fail. Attempting to perform that action will prompt the user to reconnect to the internet and complete the full Revolut login process again.<\/p>\n
Airplane mode, connectivity, and partial access scenarios<\/h2>\n
Airplane mode disables cellular, Wi-Fi, and Bluetooth simultaneously on most devices. This creates an absolute offline state where no background sync can occur and no network requests can be sent. Within this state, a logged-in user can view cached balance and transaction data, but the app cannot refresh anything or perform authenticated actions. The user sees the last-synced version of their information, which may be minutes or hours old depending on when the device last connected.<\/p>\n
Some airlines or airports offer Wi-Fi service that operates independently of cellular networks. A user could disable airplane mode’s cellular component while keeping Wi-Fi enabled, or connect to in-flight Wi-Fi after entering airplane mode. This allows limited connectivity without using the phone network. If the user’s session is still active, this intermittent Wi-Fi could enable viewing updated balances or transaction history. However, once the user disconnects from that Wi-Fi or powers off the device, they return to a fully offline state.<\/p>\n
The practical scenario is therefore conditional. A user who successfully completes Revolut login before boarding, maintains an active session during the flight, and has access to in-flight Wi-Fi can refresh their account information and perform light browsing. A user in a remote area with no connectivity whatsoever can only view locally cached data if they are already logged in. A user whose session has timed out or who needs to log in for the first time will be unable to proceed without restoring internet connectivity and completing the full Revolut authentication flow.<\/p>\n
Device switching creates a separate problem. If a user loses their primary device or switches to a backup phone while traveling, they cannot complete a Revolut login on the new device without internet. The new device lacks the session token and will be unrecognized by Revolut’s device binding system. Even if the user remembers their phone number, they cannot receive an SMS code without cellular connectivity. This is why travelers carrying backup devices should ensure they complete at least one successful login on that device while connected to reliable internet before departing.<\/p>\n
Security trade-offs of offline access<\/h2>\n
Allowing any offline access, even to cached data, introduces a security surface. If a device is stolen after the user logs out, the thief cannot access the account. If a device is stolen while the session is active, the thief can see whatever information the offline cache contains\u2014balances, transaction history, card numbers, beneficiaries, and investment holdings. This is why Revolut’s session timeout is intentionally short and cannot be extended indefinitely by the user.<\/p>\n
The alternative would be to require internet connectivity for every single action, including merely viewing balances. That approach would eliminate offline data exposure but would make the app unusable in low-connectivity environments and would create friction during temporary outages. Revolut’s design balances this by allowing read-only access to non-sensitive cached information while requiring live authentication for sensitive actions like payments or security changes.<\/p>\n
Another consideration is app-to-server state divergence. If a user views their balance while offline and then someone else logs into the account and spends money, the offline device’s cached balance will be incorrect until it reconnects and syncs. This is not a security flaw\u2014it is a manifestation of distributed systems where offline replicas cannot instantly know about remote changes. Users should understand that any financial decisions based on offline balances are based on potentially stale information.<\/p>\n
Revolut’s anti-fraud scanning and device trust scoring also rely on internet connectivity. When a user is offline, those systems cannot run checks on the current session or flag unusual activity in real time. If fraudulent activity occurs while the device is offline, the fraud detection happens when the device reconnects and the activity is reviewed. The user’s offline session continues as if everything is normal, which is why logging out or switching sessions should be among the first steps after noticing suspicious activity.<\/p>\n
Practical offline access through Google Pay and contactless payments<\/h2>\n
One narrow exception to the offline limitation exists for contactless payments facilitated through Google Pay or Apple Pay. After a Revolut card is added to a mobile payment system and that system is configured, some payments can be processed offline on supported devices. This works because the payment system stores tokenized card information that can be used for transactions under a certain threshold without validating against the issuer’s server in real time.<\/p>\n
However, this does not constitute a full Revolut login or account access in airplane mode. The user cannot check balances, view transactions, or access Revolut’s other features. They can only make small contactless payments if their device and the merchant’s reader support offline payment processing. The Revolut app itself remains largely non-functional without internet. This feature is designed for brief, high-frequency transactions such as transit fares or coffee purchases, not for general account management.<\/p>\n
Travelers should not assume that mobile payment offline capability extends to other functions. The contactless payment system is separate from the Revolut app’s authentication and session management. If the user needs to check their balance, send money, or perform any other Revolut operation, they must reconnect to the internet and complete the standard Revolut account access process, which includes whatever Revolut authentication steps are required by their current device and session state.<\/p>\n
Planning ahead: pre-flight preparation and connectivity strategies<\/h2>\n
Travelers who anticipate limited connectivity should plan ahead by ensuring a successful Revolut login on all devices they intend to use before departure. This establishes active sessions that can survive brief periods offline and makes the devices recognized by Revolut’s system. Downloading recent transaction history or taking screenshots of current balances provides a backup reference, though this is not a substitute for in-app viewing.<\/p>\n
Confirming travel plans and completing any necessary account updates\u2014address changes, adding beneficiaries, or adjusting spend limits\u2014should happen before boarding when full connectivity is available. Emergency contacts and backup authentication methods should be current. A user should verify that biometric authentication is enabled on their device and that it is configured as a secondary factor to SMS codes, not as the sole authentication method.<\/p>\n
In-flight Wi-Fi or roaming data purchased before departure can enable periodic Revolut mobile banking access during travel, though connection reliability varies. Users should be conservative about initiating payments or sensitive transactions over public Wi-Fi and should verify transaction confirmations once connectivity stabilizes. If a payment fails due to intermittent connectivity, the user should check their transaction history before retrying; failed payments may still deduct fees but will not complete the transfer.<\/p>\n
Long-term travelers or those planning extended offline periods should consider whether a multi-currency wallet with preloaded funds in local currencies reduces dependency on accessing Revolut during travel. Revolut’s spending capability in 120+ countries and support for 30+ currencies means that preparing conversions ahead of time can reduce the need for real-time account access. However, monitoring spending and fraud detection still requires periodic online access.<\/p>\n
What to do if your session expires offline<\/h2>\n
If a user has been offline for longer than their session timeout period or if they suspect their session has been terminated, the next attempt to perform any authenticated action will trigger a Revolut login prompt. At that point, the user must reconnect to the internet and complete the full authentication sequence, including SMS code verification. Biometric authentication alone will not re-establish the session if the session token has expired.<\/p>\n
The user should not repeatedly attempt to authenticate while offline or toggle airplane mode on and off in hopes of establishing a connection. Repeated failed authentication attempts can trigger temporary account lockouts or fraud flags. A better approach is to wait until reliable internet connectivity is available, then initiate the login process once. This allows the SMS code to be delivered and the device to be verified.<\/p>\n
If the user is in an environment where SMS delivery is not possible\u2014such as traveling internationally without a compatible roaming plan\u2014they may need to enable a data-only option such as a local SIM or Wi-Fi calling if their carrier supports it. Some users preemptively enable backup authentication methods such as app-based authenticators (if Revolut supports them) or security keys, though standard Revolut authentication remains SMS-based for most accounts.<\/p>\n
Account recovery options are available through Revolut’s support channels, but these also require internet connectivity to initiate. A user locked out of their account without internet access should plan to contact support once connectivity is restored. For this reason, keeping emergency contact information for Revolut support in a format that does not require the app\u2014such as written in a travel document\u2014can be helpful for extended trips.<\/p>\n