Response File Records

The response file is encrypted with the public part of the PGP Key that you generated and uploaded to CyberSource. To read a response file, you must decrypt it using the private part of the PGP key pair. You can do so with the same third-party software you used to create the keys.

The format for a request file consists of:

nA header record.

nA detail record with one or more data records, each on a separate line.

nA footer record, which indicates the end of the file.

Header Record

The header record consists of comma-separated values and uses the fields listed in the following table:

Table 5 Header Record Fields
Field Name	Description	Required or Optional	Data Type (length)
Record Identifier	Constant value indicating the record type. Format: H	Required	Alpha (1)
File Classification	Indicates whether this is a request or response file, and the type of service. Formats: cybs.au.response.pan	Required	Alphanumeric (30)
MerchantID	Your CyberSource merchant ID. Format: Alphanumeric	Required	Alphanumeric (30)
BatchID	File (batch) identifier sent in the request file. Format: Numeric	Required	Numeric (30)

Detail Record

Each file contains at least one detail record.

Table 6Detail Record Fields
Field Name	Description	Data Type (length)
Record Identifier	Constant value indicating the record type. Format: D	Alpha (1)
Request ID	Unique CyberSource identifier for the record. Format: Numeric	Numeric (30)
Old Card Number	Old card number. Format: Numeric	Numeric (19)
Old Card Expiration Month	Old expiration month. Format: MM	Numeric (2)
Old Card Expiration Year	Old expiration year. Format: YY	Numeric (2)
New Card Number	New card number. Format: Numeric	Numeric (19)
New Card Expiration Month	New expiration month. Format: MM	Numeric (2)
New Card Expiration Year	New expiration year. Format: YY	Numeric (2)
Merchant Reference ID	This field is optional and is returned in the response if present in the request file. Format: Alphanumeric	Alphanumeric (50)
BA Sub Merchant ID	This field is returned in the response if sent in the request file. Format: Alphanumeric	Alphanumeric (10)
Response Code	Response code for the record. See Table 1 , Response Codes and Reason Codes . Format: Alpha	Alpha (3)
Reason Code	Reason code for the record. See Table 1 , Response Codes and Reason Codes . Format: Numeric	Numeric (3)

Footer Record

Each file contains only one footer record.

Table 7Footer Record Fields
Field Name	Description	Data Type (length)
Record Identifier	Constant value indicating the record type. Format: F	Alpha (1)
Record Count	The number of detail records in the file. Format: Numeric	Numeric (10)
Response Code	Response code for the file. See Table 2 , Response Codes and Reason Codes. Format: Alpha	Alpha (3)
Reason Code	Reason code for the file. See Table 2 , Response Codes and Reason Codes. Format: Numeric	Numeric (3)

File Examples

Example 3Non-Billing Aggregator Response File
H,cybs.au.response.pan,merchant1,001 D,1000000000000000001,1111222233334444,11,09,,,,0001,,NUP,800 D,1000000000000000002,2222333344445555,11,09,6666777788889999,11,11,0002,,NAN,800 F,2,COM,800

Example 4Billing Aggregator Response File
H,cybs.au.response.pan,merchant1,001 D,1000000000000000001,1111222233334444,11,09,,,,0001,subId01,NUP,800 D,1000000000000000002,2222333344445555,11,09,6666777788889999,11,11,0002,subId02,NAN,800 F,2,COM,800