Payments Developer Guide
- Recent Revisions to This Document

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

Standard Payment Processing
- Additional Resources for Processing Payments
- Basic Authorizations
- Authorizations with Line Items
- Authorizations with Payment Network Tokens
- Authorizations with a Card Verification Number
- Authorizations with Strong Customer Authentication Exemption
- Zero Amount Authorizations
- Pre-Authorizations
- Final Authorization Indicator
- Authorization Reversals
- Sales
- Captures
- Multiple Partial Captures
- Refunds
- Credits
- Voids

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
- Discover/Diners ProtectBuy
- Mastercard Identity Check
- Visa Secure

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

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

Token Management Service Processing
- Additional Resources for TMS
- Authorizing a Payment with a Customer Token
- Authorizing a Payment with a Non-Default Shipping Address
- Authorizing a Payment with a Non-Default Payment Instrument
- Authorizing a Payment with a Payment Instrument
- Authorize a Payment with an Instrument Identifier
- Authorize a Payment While Ignoring Network Token
- Authorizing a Payment with a Legacy Token
- Making a Credit with a Customer Token
- Making a Credit with a Non-Default Payment Instrument
- Making a Credit with a Payment Instrument
- Making a Credit with an Instrument Identifier
- Making a Credit with a Legacy Token

Visa Bill Payments Processing
- Visa Bill Payments Authorizations
- Visa Bill Payments Captures

REST API | FDC Compass

Capture Workflow

The capture workflow begins when you send a request for a capture.

The merchant sends a request for a capture to Cybersource.

Cybersource validates the order information then sends an online capture to the payment processor or stores the capture request in a batch file. After midnight, Cybersource sends the batch file to the payment processor.

The processor settles the capture request and transfers funds to the merchant's acquiring bank account.

IMPORTANT

The payment processor does not notify Cybersource that the money has been transferred. To ensure that all captures are processed correctly, you should reconcile your capture requests with the capture reports from your processor.