Viewing the Results of Your Batch File Requests
Reports and response files provide information about the requests in your batch files.
The following reports provide information about your batch file requests:
nTransaction Request Report—replaces the Batch File Detail Report. Provides details about the transactions that were batched using the upload process. See Transaction Request Report.
nCapture Detail Report—shows all of the transactions that were submitted to your processor for settlement. You can download the report daily. If the batch file has an error, the file is not processed, and the file’s requests are not included in the report. See the Business Center Reporting User Guide (PDF | HTML).
After Cybersource processes all of the requests in the batch file, Cybersource creates the following types of CSV-formatted response files that you can use to determine the results of the requests in the file:
nFull file—this file includes the results for all the requests in the batch file.
Filename format:
<merchantID>.<batchID>.reply.all
File name example: CyberVacations.12345.reply.all
nException file—this file includes the results for the failed requests.
File name format:
<merchantID>.<batchID>.reply.rejected
File name example: CyberVacations.12345.reply.rejected
The response files are available in the Reports area on the Business Center. For transactions in India, go to https://ebc2.in.cybersource.com/ebc2/. You can download them the same way that you download Cybersource reports, which is explained in the Business Center Reporting User Guide (PDF | HTML).
The format for these files is:
nA File Header followed by a blank line
nOne or more Data Records, each on a separate line
The file header consists of a list of comma-separated name-value pairs, including:
nmerchantID
nbatchID
Example Response File Header
merchantID=infodev,batchID=12345
The data records provide the API reply information for the requests in the batch file. Each data record consists of a comma-separated list of name-value pairs containing the API response information for a single request. The name-value pairs can be in any order.
The order of the data records in the response file might not correspond to the order of the requests in your file. Use the value of the merchantReferenceCode field to link the result in the response file to the corresponding request from the batch file.
Example Response File
This example shows a full file, including two successful requests and one failed request. The failed request is the second data record in the example.
merchantID=infodev,batchID=12345 merchantReferenceCode=ABC12320398,ccCaptureReply_reasonCode=100, merchantReferenceCode=ABC141854,ccCaptureReply_reasonCode=241, merchantReferenceCode=ABC39882097,ccCreditReply_reasonCode=100, |