A banking or ride-hailing app that suddenly demands extra verification is not broken — it just disagrees with the tunnel about where you are. Split tunneling lets you handle that app by app instead of an all-or-nothing switch.

A ride-hailing or banking app that suddenly fails to log in, or throws in an extra identity check, while a circumvention tool is running — that is not the app breaking. That is exactly what split tunneling is for. It lets you choose which apps must stay on a direct connection and which must go through the tunnel, instead of the whole device being forced into one or the other.
Most circumvention tools ship this feature under different names — split tunneling, app-level routing, per-package rules — but the mechanism is the same: certain apps get tagged so they skip the tunnel and use the phone's own network directly.
Here is how it usually shows up: you open a ride-hailing app in the morning and it throws a face check, citing a "login from an unusual location." Most people's first move is to log in again or switch networks. Adding that app to the direct list fixes it for good, because the app no longer has any reason to suspect you are somewhere else.
This mostly happens to two kinds of apps. One is banking, payments and ride-hailing, which actively check where you are. The other is local-life and government-service apps, whose content is genuinely region-bound, so tunneling actually hides what you should be seeing. Everything else — video, social, work tools — usually behaves the same either way.
The rest of this guide goes in order: preparation, turning it on, verification, common traps. By the end you should be able to decide for yourself whether a given app needs a direct-connection rule, instead of switching the whole tool off the moment something looks wrong.
Banking, payment and ride-hailing apps care a lot about where you currently are. Once traffic goes through the tunnel, the location they see stops matching the region your SIM is actually in, and the risk system may throw a verification prompt, freeze the login for a while, or in bad cases ask you to sort it out in person at a branch.
That is not a bug — it is a deliberate protection meant to stop the account being used from an unfamiliar place. Split tunneling does not try to get around that check; it avoids it at the source by keeping that app's traffic on the local network, never touching the tunnel, so the risk system has no reason to fire in the first place.
This kind of check rarely warns you in advance — the first time you hit it is usually right when you are in a hurry to book a ride or send a transfer, which is exactly why it feels so jarring. Adding the sensitive app to the direct list ahead of time removes the surprise entirely, instead of leaving you to improvise every time.
The reverse also happens: apps built around local weather or phone-bill lookups return content based on an overseas address once tunneled, and may simply say the service is not available in your region. Those belong on the direct list too, while something with no regional gate — a news aggregator, most video apps — behaves about the same either way.
Whether your route is stable and whether an account gets flagged are two unrelated questions. The first is solved by the tunnel; the second is solved by keeping sensitive apps off it. Online banking has its own extra considerations, and what to watch for when paying through a VPN covers that separately.
Open whatever circumvention tool you currently use and look for "split tunneling," "rule mode," or "app routing" in its settings. The label is not standardized, but it almost always sits in connection settings or an advanced section — no reinstall required to find it.
Decide which apps actually need a direct connectionWrite your own short list. Banking, government services, local ride-hailing and food delivery almost always belong on it. Video, social and work-collaboration apps are fine on the tunnel; there is no need to test each one individually, a category-level judgment is enough, and missing one or two is easy to fix later.
Confirm the permission is actually grantedSplit tunneling usually needs permission to read the list of installed apps. If that was declined during setup, the app list in settings often comes back incomplete, and you may not immediately notice which app is missing. Go back into system permissions and grant it properly.
Most tools default to global mode, where every byte goes through the tunnel. Find the mode switch — usually right at the top level of connection settings — and pick "split tunneling" or whatever it is called in your app.
Step two: add the apps that need a direct connectionSelect banking and ride-hailing apps from the installed-apps list. It is normally sorted alphabetically or by install date, and typing the app's name finds it faster; selecting several at once is fine too.
Step three: restart those appsOnce the rule changes, an app already running in the background will not pick it up immediately, because it opened its connection under the old rule. Swipe it out of the background and reopen it so the new routing actually takes effect for that app.
Step four: test both sides separatelyOpen a directly-routed app and confirm the city it detects matches where your SIM actually is; then open a tunneled app and confirm it still reaches overseas sites normally. Only when both check out has the rule actually taken hold, rather than merely looking like it has.
Finishing the setup does not mean you can forget about it — these are the places a working rule quietly stops working without telling you.
None of these are individually hard to fix, and none are hard to spot — it is having several stack up at once that makes troubleshooting slow. Go through this list one item at a time when something breaks, rather than reaching straight for a reinstall or a different tool.
If your daily use is mostly video and overseas browsing with nothing that needs to keep a local address, the upkeep split tunneling demands can end up costing more than the problem it solves. In that case a single mode is simpler and less likely to break from a rule you forgot to update.
The test is simple: count how many apps on your list genuinely need a direct connection. One or two, and it is worth setting up once. A list that keeps growing suggests you rely on a lot of local services day to day, and the setup step is not optional for you.
The opposite case exists too: if nearly everything you use daily needs to stay direct and only the occasional overseas site needs the tunnel, it may make more sense to flip the default — leave the device on the local network by default and connect the tool only when you specifically need it, rather than maintaining an ever-growing direct list year-round.
FastOrange connects with one tap by default and needs no manual setup to cover most situations. When a specific app genuinely needs a direct connection, follow the steps above in whichever tool you are using — there is no need to assume upfront that you need the most complicated configuration available.
Split tunneling solves one specific problem: keeping region-sensitive apps on the local network while everything else keeps using the tunnel, with neither side affecting the other. Work out which apps truly need a direct connection before you start, restart each affected app once the rule changes, and test both sides afterward instead of assuming it worked — skipping that restart is exactly why people spend half an hour debugging a rule that was never actually applied.
If your phone regularly hands off between Wi-Fi and mobile data, the change in connection can reset this kind of rule too, and switching between Wi-Fi and mobile data without dropping the connection covers that separately. To see whether your own case even needs this feature, FastOrange gives every registered account free trial time daily — test it first, then decide whether to keep it long term.



One App. Every Platform. A More Stable Connection.
Available for Windows, macOS, Android, and iOS. Use One Account Across All Your Devices and Start with a Free Trial.


Choose your platform
Switch between Windows, Android, iOS, and macOS