post https://uatmea-iss-apigw.creditpluspinelabs.com/deviceapi/apis/v1/cardholder/card/cardrenew
The card renewal API allows the end user or customer to enable or disable the card renewal. This API enables Renewal Option flag at card/device level or disables this flag at card/device level. Based on this flag, the card renewal batch picks this card/device for renewal. This API is effective only when Allow Renewal flag at device plan level is enable. For example, If out of 100 cardsissued under Program X with device level plan A, and you want to renew only 50 cards. Then, the Card Renewal API is called with request parameters, such as card number or card pack ID and renewal yes or no.
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 |
---|---|---|
400 | 997 | Form Factor Type field is mandatory. |
400 | 997 | Form Factor Type should be CRD or CPI |
400 | 997 | Form Factor field is mandatory |
400 | 997 | Device Number is of invalid format |
400 | 997 | Card Pack ID is of invalid format |
400 | 997 | Renewal flag should be either Yes or No |
400 | 998 | Device Number not registered in the system |
400 | 998 | No Card Pack ID found for given details |
201 | 999 | Allow renewal is disabled. Please contact bank |
201 | 000 | Request processed successfully |
500 | 913 | Backward offset time limit violated |
400 | 994 | Invalid Request - Unrecognized field |
400 | 988 | Encryption type Not Supported |
400 | 913 | Forward offset time limit violated |
400 | 994 | Invalid Encryption - Algorithm header value |
400 | 994 | Invalid Encryption Request Parameters |
400 | 994 | Cryptography error |