API Overview

Offline Transaction File Submission Implementation Guide
- Recent Revisions to This Document

Introduction to Offline Transaction File Submission
- Payment Services Supported
- Requirements for Uploading Batch Files
- Batch Files and Batch File Templates
- Validation and Processing Results
- Offline Transaction File Submission Flow

Managing Templates and Batch Files
- Batch File Templates
- Available Batch File Templates
- Download a Batch File Template
- Create a Custom Batch File Template
- Create a Batch File
- Example Batch Files
  - Example Batch File for an Authorization Request
  - Example Batch File for a Sale Request
  - Example Batch File for a Capture Request
  - Example Batch File for a Credit Request
  - Example Batch File for a Void Request

Uploading a Transaction Batch File at the Cybersource Business Center
- Upload a Batch File at the Business Center
- Batch Processing Status

Uploading a Transaction Batch File Using the Simple Order API
- Using Java Sample Code for Basic Authentication
- Sample Code for Basic Authentication

Viewing Email Notifications
- Email Notification for a Failed Batch Validation
- Email Notification for a Successful Batch Validation
- Email Notification for Successful Transaction Processing

Viewing the Results of Batch File Validation
- Download a Batch Validation Response File
- Batch Validation Response File DTD
- Batch Validation Response File XML Elements
  - The Batch Element
  - The ValidationErrors Element
  - The Error Element
- Batch Validation Error Codes
- Example: Successful Batch Validation
- Example: Incorrect Record Count in the Trailer
- Example: Field Count in Some Data Records Does Not Match the Header
- Example: Field Count in More Than 10 Data Records Does Not Match the Header

Viewing the Results of Transaction Processing
- Download a Transaction Response File
- File Header
- Data Records
- Example Transaction Response File

Viewing the Transaction Request Report
- Download a Transaction Request Report
- Transaction Request Report DTD
- Transaction Request Report XML Elements
  - The Report Element
  - The BatchFiles Element
  - The BatchFile Element
  - The PaymentProcessor Element
  - The Request Element
- Example XML-Formatted Transaction Request Report
- Transaction Request Report CSV Records
  - First Header Record
  - Second Header Record
  - Transaction Record
- Example CSV-Formatted Transaction Request Report

Viewing the Batch Submission Detail Report
- Download a Batch Submission Detail Report
- Batch Submission Detail Report DTD
- Example XML-Formatted Batch Submission Detail Report
- Example CSV-Formatted Batch Submission Detail Report

Reference: Simple Order and SCMP API Field Mapping
- Request-Level Fields
- Core Response Fields
- Offer-Level Fields
- Response Fields

Reference: Request Fields for Batch Files
- Fields for an Authorization Request
- Fields for a Sale Request
- Fields for a Capture Request
- Fields for a Credit Request
- Fields for an ACH Service Debit Request
- Fields for an ACH Service Credit Request
- Fields for a Subscription Creation Request
- Fields for a Subscription Update Request
- Fields for a Subscription Cancellation Request

VISA Platform Connect: Specifications and Conditions for Resellers/Partners

On This Page

Viewing the Results of Transaction Processing

After a transaction batch file is validated successfully, Cybersource processes the transactions specified in the batch file and then creates transaction response files
. These CSV-formatted files show the processing results for the batched transaction requests.

One response file lists processing results for all transactions, whether accepted, rejected, or in error. The other response file lists results only for transactions that were rejected or that triggered a processing error.

Full list of transaction responses: This file lists results only for transactions that were rejected or that triggered a processing error.
File name format:
<merchantID>.<batchID>.reply.all
File name example:
CyberVacations.12345.reply.all
List of exceptions: This file lists results only for transactions that were rejected or that triggered a processing error.
File name format:
<merchantID>.<batchID>.reply.rejected
File name example:
CyberVacations.12345.reply.rejected

When all transactions requested in a batch file succeed, an email notification is sent.

Batch with batchID=55555 was validated successfully.

When processing of batched transaction requests succeeds, an email notification is sent. See Email Notification for Successful Transaction Processing.

The topics in this section cover this information:

How to download a transaction response file

The header of a transaction response file

The data records in a transaction response file

An example transaction response file

Back to top