Skip to main content
The AA orchestration flow lets you collect a user’s financial data through the Account Aggregator framework using a single, unified transactionId. You initiate a consent request, redirect the user to complete consent, track the journey to completion (via webhook or polling), and then fetch the raw data and analytics.
This section covers the pure Account Aggregator flow. Every data item is sourced from AA (dataSource and type are always AA).

​
Integration Flow

A complete AA integration is a four-step journey, all tied together by the single transaction_id you receive in step 1. You initiate consent, hand the user off to the hosted consent screen, track the journey to a terminal state, and then pull the data.
1

Initiate Consent

Call POST /v3/requestconsent to start the journey. You receive a webRedirectionUrl (the hosted consent screen) and a transaction_id to store and reuse for every subsequent call. See Initiate Consent.
2

Redirect the User

Send the user to the webRedirectionUrl to approve consent in the Account Aggregator flow. When the journey ends, the user is returned to your redirectUrl with the outcome. See User Redirection.
3

Track Status

Wait for completion using a terminal webhook push (recommended), by polling, or by listening for in-iframe UI events — all covered on the single Track Status page — until the transaction reaches a terminal state (SUCCESSFUL / UNSUCCESSFUL).
4

Fetch Data

Once the journey is successful, retrieve the raw FI data or the computed analytics (JSON, XML, or Excel) — both on the Fetch Data page — using the same transaction_id.

​
Pages in this section

​
Base URL & Headers

Base URL (UAT / Production): Contact support@moneyone.in. All API requests use these headers:
The analytics and data endpoints also accept an optional x-request-id header for request tracing.

​
Quick Reference

​
Endpoints

​
Required Headers

Need Help?

Contact support@moneyone.in for technical assistance or integration queries.