API Overview

Payments Developer Guide
- Recent Revisions to This Document

Introduction to Payments
- Financial Institutions and Payment Networks
- Card Types
- Transaction Types
- Payment Services
  - Authorization
    - Micropayment Authorization
    - Online Authorization
    - Offline Authorization
    - Pre-Authorization
    - Payment Network Token Authorization
    - Authorization Workflow
  - Sale
    - Dual-Message Processing
      - Partial Authorizations
    - Single-Message Processing
  - Authorization Reversal
  - Automatic Partial Authorization Reversal
  - Capture
    - Capture Workflow
  - Credit
    - Credit Workflow
  - Void
- Payment Features
  - Debit and Prepaid Card Payments
  - Airline Data
    - Cybersource Airline Data Processing
    - Airline Data Reference Information
      - Airline Document Type Codes
      - Ancillary Service Category Codes
  - Payer Authentication
  - Relaxed Requirements for Address Data and Expiration Date in Payment Transactions
  - Introduction to Credentialed Transactions
  - Visa Bill Payments
  - Visa Consumer Bill Payments
- Testing the Payment Services
  - Requirements for Testing
  - Test Card Numbers
  - Using Amounts to Simulate Errors
  - Test American Express Card Verification

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

Airline Data Processing
- Airline Travel Legs
- Authorize a Payment
- Capture a Ticket Payment
- Capture an Ancillary Purchase
- Issue a Follow-On Credit

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

Relaxed Requirements for Address Data and Expiration Date in Payment Transactions

Processing Payments Using Credentials
- Additional Resources for Credentialed Transactions
- Customer-Initiated Transactions with Credentials on File
  - Storing Customer Credentials with a CIT and PAN
  - Using Stored Customer Credentials During a CIT
- Reauthorization Transaction
  - Merchant-Initiated Reauthorization Transactions with PAN
- Installment Payments
  - Customer-Initiated Installment Payments with PAN
  - Merchant-Initiated Installment Payments with PAN
- Recurring Payments
  - Customer-Initiated Recurring Payment with PAN
  - Merchant-Initiated Recurring Payments with PAN
- Mastercard Standing Order Payments
  - Mastercard Initial CIT Standing Order Payment
- Mastercard Subscription Payments
  - Mastercard CIT Initial Subscription Payment
- Unscheduled COF Payments
  - Customer-Initiated Unscheduled COF Payment with PAN
  - Merchant-Initiated Unscheduled COF Payment with PAN

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

Visa Consumer Bill Payment Processing

On This Page

Credit Workflow

This workflow applies to follow-on credits, also known as refunds, and stand-alone credits. It begins when you send a request for a credit.

Credits do not happen in real time. All of the credit requests for a day are typically placed in a file and sent to the processor as a single batch
transaction. In most cases, the batch transaction is settled overnight.

The merchant sends the credit request to Cybersource.

For online credits, Cybersource validates the order information then sends the request to the payment processor.

For offline credits, Cybersource stores the request in a batch file and sends the batch file to the payment processor after midnight.

The processor validates the request and forwards it to the acquiring bank.

The acquiring bank transfers funds to the issuing bank.

Not all processors support stand-alone credits.

Back to top