The Banking Website Worked With My VPN—The App Failed at the One Job I Needed

The banking website showed my balance.

The mobile app closed two seconds after I signed in.

I was sitting at a small desk in a Seoul hotel room with a paper check beside my phone. A client had handed it to me after the final session of a conference, and my rent payment was scheduled to leave the account the following morning.

Through the website, I could see the checking account, confirm the pending rent payment and verify that the check had not been deposited.

What I could not do was put the check into the account.

That required the mobile app.

I opened it, completed Face ID and briefly saw the account screen. Then the app returned to its welcome page with a message:

This connection is not supported. Disable your VPN and try again.

I blamed the hotel Wi-Fi.

The guest network had already forced me through a captive portal and disconnected once during a video call. I closed the banking app, rejoined the Wi-Fi and tried again.

Face ID worked.

The app closed.

I turned off the VPN.

This time it stayed open, and the Deposit Checks button appeared exactly where it should have been.

That seemed to identify the solution, but it created the wrong trade-off. The hotel network was also carrying my email, cloud storage and work messages. I did not want to disable the private connection every time the bank demanded the mobile app.

I turned the VPN back on.

The website continued working.

The app threw me out again.

The website and app were solving different problems

I had assumed that mobile banking was simply the bank’s website arranged for a smaller screen.

It was not.

Banks often provide many of the same functions through both channels, but some features remain app-only. Bank of America, for example, makes Mobile Check Deposit available through its mobile app rather than ordinary Online Banking. (Bankofamerica)

That distinction explained why the working website did not solve my problem.

The browser could show my accounts. It could confirm that the rent payment was pending. It could let me move money the bank already held.

It could not photograph the check.

The app controlled the camera, biometric login and the deposit process. It also made its own connection to the bank, separate from the website open on my laptop.

My credentials were valid.

The bank was online.

The VPN could reach the website.

Only the native app rejected the route.

Once I understood that, refreshing the browser became pointless. The channel that worked did not contain the feature I needed.

The app was applying a stricter test

Banking apps have reasons to be cautious. Reported fraud losses reached nearly $16 billion in 2025, and impersonation scams remained especially costly. (Ftc)

A native app can also assess its environment more closely than a normal webpage. Android’s Play Integrity system, for example, can help an app verify that requests come from a genuine installation running on a recognised device. (Google) Banks can combine that kind of device information with network and account signals before allowing a sensitive action.

That explained the difference without fixing it.

The app accepted Face ID, so it recognised me well enough to begin. It failed only after the VPN connection became part of the session.

The website working was not proof that the provider was compatible with the banking app. It proved only that one browser route had reached the bank.

The check deposit required a higher standard.

More servers only changed where the app failed

My established VPN provider was the reasonable first choice.

It had years of public history, mature applications and servers across several nearby countries. I started with its recommended connection.

The banking website loaded.

The mobile app closed after Face ID.

I changed to a server in Japan, force-closed the app and tried again.

This time the account screen remained visible for several seconds. When I tapped Deposit Checks, the app reported a connection error and returned to the login screen.

A Singapore server reached the deposit menu but froze before opening the camera.

The provider’s fastest option brought back the original VPN warning.

Each server changed the details of the failure without changing the outcome.

The website worked every time.

The check remained on the desk.

Other travellers have seen the same split: the bank’s website remains available while the Android app immediately logs out when a VPN is active. (Reddit)

That brief experience confirmed the practical point. A browser is not a useful fallback when the required action exists only inside the app.

I did not need another server that could display my balance.

I needed one that could open the camera, submit both images and produce a deposit confirmation.

Split tunnelling removed the wrong protection

The established provider offered a bypass feature, so I excluded the banking app from the VPN.

The app opened.

Face ID completed.

The deposit menu appeared.

For a moment, that seemed like a workable answer. My browser, email and background applications would remain inside the tunnel while the bank connected directly through the hotel Wi-Fi.

But the exception now applied to the most sensitive application on the phone.

The bypass also proved something important: the account, app and camera were functioning. This particular VPN route was the obstacle.

I removed the exception.

The warning returned.

By then, the room light had begun casting a shadow over the check. The bank needed clear photographs of both sides, and waiting until morning risked leaving the account short when the rent payment arrived.

I no longer needed another country or protocol setting.

I needed the banking app to remain inside a private connection and finish the deposit.

The camera opened without excluding the bank

I closed the first provider and opened OnlydogVPN.

The smaller app did not begin with a server map or ask me to compare countries and loads. I selected the situation for a restrictive network and connected.

Then I force-closed the banking app so it would begin a fresh session.

I reopened it.

Face ID completed.

The account screen remained in place.

I tapped Deposit Checks.

The camera opened.

I placed the check on a dark hotel folder and photographed the front. The app found the edges automatically. I turned it over, added the required endorsement and photographed the back.

Then I entered the amount, selected the checking account and tapped Submit.

A progress indicator appeared.

A moment later, the bank displayed the result I had been trying to reach:

Your deposit is processing.

The app had remained inside the VPN for the entire sequence.

The paper check was now in the bank’s review queue before the rent payment left the account.

Only after the confirmation appeared did the difference between the routes matter. The service uses an HTTP/3-based transport with additional traffic obfuscation, allowing the tunnel to blend more naturally with ordinary modern web traffic.

I could not inspect the bank’s internal risk rules or identify the exact signal behind every earlier rejection. The result was still decisive: the established provider carried the website but failed at different stages of the app-only deposit, while the smaller one completed the process from Face ID to submission.

Leaving the room did not erase the result

The bank advised me to retain the paper check until the deposit was fully accepted, so I placed it in my passport wallet and went downstairs to find something to eat.

I kept the app open because I wanted to see whether the deposit appeared under pending activity.

The hotel Wi-Fi weakened in the lift.

My phone switched to mobile data.

For a moment, the account screen stopped refreshing. Then the pending deposit appeared.

The app did not close.

The bank did not demand another login.

The VPN stayed connected as the network underneath it changed.

Its HTTP/3-based route recovered without rebuilding the banking session. (IETF) On the phone, that meant only three things:

The Wi-Fi disappeared.

Mobile data took over.

The deposit confirmation remained visible.

That continuity mattered because app-only banking tasks often happen while travelling. A check may be deposited from a hotel, a card unlocked at an airport or a transfer approved while walking toward a train.

A connection that works only until the phone changes networks has not finished the job.

The smaller app stayed out of the way until the result was secure.

The working website had pointed me toward the wrong benchmark

Before that evening, I would have diagnosed the problem differently.

If the website worked through a VPN, I would have called the VPN banking-compatible.

If the app failed, I would have blamed an update, Face ID, the operating system or the hotel Wi-Fi.

But the sequence exposed a narrower problem.

The app worked when the original VPN was disabled.

It failed when that tunnel returned.

It completed the deposit when the route changed.

The bank account itself had never been inaccessible. The mobile app simply applied a stricter standard to the connection.

That distinction matters whenever the desired function is app-only.

The browser can confirm that the account and bank service are available. It cannot prove that the VPN can carry the native app through its most sensitive action.

The useful test is not whether the balance appears somewhere.

Does the camera open?

Does biometric verification finish?

Do the images upload?

Does the bank confirm the deposit?

In my case, the only meaningful benchmark was whether the paper check stopped being paper.

The smaller route completed the part the browser could not

The service has fewer locations and a shorter public history than the largest VPN providers.

Neither limitation affected the deposit.

The established provider gave me several nearby servers and reliable access to the banking website. Its routes failed at different points inside the mobile app.

Split tunnelling made the app work by removing it from the VPN.

The smaller app kept the bank inside the private route, opened the camera, uploaded both sides of the check and preserved the session when the phone moved from hotel Wi-Fi to mobile data.

By the time I returned upstairs, the website still showed the same balance it had shown an hour earlier.

The difference was that the app had finally completed the one task the website could never perform.