Open Banking & Account Data · Use case
Power personal finance and budgeting apps
Short answer
Users connect all their accounts; the provider aggregates balances and transactions, enriches them with merchant and category data, and keeps them updated. Coverage, enrichment quality and a painless renewal journey decide whether users stay.
What this use case is
Users connect all their accounts; the provider aggregates balances and transactions, enriches them with merchant and category data, and keeps them updated. Coverage, enrichment quality and a painless renewal journey decide whether users stay.
Who builds this
What your customer sees
- 1Connects several banks
- 2Sees all balances in one place
- 3Gets categorised spending insights
- 4Renews access occasionally
How Open Banking & Account Data solves it
User connects accounts
User connects accounts
Provider aggregates balances and transactions
Provider aggregates balances and transactions
Enrichment adds merchant, category and recurring payments
Enrichment adds merchant, category and recurring payments
Data refreshed on schedule
Data refreshed on schedule
Insights calculated in your app
Insights calculated in your app
Consent renewals prompted in time
Consent renewals prompted in time
Want to have
- Broad retail bank coverage
- Card and credit account data where available
- Enrichment and categorisation
- Scheduled refresh
- Renewal journeys
- Webhooks
Optional
- Subscription detection
- Savings and investment accounts
- Payment initiation for transfers between accounts
Design decisions
Data scope
simplicity versus a complete picture.
What to put in your RFP
Coverage
- banks and account types
Data
- refresh
- enrichment
Engagement
- renewal flows
Commercials
- per user pricing
How to evaluate providers for this use case
- 1Coverage for your users
- 2Enrichment accuracy
- 3Renewal conversion
Pitfalls
- Per-user pricing that does not fit a free app
- Renewal drop-off eroding the user base
- Enrichment errors undermining trust
What providers will ask you
- Target markets
- Expected users
- Monetisation model
Other Finlane categories that cover parts of this
This use case is solved mainly with Open Banking & Account Data. These categories cover specific parts of it and can be tendered alongside it.
Frequently asked questions
Other Open Banking & Account Data use cases
Aggregate salary, expenses and balances across a user's accounts to power credit or KYC decisioning.
Add pay-by-bank checkoutOffer instant account-to-account payments as a cheaper alternative to cards, with SCA built in.
Automate accounting and reconciliationPull transactions and balances into an accounting or FP&A product, categorised and enriched.