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

Reference: Simple Order and SCMP API Field Mapping

The Offline Transaction File Submission system ingests batched payment requests composed of fields from the Cybersource Simple Order API. If you normally use the SCMP API to request individual transactions, you need to know which Simple Order API fields correspond to the SCMP API fields with which you are familiar.

To request services in the SCMP API, you would set the

ics_applications

field to a comma-separated list of the services you want to run. For example, to request a credit card sale using the SCMP API:

ics_applications=ics_auth,ics_bill

To request services in the Simple Order API, you instead set each service to

true

. To request a credit card sale using the Simple Order API:

ccAuthService_run=true
ccCaptureService_run=true

The tables in this section contain an alphabetical lists of SCMP API field names and corresponding Simple Order API field names:

Request-level fields

Core response fields

Offer-level fields

Response fields

Back to top