API Overview

Payments Developer Guide
- Recent Revisions to This Document

Introduction to Payments
- Financial Institutions and Payment Networks
- Card Types
- Transaction Types
- Payment Services
- Payment Features
- Testing the Payment Services

Standard Payment Processing
- Basic Authorizations
- Authorizations with Line Items
- Authorizations with Payment Network Tokens
- Authorizations with a Card Verification Number
- Zero Amount Authorizations
- Pre-Authorizations
- Final Authorization Indicator
- Authorization Reversal
- Time-Out Authorization Reversals
- Sales
- Sales with Payment Network Tokens
- Captures
- Multiple Partial Captures
- Forced Captures
- Follow-On Credits
- Stand-Alone Credits
- Voids for a Capture or Credit
- Time-Out Voids for a Capture, Sale, Follow-On Credit, or Stand-Alone Credit

Debit and Prepaid Card Processing
- Additional Resources for Debit and Prepaid Payments
- Processing Debit and Prepaid Authorizations
- Enabling Debit and Prepaid Partial Authorizations
- Disabling Debit and Prepaid Partial Authorizations

Payer Authentication Processing
- Additional Resources for Payer Authentication
- Providing Payer Authentication Information for Authorization
- American Express SafeKey
- JCB J/Secure
- Mastercard Identity Check
- Visa Secure

Relaxed Requirements for Address Data and Expiration Date in Payment Transactions
- Requirements
- Services
- Relaxed Fields

Split Shipments Processing
- Authorizing a Sale for a Product Not Yet Available
- Processing Two Authorizations and a Capture for Multiple Products
- Processing an Authorization and Two Captures for Multiple Products

Processing Payments Using Credentials
- Additional Resources for Credentialed Transactions
- Customer-Initiated Transactions with Credentials on File
- Delayed Transaction
- No-Show Transactions
- Reauthorization Transaction
- Resubmission Transaction
- Recurring Payments
- Mastercard Standing Order Payments
- Mastercard Subscription Payments
- Unscheduled COF Payments

Required Fields for Processing a Merchant-Initiated Delayed Transaction

Use these required fields to process a merchant-initiated delayed transaction.

When relaxed requirements for address data and the expiration date are being used, not all fields in this list are required. It is your responsibility to determine whether your account is enabled to use this feature and which fields are required. For details about relaxed requirements, see Relaxed Requirements for Address Data and Expiration Date in Payment Transactions.

billTo_city
billTo_country
billTo_email
billTo_firstName
billTo_lastName
billTo_postalCode
billTo_state
billTo_street1
card_accountNumber
card_expirationMonth
card_expirationYear
ccAuthService_run: Set the value to
true
.
merchantID
merchantReferenceCode
purchaseTotals_currency
purchaseTotals_grandTotalAmount
subsequentAuth: Set the value to
true
.

subsequentAuthReason: Set the value to
2
.; Required only for Discover, Mastercard, and Visa.
subsequentAuthTransactionID: American Express: set to the transaction ID from the original transaction.
Discover: set to the transaction ID from the original transaction.
Visa: set to the last successful transaction ID.

Card-Specific Required Field for Processing a Merchant-Initiated Transactions

Discover

The listed card requires an additional field:

subsequentAuthOriginalAmount: Provide the original transaction amount.