DISBURSAL STATUS V2 API

DISBURSAL STATUS V2 API

PART I: INTRODUCTION
This api is used to get status of loan amount disbursal along with UTR details.

PART II: ABOUT DISBURSAL STATUS V2 API

The description and specific workflow is as follows:
1. Partner need to send the particular mandatory parameters in the request along
with the Authentication mechanism.
2. If the “accountId” of the customer is valid , then following are the cases:
The partner provides details to be updated.

PART III: API GUIDE

API NAME Disbursal Status API
URL https://b2bpartner-api-uat.abfldirect.com/disbursalStatusV2
HEADERS Content-Type : application/json
Partner specific (X-AUTH-TOKEN , X-API-KEY etc.)

P.S. – URL is case-sensitive

e.g.
a.) For X-AUTH-TOKEN –
{
“Content-Type: application/json”,
“X-AUTH-TOKEN: token_generated_from_token_api”
}
PART IV: REQUEST
The request should contain following parameters:

Parameter Description Type of variable and MANDATORY/NON-

Name condition on it MANDATORY
accountId Application id of  Type - String  MANDATORY
the customer at  Should not contain any
partner side. special character.
 Allowed Chars –
ascii_lowercase +
ascii_uppercase +
[‘-’ , ‘_’]
loan_no Loan no as  Type - String  MANDATORY
received in  Should not contain any
DrawDown special character.
response  Allowed Chars –
ascii_lowercase +
ascii_uppercase +
[‘-’ , ‘_’]

PART V: SAMPLE REQUEST

{
"accountId": " GROWW914270 ",
"loan_no": "LXN-D06827-280003132"
}

PART VI: RESPONSE TYPES

HTTP STATUS STATUS CODE DESCRIPTION

CODE
200 SUCCESS Disbursal Status
successfully got.
200 IN_PROGRESS Loan disbursement in
Progress.
400 ERROR BAD_REQUEST This can come in various
conditions:
  When Mandatory
parameter is missing
from request
 Some Field which can’t
be blank is left blank
BUSINESS_RULE_ERROR When unable to generate
deal number from LMS
404 ERROR BUSINESS_RULE_ERROR When some error occurred
while fetching the
Disbursal status
ERROR INVALID_LOAN_NO When loan_no is invalid
ERROR BANK_ERROR When there is an error at
Bank’s end
500 ERROR INTERNAL_SERVER_ERROR Server Error at ABFL side
502 ERROR DEPENDENCY_ERROR This can come in various
conditions:
 Server Error at LMS

PART VII: SAMPLE RESPONSES

CASE CONDITION RESPONSE STATUS

CODE
Success When details { 200
are "responseStatus": "SUCCESS",
successfully "data":{
updated " loan_no ":" LXN-D06827-280003132",
"disbursalStatus":"Loan is fully disbursed.",
"utrNo":"12345",
}
}
IN_PROGRESS When loan { 200
disbursement "responseStatus": " IN_PROGRESS",
is in progress "data":{
" loan_no ":" LXN-D06827-280003132",
"disbursalStatus":"Loan disbursement in
Progress.",
"utrNo":"",
}
}
FAILURE When any of { 400
mandatory "responseStatus": "ERROR",
field is not "error": {
present "code": "BAD_REQUEST",
"description": "accountId key is missing",
"errorType": "MISSING_ACCOUNT_ID"
}
}
When any of { 400
field is left "responseStatus": "ERROR",
blank, which "error": {
can’t be left "code": "BAD_REQUEST",
blank "description": "accountId can not be empty",
"errorType": "INVALID_PAYLOAD"
}
}
When there is { 404
an error at "responseStatus": "Error",
Bank’s end "error":{
"code": "BANK_ERROR ",
"Bank_response": "Invalid account number",
"utrNo":"",
}
}
Note: Actual Bank_response may vary, due to varying
error response messages from bank end.
When account { 404
Id is incorrect "responseStatus": "ERROR",
"error": {
"code": "INVALID_APPLICATION",
"description": "Application does not exist",
"errorType": "Provided Account ID is not found"
}
}
When loan_no { 404
is invalid "responseStatus": "ERROR",
"error": {
"code": "INVALID_LOAN_NO",
"description": "LOAN_NO does not exist",
"errorType": "Provided loan_no is not found"
}
}
Technical { 500
Issues "responseStatus": "ERROR",
"error": {
"code": " INTERNAL_SERVER_ERROR ",
"description": " SOMETHING_WENT_WRONG ",
"errorType": " INTERNAL_SERVER_ERROR "
 }
}