This API is used to update the customer's preferred mailing address option (permanent, current or office) forrequestsreceived through various channelssuch as online banking or mobile banking. The Credit+ Issuing system receives, validates, and processes the request. If the request is successful, the mailing address preference is updated, system logs the 'Mailing Address Preference Request' (Service Code: 107) 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. Following are the validations for the Mailing Address Statement Preference Flag: • If 'P' is selected, then system checks if the permanent address is populated or not. If the permanent address is not populated, then the request is rejected with the response message: 'Permanent Address details not present.'. • If 'C' isselected, then system will check whether current addressis populated or not. If it is not populated, then the request is rejected with a response message: 'Current Address details not present'. • If 'O' is selected, then system will check whether office address is populated or not. If it is not populated, then the request should be rejected with a response message: 'Current Address details not present'. If a validation fails, it sends the corresponding error in the response message.
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 | MAIL002 | Invalid device number |
| 400 | MAIL003 | Error while fetching details from device |
| 403 | MAIL004 | Invalid wallet number |
| 400 | MAIL005 | Error while fetching details from wallet. |
| 400 | MAIL010 | Invalid Client code |
| 400 | MAIL012 | Error while fetching details from client |
| 400 | MAIL013 | Invalid Form factor type. |
| 400 | MAIL006 | Error while executing Mailing address preference change API |
| 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 | HDE054 | Active request Already exist |
| 400 | HDE523 | This Service Request is not allowed for Add on device |
| 400 | HDE524 | This Service Request is not allowed for closed device |
| 400 | SERVIC001 | Service request is not applicable to product type. |
| 400 | HDE003 | Error in fetching data from Product |
| 400 | MAIL018 | Request is rejected as current mailing address preference is same as requested. |
| 400 | MAIL001 | Current Address details not present. |
| 400 | MAIL002 | Permanent Address details not present. |
| 400 | MAIL003 | Office Address details not present. |
| 500 | 999 | Internal error |
| 404 | 998 | Device(s) does not exist |
| 400 | HDE004 | Error in updating client details. |
| 400 | 997 | Form Factor field value must have max length 24. |
| 400 | 997 | Note field value must have max length 40. |