iOS Shortcut Automation for NZ Banking and Finance Apps
I set up finance automation shortcuts about three years ago after realizing I was spending roughly twenty minutes per day just logging into my Kiwibank, ANZ, and Myerpay accounts on my iPhone. That added up to about five hours a week, which was ridiculous for something as mundane as checking transaction history. The core of what most people call Unlocking Efficiency iOS Assistants Finance Login Nz A Quick Access Guide is really just Shortcuts + Apple's Secure Notes + Keychain integration, used together in a specific sequence. It is not magic, and it does not replace good password hygiene, but it does reduce repetitive login flows significantly. Before diving into the setup, I need to say this clearly: some NZ banks actively resist automation. ASB and Westpac have historically pushed back against third-party automation tools for their mobile apps, and I have seen users get temporarily locked out after running too many rapid login attempts through scripted shortcuts. I learned that the hard way in 2023 when my ASB app flagged my account after a shortcut ran authentication checks every fifteen minutes. The workaround was simple — I dropped the interval to once per hour and disabled any biometric-skipping logic that tried to bypass the app's native 2FA prompt. That stopped the lockouts immediately.
Unlocking Efficiency iOS Assistants Finance Login Nz A Quick Access Guide
The practical structure looks like this. You build a Shortcuts workflow that chains together these actions: open the banking app, trigger the keychain-stored credentials, pass through the 2FA step using a saved code from your authenticator or notes, then navigate to the specific dashboard screen you actually want to see. The whole chain typically takes eight to twelve seconds on an iPhone 13 or newer. Older devices like an iPhone XR might take closer to twenty seconds due to app load times, not the shortcut itself. The single most important component is the Secure Notes field. iOS lets you store custom key-value pairs in Notes that shortcuts can read without exposing them to other apps. I store my bank app usernames, 2FA seed codes, and even my PIN entry sequences as structured note fields. Here is how I format it: Kiwibank Login
Username: [redacted]
2FA Seed: JBSWY3DPEHPK3PXP
Pin Entry: 1-4-7-2-5-8
This is not more secure than using your bank's own app features alone. But it makes automation possible because the shortcut can pull the data without you typing anything. The counter-intuitive part that nobody talks about is the Numeric Keypad Simulation Limitation. Most NZ banking apps use on-screen numeric pads for PIN entry rather than accepting standard keyboard input. This means you cannot simply send a "type password" action — you have to tap coordinates or use the app's own accessibility labels to simulate button presses. In practice, this means you need to test your shortcut on the exact device you will use it on. A shortcut that works perfectly on an iPhone 15 Pro may completely fail on an iPhone 12 because the screen dimensions and accessibility label paths differ slightly. My workaround for this was building the PIN entry using the "Get Accessibility Node" action in Shortcuts, which reads the actual on-screen button labels rather than relying on screen coordinates. This method is slower — it adds roughly three seconds per tap — but it is far more reliable across different device models. I abandoned coordinate-based tapping entirely after watching my shortcut accidentally enter "888888" instead of my actual six-digit PIN on a software update that shifted the app's layout by twelve pixels.
Get the Full Details
Another detail people miss is the difference between Fast App Switching and background app refresh. If you enable "Run While Hidden" in your shortcut settings, iOS will often still kill the banking app's connection before the shortcut completes the login flow. The solution is to explicitly include a "Wait for App to Launch" action with a timeout of five seconds before proceeding to credential entry. This sounds trivial but accounts for most failed attempts I see in forum threads. For 2FA specifically, I recommend against storing your actual TOTP codes in the Shortcuts app itself. The Shortcuts app caches data in a way that makes it accessible through system diagnostics if someone unlocks your phone. Store the codes in a dedicated Secure Note that is not synced to iCloud — use the local-only option when creating the note. This creates a small barrier that most casual snoopers will not get past. The automation also has clear limits. It will not work for any bank requiring a hardware token or SMS-based one-time password sent to your phone number. If your institution uses Push2Sign or a similar push-notification approval system, the shortcut can open the app and navigate to the approval screen, but it cannot approve the login for you. I have built separate shortcuts that just open the right screen and wait for manual approval, which still saves about forty seconds compared to manual navigation, but it is not fully hands-off.
Some banking apps also detect automation through timing analysis. If every login happens at exactly the same interval — say, every hour like clockwork — the app's fraud detection may flag it. I solved this by adding a random delay between three and eight seconds to the shortcut using the "Pick Random Number" action. It is a small change but enough to make the pattern look more human. Here is the exact shortcut configuration I use for my primary New Zealand checking account. The action chain is open app wait five seconds get note field "Username" type username tap Next get note field "2FA Seed" generate current TOTP type TOTP wait three seconds get note field "Pin Entry" simulate four taps with accessibility nodes wait for dashboard end. Total execution time is approximately nine seconds on my current device. On my wife's iPhone SE second generation, which has a smaller screen and slower processor, it takes about fourteen seconds. If you are concerned about the security trade-offs, you are right to be. Any shortcut that accesses your credentials is a potential exposure point. The mitigation steps are straightforward: use a passcode on your iPhone, do not add the shortcut to Siri suggestions, and review your shortcut's permissions monthly. I check mine every Sunday evening. I also keep a separate "clean" phone for financial tasks that has no other apps installed beyond my banking apps and the shortcut runner itself.
The biggest practical benefit I have found is not the time saved per login — that is maybe two minutes per session — but the mental friction removed. When you eliminate the decision-making of "which app do I open first, where is my 2FA code, what was my PIN again," you reduce the cognitive load around checking your finances. That matters more than the raw speed gain, especially when you are doing it multiple times a day.
