notifyCapture (Checkout Payment)
This API is used by Antom to send the capture result to the merchant when the capture processing reaches a final state of success or failure.
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
result Result REQUIRED
Details about the payment capture result, such as capture status, result code, and result message.
notifyType String REQUIRED
The type of notification. The notification type of this API is CAPTURE_RESULT.
captureRequestId String REQUIRED
The unique ID that is assigned by the merchant to identify a capture request.
More information:
- Maximum length: 64 characters
paymentId String REQUIRED
The unique ID that is assigned by Antom to identify a payment.
More information:
- Maximum length: 64 characters
captureId String REQUIRED
The unique ID assigned by Antom to identify a capture.
More information:
- Maximum length: 64 characters
captureAmount Amount REQUIRED
The capture amount that the merchant requests to receive in the transaction currency.
captureTime Datetime
The time when Antom captures the payment.
acquirerReferenceNo String
The unique ID assigned by the non-Antom acquirer for the transaction.
More information:
- Maximum length: 64 characters
Response parameters
result Result REQUIRED
A fixed value, which is sent to Antom to acknowledge that the notification is received.
Request
Response
Result process logic
Send the following message with fixed values to Antom after receiving the notification, to acknowledge that the notification from Antom is received:
If no such message is returned to Antom due to operation issues or network issues, Antom will intermittently send the notification until the required message is returned by the merchant. Resending of the notification will be performed within 24 hours after the first notification is sent. The notification will be resent up to eight times, with an interval of 0s, 2min, 10min, 10min, 1h, 2h, 6h, and 15h.
Note: In the sandbox environment, if you do not return information in the specified format, Antom will not resend asynchronous notifications to you.
Result/Error codes
| Code | Value | Message | Further action |
|---|---|---|---|
| SUCCESS | S | Success | The capture is successful, no further action is needed. |
| ACCESS_DENIED | F | The access is denied. | Contact Antom Technical Support for detailed reasons. |
| AUTH_CANCELLED | F | The payment authorization is canceled. | Use a new paymentRequestId to initiate a payment. |
| AUTH_EXPIRED | F | The payment authorization is expired. | Use a new paymentRequestId to initiate a payment. |
| AUTH_NOT_FOUND | F | The payment authorization is not found. | Contact Antom Technical Support for detailed reasons. |
| CAPTURE_AMOUNT_EXCEED_AUTH_LIMIT | F | The total capture amount exceeds the limit of the authorized payment amount. | Create a new capture request by using an amount less than or equal to the authorized payment amount, or contact Antom Technical Support. |
| CAPTURE_IN_PROCESS | U | The capture is processing. | Wait for the notification from Antom or inquiry about the capture result. |
| CURRENCY_NOT_SUPPORT | F | The currency is not supported. | Check the currency used in the request, such as the capture currency. If the issue persists, contact Antom Technical Support for detailed reasons. |
| INVALID_CONTRACT | F | The parameter values in the contract do not match those in the current transaction. | Check whether the parameter values in the contract match those in the current transaction. If the values match, contact Antom Technical Support to troubleshoot the issue. |
| MULTI_CAPTURE_NOT_SUPPORTED | F | The transaction does not support multiple captures. | Contact Antom Technical Support for detailed reasons. |
| NO_PAY_OPTIONS | F | No payment methods are available. | Contact Antom Technical Support for detailed reasons. |
| ORDER_IS_CANCELED | F | The transaction is canceled. | Use a new paymentRequestId to initiate a payment. |
| ORDER_STATUS_INVALID | F | The transaction status is abnormal. The payment cannot be captured. | Check the transaction status. If the values match, contact Antom Technical Support to troubleshoot the issue. |
| PARAM_ILLEGAL | F | The required parameters are not passed, or illegal parameters exist. For example, a non-numeric input, an invalid date, or the length and type of the parameter are wrong. | Check and verify whether the required request fields (including the header fields and body fields) of the current API are correctly passed and valid. |
| PAYMENT_COUNT_EXCEED_LIMIT | F | The number of captures exceeds the limit that is specified by the payment method. | Contact Antom Technical Support to know the specific limit. |
| PROCESS_FAIL | F | The capture failed. | Do not retry. Human intervention is usually needed. It is recommended that you contact Antom Technical Support to troubleshoot the issue. |
| REPEAT_REQ_INCONSISTENT | F | The submitted request exists, and the parameter values of this request are not consistent with those of the existing request. | Ensure all the fields in the requests are the same or use a new paymentRequestId to initiate a payment. |
| RISK_REJECT | F | The request is rejected because of risk control. | Prompt the user that the request is rejected because of failed risk control. |
| USER_AMOUNT_EXCEED_LIMIT | F | The capture amount exceeds the user payment limit. | Create a new capture by using an amount less than or equal to the user payment limit, or contact the user or the issuing bank. |
| USER_BALANCE_NOT_ENOUGH | F | The user's balance is insufficient for the capture. | Contact Antom Technical Support for detailed reasons. |
| USER_NOT_EXIST | F | The user's account does not exist on the payment method side. | Contact the user or the issuing bank. |
| USER_STATUS_ABNORMAL | F | The user's account status is abnormal on the payment method side. | Contact Antom Technical Support to know the specific reasons. |
| UNKNOWN_EXCEPTION | U | The API call has failed, which is caused by unknown reasons. | Call the interface again to resolve the issue. If the problem persists, contact Antom Technical Support. |