Reply Fields

Because CyberSource can add reply fields and reason codes at any time:

■

You must parse the reply data according to the names of the fields instead of the field order in the reply. For more information about parsing reply fields, see the documentation for your client.

■

Your error handler should be able to process new reason codes without problems.

■

Your error handler should use the decision field to determine the result if it receives a reason code that it does not recognize.

Your payment processor can include additional API reply fields that are not documented in this guide.

Table 3

Data Type & Length

ccAuthReply_amount

Amount that was authorized.

ccAuthReply_authorizationCode

Authorization code. Returned only when the processor returns this value.

ccAuthReply_authorizedDateTime

Time of authorization.

Format: YYYY-MM-DDThh:mm:ssZ

Example: 2016-08-11T22:47:57Z equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The T separates the date and the time. The Z indicates UTC.

ccAuthReply_avsCode

AVS results. See Credit Card Services Using the Simple Order API for a detailed list of AVS codes.

ccAuthReply_avsCodeRaw

AVS result code sent directly from the processor. Returned only when the processor returns this value.

ccAuthReply_paymentNetworkTransactionID

Network transaction identifier (TID). You can use this value to identify a specific transaction when you are discussing the transaction with your processor.

ccAuthReply_processorResponse

For most processors, this is the error message sent directly from the bank. Returned only when the processor returns this value.

ccAuthReply_reasonCode

Numeric value corresponding to the result of the credit card authorization request. See Credit Card Services Using the Simple Order API for a detailed list of reason codes.

ccAuthReply_reconciliationID

Reference number for the transaction.

ccAuthReversalReply_processorResponse

For most processors, this is the error message sent directly from the bank. Returned only when the processor returns this value.

ccAuthReversalReply

Summarizes the result of the overall request. Possible values:

■

■

■

■

REVIEW: Returned only when you use CyberSource Decision Manager.

For details about these values, see the information about handling replies in Getting Started with CyberSource Advanced for the Simple Order API.

emvReply_combinedTags

The EMV data is in the tag-length-value format and includes chip card tags, terminal tags, and transaction detail tags.

For information about the individual tags, see the “Application Specification” section in the EMV 4.3 Specifications: http://emvco.com

invalidField_0...N

Fields in the request that have invalid data. For information about missing or invalid fields, see Getting Started with CyberSource Advanced for the Simple Order API.

Note These fields are included as an aid to software developers only. Do not use these fields to interact with your customers.

merchantReferenceCode

Order reference or tracking number that you provided in the request. If you included multi-byte characters in this field in the request, the returned value might include corrupted characters.

missingField_0...N

Required fields that were missing from the request. For information about missing or invalid fields, see Getting Started with CyberSource Advanced for the Simple Order API.

Note These fields are included as an aid to software developers only. Do not use these fields to interact with your customers.

purchaseTotals_currency

Currency used for the order. For the possible values, see the ISO Standard Currency Codes.

Numeric value corresponding to the result of the overall request. See Credit Card Services Using the Simple Order API for a detailed list of reason codes.

Identifier for the request generated by the client.