Credit + Issuing system will receive the Card Activation API request call and responds back with the Card Activation API response. If the response issuccessful, then device number/ Pack ID given in request will be activated. Else, appropriate message will be displayed. For this API, Device plan Activation mode will be “MANUAL”. For any other mode the activation request will be rejected. For this API, If in Device plan “PIN Data Transmission” is set as “PIN Via SMS” and “Card Activation - API” is selected in “PIN via SMS triggering events”, then clear PIN will be sent to cardholder on registered mobile number after successful card activation. If the system is not able to send the clear PIN due to an internal error, then original card activation request will not have any impact. Card Activation API will be applicable for personalized/non-personalized devices. In case of paired cards, only Primary Device will be activated. This API will not activate Paired Device.
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 Code | Error Code | Description |
|---|---|---|
| 400 | 400 | Request Parameters Validation Failure: Invalid Request |
| 201 | 404 | Device(s) does not exist |
| 201 | 500 | Request processing error |
| 201 | VALFRM028 | Invalid Device Number |
| 201 | VALFRM029 | Invalid Device Plan |
| 201 | VALFRM040 | Not allowed for Virtual Cards |
| 201 | VALFRM030 | Device is already Activated |
| 201 | VALFRM031 | Device is Cancelled |
| 201 | VALFRM032 | Device is Replaced |
| 201 | VALFRM034 | Device is Expired |
| 201 | VALFRM037 | Error while accessing stoplist data |
| 201 | VALFRM038 | Device is stoplisted |
| 201 | VALFRM033 | Device is not Normal |
| 201 | VALFRM035 | Device is not Delivered |
| 201 | VALFRM036 | Device is not Registered |
| 201 | VALFRM039 | Device cannot be activated as activation mode is not configured as manual. |
| 201 | ACTDEV004 | Invalid Card Pack ID |
| 201 | ACTDEV005 | Invalid Device Number |
| 201 | ACTDEV006 | Invalid Program |
| 201 | ACTDEV001 | Invalid Transaction Code |
| 201 | ACTDEV003 | Failed when updating device |
| 201 | ACTDEV002 | Log statement request is failed due to internal error. Please contact system admin. |
| 201 | VALFRM003 | Invalid Device |
| 201 | VALFRM005 | Invalid Card Pack ID |
| 201 | VALFRM007 | Invalid form factor type |
| 400 | 997 | Only alphanumeric characters and underscore are allowed |
| 400 | 997 | Form Factor field value must have min length 10. |
| 400 | 997 | Form Factor field value must have max length 24 |
| 400 | 997 | Device Plan Code field value must have max length 10. |
| 400 | 997 | Device Plan Code field should only contain [A-Z 0-9] and underscore and must start and end with alphanumeric character. |
| 400 | 997 | Program Code field value must have max length 10. |
| 400 | 997 | Program Code field should only contain [A-Z 0-9] and underscore and must start and end with alphanumeric character. |
| 400 | 997 | Product Type field is invalid. |
| 400 | CNA001 | Bank Does Not Exists |
| 400 | CNA002 | Card number Alias functionality is not applicable for this institution. |
| 400 | CNA003 | Record does not exist for the given details |
| 400 | CNA005 | Multiple device number are active for given details |
| 400 | CNA006 | Error while fetching device details. |
| 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 |