consultPayout
Use this interface to inquire about the expected payout results before calling the createPayout API to initiate a payout.
Structure
A message consists of a header and body. The following sections are focused on the body structure. For the header structure, see：
Note: Set the data type of each field (except array) as String. This means that you must use double quotation marks (" ") to enclose the field value. Examples:
- If the data type of a field is Integer and its value is 20, set it as "20".
- If the data type of a field is Boolean and its value is
true, set it as "true".
Request parameters
transferFromDetail Object REQUIRED
Transfer details submitted by the initiator.
Notes:
- If the value of transferFromAmount is greater than 0, the transferToAmount parameter must be set to
0. In this scenario, the fee will be deducted from transferFromAmount. - The eventual amount deducted from the Antom Business Account will be equal to transferFromAmount. The eventual amount received by the beneficiary will be the value of transferFromAmount less the deducted fee.
transferToDetail Object REQUIRED
Transfer details for the initiator.
Notes:
- If the value of transferToAmount is greater than 0, the transferFromAmount must be set to
0. In this scenario, the fee will be added to the transferToAmount. - The eventual amount deducted from the Antom Business Account will be the value of transferToAmount plus the fee. The eventual amount received by the beneficiary will be equal to transferToAmount.
businessSceneCode String REQUIRED
The business scene type of the payout.
Valid values are:
THIRD_PARTY_PAYOUT: Indicates a payout to a third-party bank account, which can be either a third-party company bank account or a third-party personal bank account.-
SAME_NAME_PAYOUT: Indicates a payout to a same-name bank account.
Note: When the value of this parameter is THIRD_PARTY_PAYOUT, contact our sales team.
transferOrderAddition Object
More information about the deduction, including information about the sender and recipient, etc.
Response parameters
result Object REQUIRED
Indicates whether this API is called successfully.
transferFromDetail Object
Transfer details submitted by the initiator.
Note: This field is returned on demand only when the value of result.resultStatus is S.
transferToDetail Object
Transfer details for the beneficiary, including the transfer amount received.
Note: This field is returned on demand only when the value of result.resultStatus is S.
Request
Response
Result/Error codes
| Code | Value | Message | Further action |
|---|---|---|---|
| SUCCESS | S | success. | No further action is needed. |
| UNKNOWN_EXCEPTION | U | API failed due to unknown reason. | The service might be down, retry later. If the issue persists, contact Antom Technical Support. |
| REQUEST_TRAFFIC_EXCEED_LIMIT | U | The request traffic exceeds the limit. | Call the interface again to resolve the issue. If the issue persists, contact Antom Technical Support. |
| 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. |
| PROCESS_FAIL | F | A general business failure occurred. Do not retry. | Human intervention is usually needed. It is recommended that you contact Antom Technical Support to resolve the issue. |
| INVALID_API | F | The called API is invalid or not active. | Check whether the correct API is being called. |
| INVALID_CLIENT | F | The client is invalid. | The Client ID does not exist or is invalid. |
| INVALID_SIGNATURE | F | The signature is invalid. | Make sure the request is properly signed with a valid signature. |
| METHOD_NOT_SUPPORTED | F | The server does not implement the requested HTTP method. | Ensure the HTTP method is |
| CONTRACT_NOT_EXIST | F | Contract does not exist. | Ensure the merchant has already signed a contract and the input is correct. |
| FEE_EXCEPTION | U | API failed due to fee associated issues. | Check the parameters and call the interface again to resolve the issue. If the issue persists, contact Antom Technical Support. |
| UN_SUPPORT_BUSINESS | F | Unsupported business. | Invalid parameters are used. Retry with the correct information. |
| USER_NO_PERMISSION | F | User does not have permission. | Retry with another user information. |
| CURRENCY_NOT_SUPPORT | F | The currency is not supported. | Make sure the currency input is correct and try again. |
| USER_NOT_EXIST | F | The user does not exist. | Retry with the correct user information. |
| USER_ACCOUNT_ABNORMAL | F | The user account status is abnormal. | Retry with a different user. If the issue persists, contact Antom Technical Support for more details. |
| USER_STATUS_ABNORMAL | F | The status of the user is abnormal. Retry with another card. | The status of the user is abnormal. Retry with another transfer order. |
| CONTRACT_CHECK_FAIL | F | The contract check has failed. | Ensure the merchant has already signed a contract and the input is correct. |
| CARD_INFO_NOT_MATCH | F | The card information does not match. | Retry with the correct card information. |