Fetch Customer Accounts
This api fetches customer accounts from NPCI. accounts will be present in the response only if gatewayResponseCode = "00". In case there are one or more accounts fetched, vpaSuggestions will be sent in response.
Note: In case merchant retires this api, the accounts will be fetched from NPCI again.
application/json
Will be shared while onboarding.
Will be shared while onboarding.
application/json
This is an epoch unix timestamp string. For example, 1496918882000. It can be used by us to invalidate older requests.
This is a signature over combination of headers, payload. Refer Signature Calculation section for more details.
Merchant generated unique profile id for customer
Constraints: Alphanumeric string with dot(.). Maximum length is 256.
Unique id sent to UPI switch for the request
Constraints: 35 character alphanumeric. Should always start with merchant prefix provided.
Device fingerprint of the customer
Bank code (IIN) of selected bank
Stringified JSON for udf parameters
Account Type(In CC TPAP should send accountType as CREDIT, in other cases they can skip sending this field)
PSP status of the API
Values: SUCCESS|FAILURE
PSP response code for the API
Values:Refer error code section
PSP response message for the API
Values:Refer error code section
Unique id for the merchant as passed in request headers
Unique id for the merchant channel as passed in request headers
Merchant generated unique profile id for customer as passed in the request
Mobile number of the customer
Values:12 digits mobile number string
Transaction id returned by gateway
Response status returned by gateway
Values:SUCCESS, FAILURE
Response code returned by gateway
Response message for code returned by gateway
Bank accounts as returned by NPCI for the customer mobile number
Values:Array of accounts
Vpa suggestions for the bank accounts fetched
Values:Array of strings
Udf parameters as passed in the request
Have questions?
- Need help? Contact support
- LLM? Read llms.txt

