Reply Fields Table 3 Reply Fields Field Name Description Returned By Data Type & Length ap_check_status_payment_status Description of the payment status. Possible values: ■ PENDING: Payment has not been processed. ■ COMPLETED: Payment is complete. ■ ABANDONED: customer cancelled the payment. Check Status String (15) ap_check_status_processor_transaction_id Alipay unique identification for the check status service request. Check Status String (28) ap_check_status_rcode One-digit reply code that indicates whether the ics_ap_check_status request was successful. Possible values: ■ -1: An error occurred ■ 0: The request was declined ■ 1: The request was successful Check Status Integer (1) ap_check_status_rflag One-word description of the result of the ics_ap_check_status request. See Reply Flags. Check Status String (50) ap_check_status_rmsg Message explaining the reply code ap_check_status_rflag. Check Status String (255) ap_check_status_trans_ref_no Reference number that you use to reconcile your CyberSource reports with your Alipay reports. For more information about tracking orders, see Getting Started with CyberSource Advanced for the SCMP API (PDF | HTML). Check Status String (32) ap_initiate_merchant_url Redirect URL to the Alipay web site to confirm the transaction. See Merchant URL Parameters. Initiate Payment ap_initiate_rcode One-digit reply code that indicates whether the ics_ap_initiate request was successful. Possible values: ■ -1: An error occurred ■ 0: The request was declined ■ 1: The request was successful Initiate Payment Integer (1) ap_initiate_rflag One-word description of the result of the ics_ap_initiate request. See Reply Flags. Initiate Payment String (50) ap_initiate_rmsg Message explaining the reply code ap_initiate_rflag. Initiate Payment String (255) ap_initiate_trans_ref_no Reference number that you use to reconcile your CyberSource reports with your Alipay reports. For more information about tracking orders, see Getting Started with CyberSource Advanced for the SCMP API (PDF | HTML). Initiate Payment String (32) ap_refund_amount Total amount for the refund. Refund String (15) ap_refund_date_time Date and time of the refund. Refund String (14) ap_refund_rcode One-digit reply code that indicates whether the refund request was successful. Possible values: ■ -1: An error occurred ■ 0: The request was declined ■ 1: The request was successful Refund Integer (1) ap_refund_return_ref Merchant-generated reference for the refund. CyberSource recommends that you send a unique value for each refund so that you can perform meaningful searches for the transaction. CyberSource will generate a refund return reference number if this field is not populated. Refund String (32) ap_refund_rflag One-word description of the result of the refund request. See Reply Flags. Refund String (50) ap_refund_rmsg Message explaining the reply code. Refund String (255) ap_refund_trans_ref_no Reference number that you use to reconcile your CyberSource reports with your Alipay reports. For more information about tracking orders, see Getting Started with CyberSource Advanced for the SCMP API (PDF | HTML). Refund String (32) ics_rcode One-digit reply code that indicates whether the request was successful. Possible values: ■ -1: An error occurred ■ 0: The request was declined ■ 1: The request was successful Initiate Payment Check Status Refund Integer (1) ics_rflag One-word description of the result of the request. See Reply Flags. Initiate Payment Check Status Refund String (50) ics_rmsg Message explaining the reply code. Initiate Payment Check Status Refund String (255) merchant_ref_number Order reference or tracking number that you provided in the request. For more information about tracking orders, see Getting Started with CyberSource Advanced for the SCMP API (PDF | HTML). Initiate Payment Check Status Refund String (50) request_id Identifier for the request generated by the client. Initiate Payment Check Status Refund String (26) Reply Flags The following table describes the reply flags that are associated with a request. Table 4 Reply Flags Reply Flag Description SOK Transaction was successful. DINVALIDDATA Data provided is not consistent with the request. ESYSTEM System error. You must design your transaction management system to correctly process CyberSource system errors. CyberSource recommends that you not design your system to endlessly retry sending a transaction when a system error occurs. For information about handling system errors and retries, see the documentation for the CyberSource client that you are using. Possible error: payment processor error due to a non-existent transaction (TRADE_NOT_EXIST).