On This Page

Transaction-Specific Fields

To make an authorization request into a credentialed transaction, you must include additional fields that inform Cybersource to either store the customer's payment information for future use, or to use an already stored card-on-file for the payment. This section describes the additional required fields that create an initial and subsequent credentialed transaction.

Initial Transactions

For an initial transaction, include these fields with a standard authorization request:

ccAuthService_commerceIndicator: Set to one of these possible values:
internet
: online transaction.
MOTO
: mail order/telephone order transaction.
A payer authentication value.
See Payer Authentication Values.
subsequentAuthFirst: Set the value to
true
.
subsequentAuthReason: Some processors and card types require a reason code when storing payment credentials.

<ccAuthService run="true">
    <commerceIndicator>internet</commerceIndicator>
</ccAuthService>
<subsequentAuth>false</subsequentAuth>
<subsequentAuthFirst>true</subsequentAuthFirst>
<subsequentAuthReason>7</subsequentAuthReason>

When you receive the initial transaction response, save the transaction identifier, which is located in the

ccAuthReply_paymentNetworkTransactionID

field. You need the transaction identifier for subsequent transactions. If you are using the

Token Management Service

(

TMS

), Cybersource stores the transaction identifier for you.

Subsequent Transactions

For a subsequent transaction, include these fields with a standard authorization request:

ccAuthService_commerceIndicator: Set to one of these possible values:

internet
: online transaction.
MOTO
: mail order/telephone order transaction.
A payer authentication value.
See Payer Authentication Values.
subsequentAuthFirst: Set the value to
true
.
subsequentAuthReason: Some processors and card types require a reason code when storing payment credentials.
subsequentAuthTransactionID: Set the value to the transaction ID from the original transaction.
For merchant-initiated transaction (MIT) card-on-file (COF) processing, store and submit the original transaction identifier (OTID) or network transaction identifier (NTID) associated with each billing agreement rather than relying on values stored in Token Management Service (TMS). Merchant-supplied OTID and NTID values take precedence over TMS-stored values and help ensure that the correct transaction identifier is used, particularly when multiple billing agreements share the same payment token or primary account number (PAN).

<ccAuthService run="true">
    <commerceIndicator></commerceIndicator>
</ccAuthService>
<subsequentAuthFirst>true</subsequentAuthFirst>
<subsequentAuthReason>7</subsequentAuthReason>
<subsequentAuthTransactionID>123456789123</subsequentAuthTransactionID>
<subsequentAuthStoredCredential>true</subsequentAuthStoredCredential>