Initiate Transaction

Call this endpoint to start the PDF upload journey. The request uses the same POST /v3/requestconsent endpoint as other orchestration flows. The PDF-only behaviour is configured per product — no extra request fields are needed to enable it.

POST /v3/requestconsent

Base URL (UAT / Production): Contact support@moneyone.in

Headers

Header	Description
`Content-Type`	`application/json`
`client_id`	Your client ID
`client_secret`	Your client secret
`organisationId`	Your organisation ID
`appIdentifier`	Your app identifier

Request Body

{
  "vua": "<mobile_number>@onemoney",
  "accountID": "<account_id>",
  "productIDList": ["<product_id_1>", "<product_id_2>"],
  "partyIdentifierValue": "<mobile_number>",
  "partyIdentifierType": "MOBILE",
  "redirectUrl": "<your_redirect_url>",
  "pan": "<pan_number>"
}

Request Parameters

string

required

Virtual User Address (e.g., 9876543210@onemoney).

string

required

Unique account identifier.

array

required

Array of product IDs for the journey. Use either this or productID.

string

required

Single product ID. Use either this or productIDList.

string

required

User identifier value (mobile, PAN, Aadhaar, etc.).

string

required

Type: MOBILE, PAN, AADHAR, EMAIL, DOB, GSTIN.

string

URL the user is returned to after completing the journey.

string

User’s PAN.

string

Optional client-supplied transaction identifier.

object

Optional configuration, including the FI data date range.

`config` example

{ "config": { "fiDataRange": { "from": "2023-01-01T00:00:00.000Z", "to": "2024-01-01T00:00:00.000Z" } } }

Response

{
  "ver": "1.21.0",
  "status": "success",
  "data": {
    "webRedirectionUrl": "<web_redirection_url>",
    "transaction_id": "<transaction_id>"
  },
  "message": "Success"
}

Store the transaction_id — it is the single identifier you use for status polling, raw data fetch, and analytics. The webRedirectionUrl carries a time-bound access_token; do not modify it.

PDF-only behaviour: When your product is configured for PDF-only, the user is taken directly to the bank statement upload screen — no Account Aggregator consent is involved. The journey collects PDF bank statements, processes them through OCR, and extracts structured financial data. You will see only a PDF block in the Track Status responses.

Error Codes

HTTP Status	Condition
`400 Bad Request`	Required fields are missing or have an invalid format (e.g. missing `vua`, invalid `partyIdentifierType`).
`401 Unauthorized`	Credentials are missing or invalid in the `Authorization` header.
`500 Internal Server Error`	An unexpected server-side error occurred.

Next steps

Continue to User Redirection.

AA Enabled

AA + PDF Enabled

PDF Enabled

Checks Enabled

KYC

Headers

Request Body

Request Parameters

`config` example

Response

Error Codes

Next steps

​Headers

​Request Body

​Request Parameters

​config example

​Response

​Error Codes

​Next steps

Headers

Request Body

Request Parameters

`config` example

Response

Error Codes

Next steps