Four quick combinations, four clear verdicts. This is the test technicians run before touching a single setting — and it works for any bank, any error, any home.
Random fixing has a hidden cost: every setting you change becomes a new suspect. The split test avoids that entirely. By trying the bank through a different door (the app instead of the browser) and a different road (mobile data instead of Wi-Fi), you isolate the fault to one owner before you fix anything. Do the two minutes. Then take the matching fix from this set — browser, network, or patience — instead of all three.
👆 Two minutes of testing replaces an afternoon of changing settings at random.
Every access problem lives in exactly one of three places: your browser, your network, or the bank. The split test separates them by changing one thing at a time. Axis one is the door: website in a browser versus the official iMobile app. Axis two is the road: your home Wi-Fi versus mobile data. Run the payment (or just a login) in each combination and read the verdict off the panel above — each pattern points at a different owner, and each owner has a different fix in this set.
The app reaching the bank through the same Wi-Fi acquits your network and the bank in one move. What remains is the browser's own layer: stale site data, a blocking extension, or settings that break the payment hop. Go straight to the one-site clear in this set, allow pop-ups and redirects for the bank, and pause blockers for the site. If a second browser on the same computer works, that confirms it further — your main browser's profile is where the fault lives.
Now the browser and the bank are both acquitted; the road between your router and the bank is the problem. In rough order: restart the router; run ipconfig /flushdns on the computer; check whether a VPN, a router-level filter, or a 'family safety' DNS service is intercepting banking domains. If the failure began the day your internet provider changed something — or affects a neighbour on the same provider too — it sits with the provider, and a call to them with the exact error and time beats any setting you can change.
When the app and the website both fail, on Wi-Fi and on data, on your phone and a family member's, the efficient diagnosis is: not you. Banks have outages and maintenance windows like everyone else, just quieter ones. Check the bank's official channels for notices, then wait — and read the maintenance page in this set for how to wait safely, including why retrying a payment repeatedly during an outage is the one thing not to do.
The office variation deserves one line: if it fails only at work, your office firewall or proxy is deciding for you. The fix there is a conversation with your IT team — or simply banking from your phone on mobile data, on your own time, through the official app.
Watch the video to see the access error being cornered live — then use this page's four verdicts whenever any bank page misbehaves.
▶️ Watch Full VideoTwo browsers failing identically while the app succeeds shifts suspicion back toward something shared: your antivirus's web protection, a system-wide proxy or VPN, or your network after all. Test the website on the same computer through a phone hotspot — if it works there, it is the network; if it still fails, look at security software and VPNs on the computer itself.
For most daily banking, honestly yes — the official app is a perfectly good primary door, and many people prefer it. The website matters for some statements, bulk work and larger screens. Treat the app as your working route while you fix the browser at leisure, not as a reason to leave the fault undiagnosed forever.
Intermittent results usually mean an intermittent owner: a flaky home connection, an overloaded router, or the bank's service degrading rather than down. Note the times it fails — a pattern (only evenings, only peak hours) is itself the clue, pointing at congestion at your provider or peak load at the bank rather than any setting of yours.