API Fields

 

When you send an authorization request that includes card-present data, you must include the basic fields required for every authorization request. For information about card-not-present fields required for these requests, see the Credit Card Services User Guide.

XML Schema Versions

For general information about the XML schema versions, see Getting Started with CyberSource Essentials. The following table specifies the Simple Order API version to use for each processor for clear-text card-present transactions.

 

Table 4

Simple Order API XML Schema Versions for Card-Present Transactions

Processor	Version for Clear Text Transactions
Chase Paymentech Solutions	1.25 or later
FDC Nashville Global	1.24 or later
FDMS Nashville	1.29 or later
GPN	1.26 or later
RBS WorldPay Atlanta	1.48 or later
TSYS Acquiring Solutions	1.13 or later

Formatting Restrictions

Unless otherwise noted, all field names are case sensitive and all fields accept special characters such as @, #, and %.

 

The values of the item_#_ fields must not contain carets (^) or colons (:) because these characters are reserved for use by the CyberSource services. Values for request-level and item-level fields must not contain new lines or carriage returns. However, they can contain embedded spaces and any other printable characters. CyberSource removes all leading and trailing spaces.

Data Type Definitions

 

For more information about these data types, see the World Wide Web Consortium (W3C) XML Schema Part 2: Datatypes Second Edition.

 

Table 5

Data Type Definitions

Data Type	Description
Integer	Whole number {..., -3, -2, -1, 0, 1, 2, 3, ...}
String	Sequence of letters, numbers, spaces, and special characters