Wise Stopped Working With My VPN—The Fix Was One Consistent Route, Not Another Country

The transfer failed one screen before confirmation.

I was in a hotel lobby in Lisbon, trying to pay a freelance designer before her bank’s end-of-day cutoff. The recipient details were correct. The money was already in my Wise balance. I only needed to review the amount and approve the transfer.

Instead, the website displayed a verification challenge.

I completed it.

The page refreshed and showed another one.

After the third attempt, the challenge stopped loading altogether.

I blamed Wise first.

I closed the browser, cleared its cache and opened a private window. The login page accepted my password, then returned me to the same verification loop.

The Wise status page showed its website, app and payment systems operating normally. That left the connection in front of me.

I was using a major VPN because the hotel Wi-Fi was shared with hundreds of rooms. Its automatic mode had first connected through Spain, then moved to France when the original server slowed down.

I changed it manually to Portugal.

Wise sent a new-device approval request.

I approved it from my phone.

The website asked me to prove I was human again.

The payment deadline was now fourteen minutes away.

Wise was reacting to a moving session

Wise’s troubleshooting guidance says a VPN or proxy can interfere with its CAPTCHA. The recommended sequence is simple: pause the VPN, complete the challenge and reconnect afterward.

That explained why the page was stuck. It also exposed the larger mistake I had made.

My Wise session had crossed several VPN locations in less than ten minutes. Wise can use device and location signals to identify suspicious access, including activity that appears to come from another country.

Changing the VPN location did not alter my registered address, known device, account history or recipient.

It changed only where the connection appeared to emerge.

By allowing automatic server changes and then jumping between countries manually, I had surrounded an ordinary payment with unnecessary movement.

The provider gave me more than a hundred locations.

Wise needed my session to stop travelling.

Turning the VPN off fixed the challenge, not the transfer

I followed Wise’s advice.

I disconnected the VPN, reopened the page and completed the CAPTCHA. This time it cleared immediately.

The transfer screen returned with the amount, fee and recipient details intact.

That solved the first obstacle. But I was still on unstable hotel Wi-Fi, and the connection had already paused twice while I worked.

I reconnected the established VPN, selected one Portuguese server manually and returned to the transfer.

The page loaded.

I reviewed the recipient name and pressed Confirm and send.

The hotel Wi-Fi weakened.

The VPN changed to Reconnecting.

Wise returned me to the login screen.

A new verification email arrived.

Before trying again, I checked the activity tracker, as Wise recommends after an interrupted payment. No transfer had been created.

I still had nine minutes.

The CAPTCHA was no longer the problem. The next requirement was more important: maintain one protected, recognisable session long enough to approve the payment and see it appear in the activity list.

More server choices created more security checks

My established provider was not an obscure service.

It had years of public history, mature applications, extensive documentation and broad international coverage. Those strengths were why I trusted it while travelling.

But its automatic mode treated weak hotel Wi-Fi as a reason to build another route. Each recovery could create a fresh tunnel or a different exit address.

For casual browsing, that might mean refreshing a page.

For a financial account, it can mean another verification step.

Wise may restrict access when it detects unusual activity or needs to confirm that the account holder is present. Repeated location changes did not prove anything was wrong, but they gave the payment system more changes to interpret.

Other travellers describe the practical consequence in simpler terms: when a cross-border money account questions a login far from home, a temporary interruption can delay rent, invoices or travel payments. (Reddit: r/digitalnomad)

That was the point where I stopped searching for a better country.

I needed one route that stayed consistent through the final confirmation.

The smaller app began with the payment

I had OnlydogVPN installed as a backup.

The service has fewer locations than the established provider, a shorter public history and fewer independent reviews. Those limitations matter when someone needs a specific city or wants the broadest record of third-party assessment.

I did not need a particular city.

I needed the hotel network to stop changing underneath one legitimate transfer.

The app organised its options around situations rather than opening with a world map. I selected the preset for sensitive account access on an unstable public network.

It established one route.

I opened Wise in a clean browser window and logged in. The account accepted the familiar-device approval without returning me to the CAPTCHA loop.

I created the transfer again.

Recipient.

Amount.

Reference.

Review.

The hotel Wi-Fi weakened as I reached the final screen.

The page paused.

The protected connection recovered.

The confirmation screen stayed open.

I pressed Confirm and send.

For several seconds, nothing moved. Then the activity page appeared with the transfer at the top:

Money received

A moment later, it changed to:

Your money’s being processed

The transfer was now real, visible and trackable.

I sent the designer a screenshot. Her reply arrived before I closed the laptop:

Got it—thank you.

The deadline had three minutes left.

Wise had not needed me to appear in another country. It needed the connection to stop changing long enough to confirm the payment.

The technology mattered because the page stayed open

The service uses an HTTP/3-based transport with additional traffic obfuscation. HTTP/3 runs over QUIC, which is designed to recover quickly when packets are lost or the network path changes. (RFC 9000)

In the hotel lobby, the result was straightforward:

The Wi-Fi weakened.

The VPN recovered.

The Wise session remained open.

I could not observe Wise’s internal risk-scoring rules or the hotel’s traffic-management decisions. I could observe the result on the same laptop and network.

The established VPN repeatedly converted a brief connection problem into a new tunnel and another login.

The smaller app preserved the route long enough for Wise to keep the confirmation page open.

For this payment, consistency mattered more than another fifty countries in the menu.

The phone became a transfer tracker without another login detour

After the payment entered processing, I needed to leave for the airport.

The laptop battery was nearly empty, so I wanted the Wise tracker available on my phone. The phone would move from hotel Wi-Fi to mobile data, then to airport Wi-Fi.

The smaller service let me link it using a verification code.

I approved the code from the laptop and connected the phone without retrieving another VPN password or waiting for a new account email.

The payment had already succeeded. Device sharing did not make Wise process it faster.

It removed the next practical friction: I could close the laptop and continue tracking the transfer on a protected phone connection.

In the taxi, the phone left the hotel Wi-Fi and switched to mobile data.

The connection recovered.

The Wise tracker remained visible.

Before I reached the airport, the status changed again:

Sent

What to do when Wise does not work with a VPN

Start by identifying the exact failure.

If Wise reports a wider service incident, changing VPN servers will not repair it. If the service is operating normally but the CAPTCHA will not complete, pause the VPN, clear the challenge and reconnect afterward.

Once the CAPTCHA is complete, stop switching countries.

Choose one appropriate route and keep it active through login, recipient review, payment approval and confirmation. Rapid location changes add friction without changing your real account details.

If the page fails during the final step, check the Wise activity tracker before creating another transfer. A blank confirmation screen does not tell you whether the payment was created.

The useful questions are concrete:

Did the CAPTCHA clear?

Did the same login session remain active?

Did the confirmation page survive a brief network interruption?

Did the transfer appear in the activity tracker?

Did the VPN remain on one route instead of rebuilding the session?

Use accurate residency and account information. A VPN protects the connection; it does not change where Wise services are legally available.

My established provider still offered more locations, a longer history and a larger support organisation.

Those strengths did not help when automatic route changes kept turning one payment into another security check.

The smaller service offered fewer geographic choices, but its sensitive-account preset held one route through weak hotel Wi-Fi, preserved the confirmation screen and kept the transfer tracker available as I left.

Wise did not need me to appear in more countries. It needed my legitimate payment to remain on one connection long enough to be confirmed.