Reset PIN Retry Counter API (V1)

post

https://uatmea-iss-apigw.creditpluspinelabs.com/deviceapi/apis/v1/services/helpdesk/resetpinretrycounter

This API is used to reset PIN retry counter for requests received through various channels such as online banking or mobile banking.
The Credit+ Issuing system receives, validates and processes the request. If the request is successful, PIN retrial attempts counter is reset, system logs the “Reset Pin Retry Counter” (Service Code: 109) service request (SR) and sends the service request details in the response message. If the request fails, the system returns the corresponding error code in the response and the SR is not logged.
NOTE: This API is specific for users who are currently using version 1 of this API. For using version 2 of this API, refer to the Reset PIN Retry Counter API (V2) section.

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 Code	Error Code	Reason
201	CCRBO0004	Request processed successfully
400	997	Reset Pin Retry Counter failed: invalid request
403	900	Invalid User
404	998	Device(s) does not exist
500	999	Invalid Request Type
400	997	Request Date should be less than or equal to institution date.
400	997	Request Date field must be in MM/dd/yyyy HH:mm:ss format.
404	998	NO_DEVICE_ERROR
500	RP101	DEVICE_ERROR
400	RP102	Invalid Device Plan.
500	RP103	Error while retrieving data from device plan
500	RP107	Error while executing Retry pin reset counter through AP
400	HDE050	Institution code is mandatory
400	HDE051	Device number is mandatory
400	HDE052	Service code is mandatory.
400	HDE053	Error in fetching data from service_code_mst.
400	HDE100	Device is not in normal state
400	HDE006	Invalid Device Number
400	HDE504	Reset Pin Blocked Request Service is not available for virtual devices

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

deviceNumber

string

required

length ≤ 24

^[0-9]+$

Unique number of the device. Numeric.

priorityRequest

string

enum

Indicates whether this request needs to be taken on priority. Must be 0 (No priority) or 1 (Priority request).

Allowed:

note

string

length ≤ 4000

Any free text that requestor may want to send for logging purpose.

channel

string

length ≤ 10

Accessing channel.

requestDate

string

required

^(0[1-9]|1[0-2])/(0[1-9]|[12][0-9]|3[01])/([0-9]{4}) ([01][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9]$

Date on which the request is sent. Format MM/DD/YYYY HH:MM:SS. Must be less than the institution date.

Headers

Correlation-ID

string

^[a-zA-Z0-9-]{1,50}$

API Consumer must share Correlation-ID in the HTTP header for API requests. The Correlation-ID must be unique for each request. It is recommended to generate a 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.

Source

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

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

201Successful PIN retry counter reset