Skip to main content
Call this endpoint to start the consent journey. The request is identical to the AA-only flow — the PDF fallback is handled automatically by the smart router and requires no extra request fields. 
POST /v3/requestconsent
Base URL (UAT / Production): Contact support@moneyone.in

​
Headers

HeaderDescription
Content-Typeapplication/json
client_idYour client ID
client_secretYour client secret
organisationIdYour organisation ID
appIdentifierYour 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>",
  "fipID": ["<fip_id_1>", "<fip_id_2>"],
  "pan": "<pan_number>"
}

​
Request Parameters

​
vua
string
required
Virtual User Address (e.g., 9876543210@onemoney).
​
accountID
string
required
Unique account identifier.
​
productIDList
array
required
Array of product IDs for multi-consent. Use either this or productID.
​
productID
string
required
Single product ID. Use either this or productIDList.
​
partyIdentifierValue
string
required
User identifier value (mobile, PAN, Aadhaar, etc.).
​
partyIdentifierType
string
required
Type: MOBILE, PAN, AADHAR, EMAIL, DOB, GSTIN.
​
redirectUrl
string
URL the user is returned to after completing the journey.
​
fipID
array
Array of FIP identifiers to target.
​
pan
string
User’s PAN.
​
transactionID
string
Optional client-supplied transaction identifier.
​
fitype
array
Optional list of FI types to request.
​
config
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 across both AA and PDF. The webRedirectionUrl carries a time-bound access_token; do not modify it.
PDF fallback behaviour: AA is always attempted first. When AA cannot deliver (e.g. an unhealthy FIP, a rejected consent, or no data), the smart router automatically falls back to a PDF statement upload within the same journey. No additional request fields are needed to enable this — the fallback is configured per product. You will see both an AA block and a PDF block in the Track Status responses.

​
Error Codes

HTTP StatusCondition
400 Bad RequestRequired fields are missing or have an invalid format (e.g. missing vua, invalid partyIdentifierType).
401 UnauthorizedCredentials are missing or invalid in the Authorization header.
500 Internal Server ErrorAn unexpected server-side error occurred.

​
Next steps

Continue to User Redirection.