Query cardholder detailSignature required
Partners can call this interface to retrieve the detailed information of a particular cardholder.
Structure
A message consists of a header and body. For details, see the following sections.
Request header
Field | Required | Sample | Description |
Client-Id | Yes |
|
|
Signature | Yes |
| |
Content-Type | Yes |
| |
Request-Time | Yes |
| |
Connected-AccountId | Conditional |
| Attention Required when a partner manages a customer's account. |
Access-Token | Conditional |
| Attention Required for OAUTH authorization. Refer to applyToken. |
Request parameters
cardholderId String REQUIRED
Unique identifier for the cardholder.
Response parameters
result Result REQUIRED
The result of the API call.
cardholderId String REQUIRED
Unique identifier for the cardholder.
auditStatus String REQUIRED
Status of the audit.
Valid values are:
APPROVEDPENDINGREJECTED
availableStatus String REQUIRED
The status of the card.
Valid values are:
T: UsableF: Not usable
cardholderType String REQUIRED
Cardholder type. Valid values are:
INDIVIDUALEMPLOYEESHAREHOLDER
cardholderInfo Object REQUIRED
The information of the card holder.
Request
Response
Result processing logic
After calling the API, a response is returned. Possible values for result.resultStatus are:
Result status | Description |
| Indicates that the API call succeeded. |
| Indicates that the API call failed. For additional information on the failure, refer to result.resultCode. |
| Indicates that the API call result is unknown. If this status is returned, the Partner may make a query. The querying strategy is as follows:
If no queries succeed, contact our Technical Support Team. |
result.resultCode
| Code | Value | Message | Further action |
|---|---|---|---|
| SUCCESS | S | Success | |
| PARAM_ILLEGAL | F | Illegal parameters exist. For example, a non-numeric input, or an invalid date. | Refer to the API documentation page and confirm whether the request headers and parameters are correct. |
| SYSTEM_ERROR | F | System error. | Do not retry. Contact WorldFirst technical support for details. |
| SERVICE_NOT_ALLOWED | F | Service not allowed. | Retry with the correct information. If the issue persists, contact WorldFirst technical support. |
| UNKNOWN_EXCEPTION | U | API failed due to unknown reason. | Server error. If retrying later does not resolve the issue, contact WorldFirst technical support. |
| REQUEST_TRAFFIC_EXCEED_LIMIT | U | The request traffic exceeds the limit. | Retry. If the issue persists, contact WorldFirst technical support. |
| OAUTH_FAIL | F | OAuth process failed. | Contact WorldFirst technical support for details. |
| INVALID_API | F | The called API is invalid or not active. | Confirm whether the correct API is being called. |
| INVALID_CLIENT | F | The client is invalid. | Client ID does not exist or is invalid. |
| INVALID_SIGNATURE | F | The signature is invalid. | Confirm that the request is correctly signed. |
| METHOD_NOT_SUPPORTED | F | The server does not implement the requested HTTP method. | Confirm that the HTTP request method is POST. |
| CONTRACT_CHECK_FAIL | F | The contract check has failed. | Contact WorldFirst technical support to understand the contract status before retrying. |