Fields for a Capture Request

This table describes the required and optional fields for specifying a capture request.
Field names are listed in the table as they appear in batch file templates. An asterisk after a field name indicates that the field is required for an authorization request. When you create a batch file based on a template, remove any asterisks from field names.
Fields in a Data Record for a Capture Request
Column
Field Name
Description
A
merchantReferenceCode
*
Merchant-generated order reference or tracking number.
  • Data type: String
  • Data length: 50
  • Required
B
purchaseTotals_currency*
Currency used for the order.
  • Data type: String
  • Data length: 5
  • Required
C
purchaseTotals_grandTotalAmount*
Grand total for the order. You must include either this field or
item_#_unitPrice
in your request. If you use
TSYS Acquiring Solutions
as your payment processor, you can set this field to 0 to check whether the card is lost or stolen.
  • Data type: String
  • Data length: 15
  • Required
D
ccCaptureService_authRequestID*
The requestID returned from a previous request for ccAuthService.
  • Data type: NA
  • Data length: NA
  • Required
E
ccCaptureService_authRequestToken
The requestToken returned from a previous request for ccAuthService.
  • Data type: NA
  • Data length: NA
  • Optional
F
ccCaptureService_authType
If the request contains a verbally authorized transaction, this field must contain the value verbal.
  • Data type: NA
  • Data length: NA
  • Optional
G
ccCaptureService_verbalAuthCode
Verbally received authorization code.
  • Data type: NA
  • Data length: NA
  • Optional
H
billTo_customerID
Your identifier for the customer.
  • Data type: NA
  • Data length: NA
  • Optional
I
merchantDefinedData_field1
Four fields that you can use to store information. NOTE: If you are creating a profile based on an authorization, the merchant-defined data fields do not get transferred to the new profile.
  • Data type: String
  • Data length: 64
  • Optional
J
merchantDefinedData_field2
Four fields that you can use to store information. NOTE: If you are creating a profile based on an authorization, the merchant-defined data fields do not get transferred to the new profile.
  • Data type: String
  • Data length: 64
  • Optional
K
merchantDefinedData_field3
Four fields that you can use to store information. NOTE: If you are creating a profile based on an authorization, the merchant-defined data fields do not get transferred to the new profile.
  • Data type: String
  • Data length: 64
  • Optional
L
merchantDefinedData_field4
Four fields that you can use to store information. NOTE: If you are creating a profile based on an authorization, the merchant-defined data fields do not get transferred to the new profile.
  • Data type: String
  • Data length: 64
  • Optional