A practical comparison
| Method | Strengths | Limitations |
|---|---|---|
| Direct bank aggregation | Can provide broad account history, balances and standardized feeds where supported. | Coverage varies by bank and country; may require a regulated intermediary, consent flow or credentials/token relationship. |
| Android notifications | Fast capture, no direct bank login, local access to alerts from apps selected by the user. | Android only; depends on notification delivery and message detail; historical transactions may be absent. |
| Transaction emails | No bank login, often includes rich purchase details, can cover events missed as push alerts. | Requires mailbox permission; formats vary; irrelevant mail must be filtered carefully. |
| Statements or exports | Authoritative cycle records and useful reconciliation source. | Usually delayed and requires periodic import or manual handling. |
Privacy and credentials
Notification- and email-based approaches can avoid direct online-banking credentials. Email access is still sensitive and should be narrowly scoped, transparent and revocable. Aggregation may be appropriate when a trusted provider offers reliable coverage and the user values complete account feeds.
Availability and reliability
No method is universally available. A bank may support aggregation but provide poor alerts, or send detailed email while lacking an accessible API. Device power management, email delays and changed message formats can also affect capture.
A combined approach
Some people use notifications for speed, email as a second capture source and statements for reconciliation. Deduplication and review then matter more because one purchase may appear several times.
Where Stash fits
Stash focuses on selected Android bank notifications and optional read-only Gmail transaction import, without requesting bank login credentials. It is a deliberate alternative, not a claim that notification tracking is superior for every user.