Consumer Products · Workflow

Account Aggregator consent and fetch (Personal Finance)

The user links bank accounts through consent, sees categorised data and can revoke at any time.

Step by step

Each step is a governed Action: it is permission-checked, logged, and either reversible or compensated.

1
The user sees the purpose, data types, date range, fetch frequency and expiry before linking.
2
A consent request goes through the licensed FIU partner to the Account Aggregator.
3
The user approves in the Account Aggregator flow with OTP.
4
Data is fetched within the consent and normalised into accounts and transactions.
5
Transactions are categorised, recurring series detected and budgets updated.
6
On revoke, fetching stops and fetched data is deleted or kept per the user's choice and the purge policy.

Tell us about your team and the outcomes you want. We will walk you through the apps, the Digital Employees and the plan for your industry.