Allows you to process a card transaction in any of the following situations:
- An initial transaction that uses a saved card token.
- An initial transaction that uses the full (raw) card information (where supported).
- A subsequent transaction that uses a saved card token.
- A subsequent transaction that uses the full (raw) card information (where supported).
- A subsequent transaction that uses a saved terminal token.
For more information about how to implement this endpoint, see the recipes (listed below) or the Creating a card checkout page with your own form, Running a card transaction using full card information, or Running a card transaction with the API topic.
Aside from the fields marked required here, the gateway you are using may require additional fields. For information on gateway-specific required fields, see the Connections documentation.
For the 3DS workflow, the system returns a redirectUrl instead of the standard response, along with an asyncTraceId that you can use with the View transaction async status endpoint for tracking progress and status. For a tutorial, see Using 3DS to run transactions.
Important
Parameters passed with a process request override any data points that are saved with the card token.
For example, if the value for
data.customer.billToAddressOneis saved with the card token as729 Jay Road, but the value for that field is passed with the process request as2147 West Silverlake Drive, the system uses the address atSilverlake Drive.
Try It
To use the Try It feature for this endpoint, you can use the credentials for your Sandbox API user.
You can also use the following test account. Copy the value and paste it into the appropriate space in the Try It section to the right.
username:[email protected]
password:JZdzoXpdDeH6VAProvide the following as body parameters, depending on which payment flow you are using:
- For an initial or subsequent transaction with a saved card token: Include at least the
data.amount,processingOptions.paymentType, andtokenex.token.- For a subsequent transaction with a saved terminal token: Include at least the
data.amount,processingOptions.paymentType, andterminal.token.- With the full card information: Include at least the
data.amount,processingOptions.paymentType,card.pan,card.expirationYear, andcard.expirationMonth.
Note: Sending full card information may increase your PCI scope.- For a subsequent transaction with the full card information: Include at least the
data.amount,processingOptions.paymentType,card.pan,card.expirationYear,card.expirationMonth, andrecurringId.For information about test card numbers and values you can use, see the documentation for the specific gateway/connection integration guide you want to use or, if you are testing Account Updater, see the Test cards for account updater section of the "Checking a card's enrollment tag" topic.