PIN Authorization

PIN Authorization API should not be initiated by consumer in case PIN Authentication API failed. Pine Labs also maintains the time difference between these two correlated APIs. It is expected latency of 180 Seconds/ 3 minutes between these two API’s in Production environment. In case PIN Authorization API is not received in 180 Seconds after successful response of API Authentication API, PIN Authorization API will be rejected with Proper Error message.

NOTE: The API, if sent with Card Number Alias (CNA), will fetch the corresponding associated device for further processing only if DEVICE _STATUS_CODE = NORMAL (0) OR (DEVICE_STATUS_CODE = UPGRADE (9) AND UPGRADE_STATUS = 1).

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.
  • Reason: This is the description of the error code returned by Credit+ Issuing application.
HTTP CodeError CodeReason
200000Successful.
400911Mandatory field validation failed.
408912Forward Offset Time limit Violated.
408913Backward Offset Time limit Violated.
408915Pin set operation time limit violated.
404916Incorrect API Reference Number or Device Number.
500917Failed to Set PIN.
500999Error while processing request.
400997Program code field should only contain [A-Z 0-9] and underscore and must start and end with alphanumeric character
400997Program Code field value must have max length 6.
400997Device Plan code field should only contain [A-Z 0-9] and underscore and must start and end with alphanumeric character.
400997Device Plan Code field value must have max length 10.
400997Only alphanumeric characters and underscore are allowed.
400997Card Number Alias field value must have max length 24.
400997Product Type field is invalid.
400997Device Number and Card Number Alias fields are empty. Please provide value for atleast one field.
400CNA001Bank Does Not Exists
400CNA002Card Number Alias Functionality is not applicable forthisInstitution
400CNA003Record does not exists for the given details
400CNA005Multiple device numbers are active for given details
400CNA006Error while fetching device details
400994Invalid Encryption-Algorithm header value
400994Invalid Encryption Request Parameters
400994Cryptography error
Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
Headers
string
^[a-zA-Z0-9-]{1,50}$

API Consumer must share a Correlation-ID in the HTTP header for API requests. The Correlation-ID must be unique for each request. It is recommended to generate universally unique identifier (UUID) of length 32 or 36 that is compliant with RFC 4122. The maximum supported length is 50 alphanumeric characters. For example, ac97d177-9345-4934-8343-0f91a7a02836. If the Correlation-ID is not received in the incoming request, the system generates the UUID dynamically and assigns it to the request.

string

API Consumer can share Source in the HTTP header for API requests. 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.

Response

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