Query card BIN configurationSignature required

2026-07-31 02:06

POST /amsin/api/v1/business/worldcard/queryCardBinConfig

Before calling the applyCard API to issue a card, partners can call this API to query available card BIN configurations.

Structure

A message consists of a header and body. For details, see the following sections.

Field	Required	Sample	Description
Client-Id	Yes	`Client-Id: *****`	For more information about these request header fields, see Request structure. To generate`Signature`, see Sign a request and validate the signature.
Signature	Yes	`Signature: algorithm=RSA256, keyVersion=2, signature=*****`
Content-Type	Yes	`Content-Type: application/json; charset=UTF-8`
Request-Time	Yes	`Request-Time: 2019-04-04T12:08:56+08:00`
Connected-AccountId	Conditional	`Connected-AccountId: *****`	Attention Required when a partner manages a customer's account.
Access-Token	Conditional	`Access-Token: ******`	Attention Required for OAUTH authorization. Refer to applyToken.

The type of card.

Valid value is:

The result of the API call.

Show child parameters

Card BIN configuration list.

This field is returned only when resultStatus = S.

Show child parameters

API Explorer

URL

Request Body

Response Body

After calling the API, a response is returned. Possible values for result.resultStatus are:

Code	Value	Message	Further action
SUCCESS	S	Success
PARAM_ILLEGAL	F	Illegal parameters exist. For example, a non-numeric input, or an invalid date.	Check and verify whether the request fields, including the header fields and body fields, are correct and valid. For details on the fields of each API, see the specific API Structure section.
UNKNOWN_EXCEPTION	U	API failed due to unknown reason.	The service might be down, retry later. If the issue persists, contact our Technical Support Team.
SYSTEM_ERROR	F	System error.	Do not retry, and contact our Technical Support Team for more details.
USER_NOT_EXIST	F	The user does not exist.	Retry with the correct user information.
CONTRACT_NOT_EXIST	F	Contract does not exist.	Ensure the Partner has already signed a contract and the input is correct.
ACCESS_TOKEN_EXPIRED	F	The access token expired.	Refresh the token to get a new access token or contact our Technical Support Team to address it.
AUTHORIZATION_NOT_EXIST	F	The authorization does not exist.	Make sure that the input is correct. If the issue persists, contact our Technical Support Team to verify the authorization status.

Result status	Description
`S`	Indicates that the API call succeeded.
`F`	Indicates that the API call failed. For additional information on the failure, refer to result.resultCode.
`U`	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: Maximum 7 queries are allowed. Intervals between queries: 5 min, 10 min, 20 min, 40 min, 80 min, 160 min, and 320 min. If no queries succeed, contact our Technical Support Team.