Why Revolut Stops Working With a VPN—and Why One Stable Route Fixed It

The Revolut notification appeared while I was standing at a car-rental counter:

Confirm this payment in the app.

I had booked the car weeks earlier. Now the rental company needed one final deposit approval before the agent could release the keys. I opened Revolut on my phone and waited.

The logo stayed on the screen.

Then the app displayed a connection error.

I blamed the airport Wi-Fi, disconnected and joined it again. A browser page loaded immediately. My messages arrived. The VPN icon remained green.

Revolut still would not open.

The rental agent glanced at the queue forming behind me. I switched the VPN to another country, closed the app and tried again.

This time Revolut reached the login screen, requested verification and froze before completing it.

On the third server, the app opened. The pending payment did not.

I had installed a VPN because I did not want to manage money over an airport network without one. Yet the tool protecting the connection was now standing between me and the account I needed to use.

“Revolut not working with VPN” sounded like a technical inconvenience.

At the counter, it meant I had several minutes to approve the deposit or lose the reservation.

Revolut was checking more than my password

I had assumed that once Revolut recognised my phone, passcode and face, the network underneath them would not matter much.

Financial apps do not make decisions from one signal alone.

Revolut offers security features that can compare a phone’s location with the location of a card terminal. It also monitors account activity and may request additional verification when a login or payment looks unusual.

A VPN adds another location signal: its exit IP address.

Using a VPN is not itself proof of fraud. Revolut even includes VPN-related benefits in some paid plans. But its support material acknowledges that an active VPN can trigger fraud prevention during certain account-linking or payment processes.

The problem at the rental counter was therefore not encryption.

My phone was physically at the airport. The card terminal was beside me. Meanwhile, I had made the app appear to connect from three different countries within a few minutes.

I was changing the story every time Revolut tried to verify it.

That realisation led directly to the mistake I had been repeating.

More servers gave me more ways to look inconsistent

The established VPN was a reasonable first choice.

It had years of public history, a large support operation and servers in more countries than I would ever need. Those strengths normally made it feel dependable.

At the rental desk, they gave me options.

I started with the automatic connection. When Revolut failed, I chose the nearest country in the list. When verification froze, I selected a server with a lower reported load. Then I changed protocol.

Each decision seemed sensible by itself.

Together, they made the session less coherent.

One connection loaded my account balance but not the pending payment. Another reached the confirmation screen and returned me to the home page. The next prompted me to verify the device again.

Other Revolut users have described a similar pattern: the app works through a VPN for months, then suddenly fails on particular servers while opening normally as soon as the VPN is disconnected. (Reddit: r/Revolut) The useful detail was not that every user had the same cause. It was that VPN-related failures often appeared at different stages rather than as one clean block.

I could not observe Revolut’s internal risk rules or the airport network’s filtering decisions. The failure may have involved the reputation of a shared exit IP, rapid location changes or an interrupted verification session.

What I could see was enough.

Every server change gave Revolut a new network identity while I was asking it to approve the same financial action.

The large server list had stopped being a safety net. It had become a machine for generating fresh variables.

Turning the VPN off solved the wrong problem

I disconnected the VPN.

Revolut opened immediately.

The pending rental deposit appeared. I tapped it, and the confirmation screen loaded without hesitation.

For a moment, that seemed like the answer.

But I was still using public airport Wi-Fi. The airport network could not read the encrypted contents of the Revolut session, but I still did not want my rule for financial apps to become: when access fails, remove a layer of protection and hope the network is trustworthy.

Mobile data would have been the obvious alternative, but roaming had not activated properly after landing. The airport Wi-Fi was the only usable connection available.

So the choice was no longer between VPN and no VPN.

It was between a connection that kept changing my apparent network identity and one that could preserve a single session long enough for Revolut to complete its checks.

That was a much narrower requirement than the one I had been using to compare VPNs.

I did not need to appear farther away.

I needed to stop moving.

The smaller app gave Revolut one consistent session

I opened OnlydogVPN, which I had installed as a travel backup.

It has fewer server locations than the established provider, a shorter public history and fewer independent reviews. Those limitations would matter if I regularly needed an address in a particular small city.

At the rental desk, I did not need a city.

I needed one connection that would remain stable from login to payment approval.

The smaller app organised its choices around situations instead of presenting a long geographical list. I selected the option for an unreliable public network and connected.

Then I reopened Revolut.

The logo disappeared.

My balance loaded. The pending rental payment appeared beneath it. I tapped the transaction and completed the biometric check.

The screen paused for a second.

Then it displayed:

Payment confirmed.

The rental terminal changed from waiting to approved. The agent printed the agreement and placed the keys on the counter.

No second server.

No new country.

No repeated device verification.

The app had not bypassed Revolut’s security controls. It had simply allowed the verification process to finish without changing the connection underneath it.

That was the result I had been missing.

The useful technology stayed in the background

The airport Wi-Fi weakened while the rental agent printed the contract.

The signal indicator fell, disappeared briefly and returned.

Revolut remained open.

The smaller service uses an HTTP/3-based transport, which runs over QUIC and is built to recover efficiently when packets are lost or the underlying network path changes. (RFC 9308)

The practical difference required no protocol diagram.

The protected session survived the interruption.

With the established provider, a brief network problem had become a new tunnel, a new server identity and another Revolut verification attempt. With the smaller app, the connection recovered without turning the airport’s momentary Wi-Fi failure into a new login event.

That mattered more in a financial app than it would while reading the news.

A failed webpage can be refreshed. A payment confirmation interrupted halfway through creates a more uncomfortable set of questions:

Did the approval reach Revolut?

Should I tap again?

Could a second attempt duplicate the payment?

Will another login trigger another security check?

A VPN that recovers quietly removes those questions before they appear.

The established provider had offered many ways to begin a new connection. The smaller app did a better job of preserving the connection I had already begun.

I stopped treating distance as privacy

My mistake had started with an old habit: when a VPN causes trouble, choose another country.

That can help when a server is overloaded or a website is unavailable from one region. It is a poor instinct when a financial app is already comparing the device, transaction and travel context.

A VPN should protect the route to Revolut, not invent a journey that the phone, card terminal and account activity do not support.

Once I understood that, the setup became simpler.

I kept the phone’s location permission available for Revolut’s own security features. I stopped switching countries during an active login or payment. I chose one public-network connection and let the app finish before changing anything.

If Revolut displayed a security restriction or requested identity verification, I would follow the process inside the app rather than trying to route around it. The goal was not to defeat fraud prevention.

It was to stop triggering unnecessary suspicion through a connection that kept changing shape.

The next payment showed whether the fix would last

An hour later, I stopped at a fuel station.

The card terminal requested another in-app confirmation because of the deposit arrangement. The same VPN connection was still active.

I opened Revolut.

The notification was already waiting.

I approved it, returned to the terminal and completed the payment.

There was no frozen login screen and no hunt for a working server. More importantly, I no longer felt tempted to change countries the moment a screen took an extra second to load.

The connection had become boring.

For a financial app, boring is valuable.

Later, I opened the service on my laptop to download the rental documents. Instead of entering another account password over the airport network, I linked the second device with a verification code from my phone.

That was not what approved the deposit. The important problem had already been solved.

But it removed the next piece of friction without creating another login session, another password prompt or another chance for the setup to diverge across devices.

I left the service installed on both.

What to do when Revolut fails with a VPN

When Revolut stops loading or freezes during verification, changing servers repeatedly can make the situation worse.

First, stop creating new location signals. Avoid jumping between countries during an active login or payment.

Keep the device location accurate so Revolut can compare it with the real transaction context. Reopen the app on one stable VPN route rather than testing several exit locations in quick succession.

If the app requests identity verification or displays a clear security warning, complete that process inside Revolut. A VPN should protect the connection, not be used to evade an account check.

Finally, judge the VPN by the task that matters. Did the app open? Did the pending transaction appear? Did confirmation finish? Did the session survive a brief Wi-Fi interruption?

My established provider still had more servers, more years of operation and more advanced controls. Those advantages remained real.

They simply did not approve the deposit.

The smaller service gave me fewer choices, but it kept one protected route stable from login through biometric confirmation and the final payment response.

The VPN that got me the car keys was not the one that hid my location most aggressively. It was the one that stopped making Revolut think I had crossed three borders before the deposit cleared.