Usually, if you use your bank's official app or type its address yourself: the connection is encrypted with HTTPS, so the Wi-Fi can't read your balance or password. The real risks on public Wi-Fi are fake hotspots, fake login pages and phishing links. Use the app, stop at any certificate warning, keep two-step verification on, and use mobile data or a VPN when you can.
You're at the airport, your card has just been declined, and the free Wi-Fi is right there. Is it safe to open your banking app?
The honest answer is more reassuring than most warnings suggest, with a few real traps. Here's where the risk actually is.
The short answer, risk by risk
| Risk on public Wi-Fi | How likely it matters | What protects you |
|---|---|---|
| Someone on the network reads your balance or password | Low, if the connection uses HTTPS | Encryption built into your bank's app and website |
| A fake certificate lets someone read the traffic | Low, as long as you never click through a warning | Your browser's certificate check; pinning in some banking apps |
| A fake hotspot shows a fake bank or login page | Real | Using the official app, typing the address, checking where you are |
| A phishing link by text or email | Real, and not specific to Wi-Fi | Never logging in from a link |
| Someone reads your screen over your shoulder | Real in crowded places | Your hand, and a screen lock |
Official advice differs in tone. The US Federal Trade Commission says that thanks to encryption, using public Wi-Fi is "usually safe". Germany's BSI is more cautious: it recommends avoiding online banking on public WLAN and, if you can't, using a VPN. Both are right about different things: the encryption holds up well; the people and pages around it are the weak point.
What already protects you
- HTTPS everywhere. Banking websites and apps encrypt the connection. Sites can also turn on HSTS (RFC 6797), which makes your browser refuse insecure connections to them and not let you click past a certificate error; banks have every reason to use it.
- Certificate pinning in some apps. An app can accept only its own bank's certificates instead of any certificate the phone would trust, a technique Android's network security configuration documents. Even a network that tries to slip in a fake certificate gets nowhere.
- Two-step verification. In the EU, the payment services directive, PSD2, requires strong customer authentication (Article 97) when you log in to your account online or make an electronic payment: two independent factors, such as your phone plus a PIN or your fingerprint. A password caught on a fake page isn't enough on its own.
Where the real risk is
Almost every successful attack around public Wi-Fi goes around the encryption rather than through it:
- Fake login pages. A fake hotspot, or a fake Wi-Fi login page, asks you to "verify" with your bank or email details. Our guide to evil twin Wi-Fi shows how these work.
- Fake addresses. On a hostile network, typing a bank's name into a search box or following a link can land you on a look-alike site. Your bank's app doesn't have that problem.
- Links. A text message saying your card is blocked, with a link to "fix it", is phishing whether you're on Wi-Fi or not.
- Shared devices. A hotel business-centre computer can record everything you type. Bank only from your own device.
A safe routine for banking away from home
- Use your bank's official app, installed from the official app store, rather than the browser.
- If you use the browser, type the address or use a bookmark. Don't search for your bank on a network you don't trust.
- Never enter bank details on a Wi-Fi login page. Hotels and cafés don't need them.
- Stop at any certificate warning. Close the page; don't continue.
- Keep two-step verification on, and read what you're confirming before you approve it.
- For transfers, prefer mobile data if you have it. Otherwise, use a VPN.
- Log out when you're done on shared or borrowed devices.
VPNs and banking apps
A VPN adds a layer on public Wi-Fi: the network sees one encrypted connection instead of the name of your bank, and your lookups go to the VPN's resolver instead of one the hotspot controls. It doesn't make phishing safe, and it doesn't replace any of the steps above.
Some banks are wary of VPN connections, or of sign-ins from another country, and ask for extra checks or refuse to log in. If that happens, you don't have to switch the VPN off for everything: exclude only the banking app with split tunneling. The app then connects directly, still protected by its own encryption, and everything else stays in the tunnel. Travelling abroad raises the same questions; our guide on whether you need a VPN when travelling covers them.
How PryVPN fits in
- It connects on its own on untrusted Wi-Fi, so you're not relying on remembering to switch it on at the airport (public Wi-Fi help).
- Its DNS runs inside the tunnel, and known malware and phishing domains are blocked there. That helps, but new phishing sites appear every day: no filter replaces checking the address.
- Split tunneling lets a banking app that refuses VPNs connect directly, without turning protection off for everything else.
Frequently asked questions
Is it safe to check my balance on hotel Wi-Fi?
With your bank's official app, yes, in almost all cases: the connection is encrypted. Be careful with the hotel's own login page, which should never ask for bank details.
Can the Wi-Fi owner see my bank password?
Not if the site or app uses HTTPS and you don't click through a certificate warning. They can see that you connected to your bank, unless you use a VPN.
Is the bank's app safer than its website?
On an untrusted network, usually yes: you can't mistype the address or land on a look-alike page, and some apps check the bank's certificate more strictly than a browser does.
Does incognito mode help?
No. Incognito only stops your browser from saving history on your phone. It doesn't change what the network sees.
If you'd like a VPN that switches itself on at the airport and lets your banking app connect directly when it needs to, you can download PryVPN.
Sources
- FTC Consumer Advice: Are Public Wi-Fi Networks Safe? What You Need To Know
- Directive (EU) 2015/2366 (PSD2), Article 97: strong customer authentication
- Android Developers: Network security configuration (certificate pinning)
- RFC 6797: HTTP Strict Transport Security (HSTS)
- BSI: Security tips for online banking (German)
Spotted a mistake? Write to support@pryvpn.com and we'll fix it and update the date.
