| Bookmark Name | Actions |
|---|
Account Aggregation Architecture
This section shows the architecture of the Account Aggregation Microservice.
Account Aggregation microservice elements are explained in the below table.
|
Element |
Description |
|---|---|
|
Other Bank Directory |
Holds the other bank details |
|
Salt Edge Integrator |
Communicates with the TPP provider and transfers the respective account and transaction details to the Arrangement and Holdings microservices. |
|
External Connection Manager |
holds the connection details of the TPP for every digital profile user |
|
Tracker |
Tracks whether the account transactions and balances are successfully loaded to the respective microservice |
The workflow among various microservices in this architecture is explained below:
- The Arrangement microservice holds the static details of the accounts received from the TPP provider.
Holdings microservice stores the account balances and transactions. - The Consent microservice stores the consent received from the TPP.
- The Notification microservice acts as an intermediate layer between the Account Aggregation Microservice and Fabric. It generates notifications for the events defined below and sends the request to Fabric.
- Fabric then forwards and displayed the message to the respective customer through text message, email or app notification.
Add Bookmark
save your best linksView Bookmarks
Visit your best links
BACK
Are you sure you want to log-off?