Apple Pay Remembers Every Tap. Your Budget Can Too

Tap, beep, walk away - and by dinner the amount is gone from memory. Wallet keeps a perfect history of every Apple Pay payment, yet budget apps cannot simply read it: outside Apple's own US-only cards there is no transactions API. There is, however, an official bridge almost nobody flips on. Since iOS 17, Shortcuts ships a transaction trigger - renamed "Wallet" in iOS 26 - that fires the moment you pay by card and can hand the amount and the merchant to any app. Practitioners have been wiring it up for years - Graham Haley's walkthrough is a good tour - and expense trackers are quietly building whole features on it.

How the bridge works

The setup is one automation in the Shortcuts app:

• trigger: a card transaction, on the cards you choose - Apple documents it under Personal Automations
• "Run Immediately" on, so nothing asks for confirmation at the till
• the trigger hands over the payment as a typed currency amount plus the merchant name
• an app action files it in the background - the phone never leaves your pocket

The part that deserves more attention: it all happens on the device. No bank login, no aggregator in the middle, no server that stores your purchases. The payment data goes from Wallet to the app across your own phone and stops there.

Where it breaks - honestly

The trigger rides the same notification your bank sends to Wallet, with a hard timeout. The failure modes are documented at length on Apple's developer forums, open bug reports and all:

1. Slow banks. If the bank reports the transaction late, the automation runs empty or not at all - some banks answer in seconds, some in hours. The payment still lands in Wallet's history; the trigger just stopped waiting.
2. Notification summaries. When iOS summarizes notifications, the Wallet notification can be held past the trigger's timeout. Excluding Wallet from summaries fixes it.
3. Housekeeping. Wallet needs mobile data, and per-card transaction notifications must stay on. And yes - a declined payment can fire the trigger too.

A budget you have to remember is a budget you will forget.

The safety net nobody mentions

Here is the useful asymmetry: the payment ALWAYS exists in Wallet's own history, even when the trigger misses it. So the recovery pattern is simple - open the card in Wallet, screenshot the screen, let a shortcut read the text off the screenshot and log what it finds. Clunky? Slightly. Reliable? Completely: it does not depend on timing at all.

What we are shipping

We have skin in this game: SumiQ 1.0.3 builds this exact stack in. Connect once, and every tap files itself with the amount, the merchant, an auto-picked category - and if you pay in a foreign currency, it converts to your home one on the fly. Payments a slow bank dropped are pulled back through the Wallet-screenshot recovery flow. And for cash or anything else there is Quick Log: double-tap the back of the phone, answer "how much" and "on what", done. It is in TestFlight now and rolls out with the next update - the details live in the changelog. As always: on device, no bank login, no accounts.

---

Bottom line: your iPhone already knows what you spent - the only question is whether that knowledge reaches your budget. Flip the bridge on: automation catches most taps the second they happen, recovery catches the rest, and the ledger fills itself while the receipt is still printing.

Sources: Apple Support, Apple Developer Forums, grahamhaley.co.uk.