Using your bank and home services while abroad

Every connection arrives with an address, and services use it to guess where you are. The address belongs to whatever network you're on: the hotel's Wi-Fi, a café, or a local SIM card. It's a rough guess, but at the level of a country it's usually right.

For a bank, a sign-in from a new country is a classic sign of a stolen password. So it does what your card provider does when your card turns up abroad: it slows down and checks. That might mean a code by text, a prompt in the app or, now and then, a held payment.

Other services at home react too. Some government portals, mobile-operator accounts and shops expect visitors from their own country, and a few won't load at all from elsewhere. None of this is personal. By address alone, they can't tell a traveller from an intruder.

Let's follow one evening. You live in Manchester, you're in Lisbon for a fortnight, and your council tax is due tomorrow.

First, the hotel Wi-Fi. It has a sign-in page, so you complete that before anything else; the network won't carry anything until you do, a VPN included. Then you open your bank's app without WrapVPN. The bank sees an address belonging to a Portuguese hotel, and it asks for a code.

Now try it with WrapVPN connected to London. Your phone wraps everything in an encrypted tunnel to our London server, and your traffic leaves from there. The bank sees a UK address, which looks a lot more like you on an ordinary Tuesday.

There's a side benefit on hotel Wi-Fi. The hotel's network sees an encrypted connection to our server rather than the services you're using. Your banking app already encrypts what you send, so this isn't about your password; it's about keeping the rest of your evening to yourself.

For the bank's check, the country is what counts. London gives you a UK address, Frankfurt a German one, and the New York area an American one. Pick the location in the country your bank, tax office or phone company expects.

WrapVPN has servers in some countries, and the list in the app is the current one. If your country isn't on it, a nearby location will still be quick, but it won't look like home. If you're from Dublin, say, and Ireland isn't on the list, London is a short hop, yet an Irish bank will see a UK address.

Distance matters for speed, not for the check. Connecting from Lisbon to London adds a little delay to each request, which you won't notice in a banking app. From Sydney, London is a much longer trip, so switch back to a nearby location once you've finished with home.

A home-country address removes one reason for suspicion, and only one. Banks also weigh your device, your card activity and your usual habits, so a code request can still appear. It's worth answering rather than dodging: it's the check that protects you if someone else has your password.

The address is also shared. Everyone connected to our London server appears from the same address, and some services can recognise addresses that belong to VPNs. A few treat them with extra caution, which can mean another check or, occasionally, a refusal. If that happens, disconnecting and answering the code from abroad is usually the quicker route.

So think of a home server as a way to make your sign-ins look ordinary, with no guarantee attached. Your bank decides how it treats any address, and we can't promise how a particular service will respond.

Most banking trouble abroad is sorted at home, before you've packed. Ten minutes the week before saves an awkward call to your bank from a hotel lobby, and an expensive one if you're roaming. Work through this list with your phone in hand.

Services at home react to where you appear to be, and a WrapVPN server in your home country lets you appear there. It helps most with sign-ins and sites that expect a home address, while your bank keeps the final say. Install WrapVPN before you leave, find your home location, and connect to it whenever home services get fussy.