Both AA and PDF appear in every contract on these pages. A single, unified
transactionId ties the
whole journey together — you use the same identifier for status polling, raw data fetch, and analytics,
regardless of whether the data ultimately arrived via AA or PDF.Integration Flow
A complete journey is tied together by the singletransaction_id returned in step 1.
AA is attempted first; the smart router transparently falls back to a PDF statement upload
when AA cannot deliver — all within the same journey and the same transaction_id.
1
Initiate Consent
Call
POST /v3/requestconsent to start the journey and receive a transaction_id. See
Initiate Consent.2
Redirect the user
Send the user to
webRedirectionUrl to complete the AA consent journey. See
User Redirection.3
Smart routing & fallback
AA is attempted first. If AA cannot deliver, the smart router falls back to PDF statement upload
within the same journey.
4
Track status
Monitor completion via webhook (recommended), status polling, or in-iframe UI events —
all covered on the Track Status page. Each surfaces the AA block,
the PDF block, and the routing decision.
5
Fetch data
Once the journey is
SUCCESS, retrieve the raw FI data or normalized analytics —
both on the Fetch Data page.Pages in this section
Base URL
Base URL (UAT / Production): Contact support@moneyone.in
Common Headers
Every API request on these pages uses the following headers: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.