How to use the AA APIs?

Once the FIU/LSP receives the Account Aggregator access they can leverage the Signzy solution to integrate the AA journey on their platforms/onboardings etc.

The Account Aggregator APIs work in the following sequence -

Create Consent Request:
- The FIU initiates a request to access the end customer's financial information from financial institutions(FIPs).
- This request can be initiated through APIs and the consent approval link can either be sent via SMS or can be done through a frontend redirection on the application interface.
- The end-user goes through the consent approval journey by clicking on the link and selects the institutions they want to fetch data from and provide to the FIUs.
Checking Consent Status:
- After the consent approval journey is submitted, the FIU checks the status of the consent provided by the user.
- If the consent is pending or not yet accepted, the end-user can be prompted to provide or confirm their consent.
Requesting Financial Information:
- Once the consent is accepted, the FIU generates a request to the Account Aggregator platform to fetch financial information from the selected institutions.
- This request includes details such as user identifiers, and the time range of data requested.
Checking Status of Financial Information Request:
- The FIU can periodically check the status of the financial information request made to the Account Aggregator platform.
- It can also utilize callback URLs to receive asynchronous updates on the status of the request.
- Alternatively, it can also make real-time/synchronous API calls to query the status.
Fetching Financial Information:
- Once the financial information is ready, the FIU can fetch it from the Account Aggregator.
- The data can be fetched in two formats such as JSON and XML based on the FIU's preference.
- Additionally, Signzy also provides options for the FIU to fetch analytics reports based on transactional details fetched in the financial data.

Singzy also provides multiple features to enable faster and custom developments by the FIUs such as -

Callback URLs and Response for Status Checks API:

Callback URLs are used to receive real-time updates on the status of consent requests and financial information requests.
The system registers callback URLs during the initial request creation process.
When there is a status change in the request (e.g., consent accepted, data ready), Signzy sends notifications to the registered callback URLs.
Response for the status checks API provides detailed information about the current status of the request, allowing the system to track progress and take appropriate actions accordingly.

Analytics Report Generation:

The system utilizes the fetched financial information to generate analytics reports.
End customers can request analytics reports based on transactional details.
Reports can be generated in formats such as PDF, Excel, or JSON, providing flexibility for data consumption and analysis.