FILTER BY TAG

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:
Set the value to
true
.
Some processors and card types require a reason code when storing payment credentials.
Set the value to
customer
.
Set to one of these possible values:
  • internet
    : Online transaction.
  • MOTO
    : Mail order/telephone order transaction.
  • A payer authentication value.
{ "processingInformation": { "commerceIndicator": "internet", "authorizationOptions": { "initiator": { "type": "customer", "credentialStoredOnFile": true, "merchantInitiatedTransaction": { "reason": "7" } } } } }
When you receive the initial transaction response, save the transaction identifier, which is located in the
id
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.
This table shows the fields required for each type of CIT and initial transaction.

Subsequent Transactions

For a subsequent transaction, include these fields with a standard authorization request:
processingInformation.authorizationOptions. initiator. merchantInitiatedTransaction. previousTransactionID
  • American Express: Set the value to the transaction ID from the original transaction.
  • Discover: Set the value to the transaction ID from the original transaction.
  • Visa: set the value to the last successful transaction ID.
Some processors and card types require a reason code when you use stored payment credentials.
Set the value to
true
.
Set the value to
merchant
for MIT transactions.
Set to one of these possible values:
  • install
    : Installment payment
  • internet
    : E-commerce order
  • MOTO
    : Mail order or telephone order
  • recurring
    : Recurring payment
  • A payer authentication value.
{ "processingInformation": { "commerceIndicator": "internet", "authorizationOptions": { "initiator": { "type": "merchant", "storedCredentialUsed": true, "merchantInitiatedTransaction": { "reason": "7", "previousTransactionId": "123456789123" } } } } }
This table shows the values for subsequent authorization fields.