transactionId. The user uploads
their PDF bank statements, which are processed through OCR and document analysis to
extract structured financial data and analytics.
This section covers the pure PDF statement-upload flow. Every data item is sourced
from PDF (
dataSource and type are always PDF). No Account Aggregator (AA)
consent is involved.Integration Flow
A complete PDF integration is a four-step journey, all tied together by the singletransaction_id you receive in step 1. You initiate the transaction, hand the user off
to the hosted upload screen, track the journey to a terminal state, and then pull the data.
1
Initiate Transaction
Call
POST /v3/requestconsent to start the journey. You receive a
webRedirectionUrl (the hosted upload screen) and a transaction_id to store and
reuse for every subsequent call. See Initiate Transaction.2
Redirect the User
Send the user to the
webRedirectionUrl to upload their bank statement PDFs.
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): Contactsupport@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.