JIT Funding Inquiry API

JIT Funding Inquiry API is used to retrieve the available credit limit of the cardholder. It is applicable for prepaid products issued on Pine Labs platform.

HTTP Status and Response Status Matrix

  • HTTP Code: This is the response status code issued by a server in response to a client's request made to the server.
  • Error Code: This is the error code returned by Credit+ Issuing application in the ‘code’ field of the response message indicating if the request was processed successfully or failed.
  • Description: This is the description of the error code returned by Credit+ Issuing application.
  • Details: This is the detailed description of the error code returned by Credit+ Issuing application
HTTP CodeReason CodeDescriptionDetails
200OKThe server has successfully processed your request.
400RECORD_NOT_FOUNDRecord not found for given search criteria.
400CREDIT_LINE_ACCOUNT_NOT_CREATEDCredit Line or Funding Source is not created for this loan account number.
400INVALID_FIELD_LENGTH'card_id' field value length must be less than or equal to 24 characters.
400INVALID_FIELD_VALUEIncorrect value for field 'X-MC-Channel'.
400INVALID_FIELD_VALUE'card_id' field value '12344$' must match '^[A-Za-z0-9_!'()+,-.]$'
Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

API consumer must share card_id as a path parameter for API requests. It is a unique identifier of the card. Currently only CNA (Card Number Alias) is considered as the card_id. The Card Number Alias is equivalent to the funding source on Credit+ Issuing system.

Headers
string
^[a-zA-Z0-9-]{1,36}$

API consumer can share unique X-MC-Correlation-ID in HTTP header for each API request. It is recommended to generate UUID (maximum length: 36 alphanumeric characters.) that is compliant with RFC 4122. If it is not shared, then the system generates a unique value for each request. For example, ac97d177-9345-4934-8343-0f91a7a02836

string
enum

API consumer can share X-MC-Channel in HTTP header for API requests. It is the network or channel through which request is routed. The only available value for Channel is API.

Allowed:
string

API consumer can share X-MC-Source in HTTP header for API requests. It identifies the request originators application. For the list of source values, see the Pre-conditions for HTTP Header of REST API topic in the Pre-requisite for Rest API section.

string
length ≤ 50

API consumer can share X-MC-Client-Application-User-ID in HTTP header for API requests. This parameter is a unique identifier to track actual user performing action at the client's end. This field is used only for logging purpose. The maximum length is 50.

Response

Language
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json