Implement a Yapily data enrichment flow combining account aggregation with transaction categorization for a B2B expense analytics platform

Steps

1. Create an institution connection for the user by POST /account-auth-requests with applicationUserId, institutionId, and callback; redirect the user to the returned authorisationUrl to complete Open Banking consent
2. After redirect, exchange the consent token by POST /accounts with the consent header; receive a list of accounts including accountType, balance, and currency
3. Fetch transactions via GET /accounts/{accountId}/transactions?from=YYYY-MM-DD&to=YYYY-MM-DD using the consent header; Yapily returns raw transaction data including merchant name, amount, transaction type, and ISO category codes where provided by the ASPSP
4. Enrich raw transactions using Yapily's categorization (where enabled in your plan) by checking the enrichment object on each transaction; fields include transactionCategory, merchant, and logo URL
5. For ASPSPs that do not provide categorization data, forward raw transactions to a categorization service (e.g., Plaid Enrich or your own ML model) using the transaction narrative as input
6. Aggregate enriched transactions by merchant and category across multiple connected accounts; store the accountId, institutionId, and consent expiry date per connection to manage re-consent workflows proactively