Recent Revisions to This Document

About This Guide

Introduction to Payments
- Payment Services
- Financial Institutions and Payment Networks
  - Merchant Financial Institutions (Acquirers)
  - Issuing (Customer) Financial Institutions
  - Payment Networks
  - Payment Processors
- Card Types
  - Co-Badged Cards
  - Co-Branded Cards
  - Credit Cards
  - Debit Cards
  - Prepaid Cards
  - Private Label Cards
  - Quasi-Cash
- Transaction Types
  - Card-Not-Present Transactions
  - Card-Present Transactions
  - Authorizations with Card Verification Numbers
    - CVN Locations and Terminology
    - International Transactions
      - Dynamic Currency Conversion
      - Merchant Remittance Funding
  - Token Management Service
- Payment Processing
  - Authorizations
    - Online Authorizations
    - Offline Authorizations
    - Incremental Authorizations
      - Example
    - Payment Network Token Authorizations
    - Authorization Workflow
  - Capture
    - Capture Workflow
  - Sales
    - Dual Message Processing
      - Partial Authorizations
    - Single Message Processing
  - Authorization Reversals
  - Credits
    - Credit Workflow
  - Capture or Credit Voids
  - Interchange Optimization
  - Japanese Payment Options
  - Split Shipments

Basic Processing
- Basic Authorizations
  - Required Fields for Processing Basic Authorizations Using the REST API
    - Country-Specific Required Fields for Processing Basic Authorizations Using the REST API
  - Declined Authorizations
  - REST Interactive Example: Processing an Authorization
  - REST Example: Processing a Basic Authorization
- Authorization with Line Itemization
  - Required Fields
    - Country Specific Required Fields
  - REST Example: Processing a Basic Authorization with Line Items
- Incremental Authorization
  - Required Fields for Processing Incremental Authorizations Using the REST API
    - Country Specific Required Fields for Processing Basic Authorizations Using REST APIs
  - Optional Fields for Processing Incremental Authorizations Using the REST API
  - REST Example: Processing an Incremental Authorization
- Processing an Authorization with a Card Verification Number
  - Required Fields for Processing Basic Authorizations with a Card Verification Number Using the REST API
  - Optional Fields for an Authorization with a Card Verification Number Using the REST API
  - REST Example: Processing an Authorization with a CVN
- Authorizations with the DCC Gateway Service
  - Required Fields for Processing Authorizations Using the REST API
    - Country Specific Required Fields for Processing Basic Authorizations Using REST APIs
  - REST Example: Processing a Authorization
- Zero Amount Authorizations
  - Required Fields for Processing Zero Amount Authorizations Using the REST API
    - Country-Specific Required Fields for Processing Basic Zero Amount Authorizations Using the REST API
  - REST Example: Processing a Zero Amount Authorization
- Authorization with Strong Customer Authentication Exemption
  - Required Fields for an Authorization with an SCA Exemption Using the REST API
  - REST Example: Authorization with an SCA Exemption for Low-Value Transactions
- Authorization Reversals
  - Required Fields for Processing Authorization Reversals Using the REST API
  - REST Example: Processing an Authorization Reversal
- Captures
  - Required Fields for Capturing a Payment Using the REST API
  - REST Interactive Example: Capturing a Payment
  - REST Example: Capturing an Authorization
- Captures with the DCC Gateway Service
  - Required Fields for Processing Captures Using the REST API
  - REST Example: Processing a Capture
- Multiple Captures
  - Required Fields for Multiple Captures Using the REST API
  - REST Example: Processing Multiple Partial Captures
- Sales
  - Required Fields for Processing a Sale Using the REST API
  - REST Example: Requesting a Sale
- Refunds
  - Required Fields for Processing Refunds Using the REST API
  - REST Interactive Example: Processing a Refund
  - REST Example: Processing a Refund
- Credits
  - Required Fields for Processing a Credit Using REST API
  - REST Interactive Example: Processing a Credit
  - REST Example: Processing a Credit
- Voids
  - Required Fields for Processing Voids Using the REST API
  - REST Example: Processing a Void

Card-Present Authorizations
- EMV Chip Contact Payments with an Online PIN Authorization
  - Required Fields for a Contact EMV Authorization with Online PIN Using the REST API
  - Country-Specific Required Fields for an EMV Credit Card Transaction Using the REST API
  - REST Example: EMV Chip and Online PIN Authorization
- EMV Chip (Contact) and Offline PIN Authorization
  - Required Fields for a Contact EMV Authorization with Offline PIN Using the REST API
  - Country-Specific Required Fields for an EMV Credit Card Transaction Using the REST API
  - REST Example: EMV Chip (Contact) with an Offline PIN
- EMV Chip (Contact) and Signature Authorization
  - Required Fields for a Contact EMV Authorization with a Signature Using the REST API
  - Country-Specific Required Fields for an EMV Credit Card Transaction Using the REST API
  - REST Example: EMV Chip (Contact) with a Signature
- EMV Chip (Contactless) and Online PIN Authorization
  - Required Fields for an EMV Contactless Authorization with an Online PIN Using the REST API
  - Country-Specific Required Fields for an EMV Credit Card Transaction Using the REST API
  - REST Example: EMV Chip (Contactless) with an Online PIN
- EMV Chip (Contactless) and Offline PIN Authorization
  - Required Fields for an EMV Contactless Authorization with an Offline PIN Using the REST API
  - Country-Specific Required Fields for an EMV Credit Card Transaction Using the REST API
  - REST Example: EMV Chip (Contactless) with an Offline PIN
- EMV Chip (Contactless with a Signature Authorization
  - Required Fields for an EMV Contactless Authorization with a Signature Using the REST API
  - Country-Specific Required Fields for an EMV Credit Card Transaction Using the REST API
  - REST Example: EMV Chip (Contactless) with a Signature
- Card-Present Authorizations with Magnetic Stripes
  - Required Fields for Authorizations with Swiped Track Data
  - Optional Fields for Authorizations with Swiped Track Data
  - REST Example: Authorization with Swiped Track Data
- Card Present Authorizations with Hand Keyed Data
  - Required Fields for Authorizations with Keyed Data
  - Example: Sale Using Keyed Data
- Card-Present Authorizations for Cash Advances with Credit Cards
  - Required Fields for a Cash Advance Authorization
  - Optional Fields for a Cash Advance Authorization
  - REST Example: Authorizing a Cash Advance
  - Response Codes for a Cash Advance Authorization
- Captures for Contact EMV Authorizations
  - Required Fields for Processing Basic Captures Using REST APIs
  - REST Example: Processing a Capture Using the REST API

Japanese Payment Options
- Authorizing a Single Payment with Japanese Payment Options
  - Required Fields for Authorizing a Single Payment with the JPO Method Using the REST API
  - REST Example: Authorizing a JPO Single Payment
- Authorizing a Bonus Payment with Japanese Payment Options
  - Required Fields for Authorizing a JPO Bonus Payment Using the REST API
  - REST Example: Authorizing a JPO Bonus Payment
- Authorizing an Installment Payment with Japanese Payment Options
  - Required Fields for Authorizing a JPO Installment Payment Using the REST API
  - REST Example: Authorizing a JPO Installment Payment
- Authorizing a Revolving Payment with Japanese Payment Options
  - Required Fields for Authorizing a Revolving Payment with the JPO Method Using the REST API
  - REST Example: Authorizing a JPO Revolving Payment
- Authorizing a Combination Payment with Japanese Payment Options
  - Required Fields for Authorizing a Combination Payment with the JPO Method Using the REST API
  - REST Example: Authorizing a JPO Combination Payment

Split Shipments
- 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

Payer Authentication Processing
- Providing Payer Authentication Information for Authorization
- American Express SafeKey
  - Required Fields for an Authorization with American Express SafeKey
  - Optional Field for an Authorization with American Express SafeKey
  - REST Example: Authorization with American Express SafeKey
- JCB J/Secure
  - Required Fields for an Authorization using JCB J/Secure Authentication
  - REST Example: Authorization with JCB J/Secure
- Mastercard Identity Check
  - Required Fields for an Authorization with Mastercard Identity Check
  - REST Example: Authorizing Mastercard Identity Check
- Visa Secure
  - Required Fields for an Authorization with Visa Secure
  - REST Example: Authorization with Visa Secure

Stored Credential Processing
- Customer-Initiated Transactions with Credentials on File
  - Storing Customer Credentials with a Customer-Initiated Transaction
    - Required Fields
    - REST Example: Storing Customer Credentials During a Customer-Initiated Transaction
  - Using Stored Customer Credentials During a Customer-Initiated Transaction
    - Required Fields
    - Card-Specific Required Field
    - REST Example: Retrieving Customer Credentials During a Customer-Initiated Transaction
- Merchant-Initiated Transactions
  - Industry Practice Transactions
    - Merchant-Initiated Delayed Transaction
      - Required Fields for Merchant-Initiated Delayed Transaction
      - Card-Specific Required Field
      - REST Example: Merchant-Initiated Delayed Authorization Transaction
    - Merchant-Initiated Incremental Transaction
      - Required Fields for Incremental Transactions
      - Card-Specific Required Field
      - REST Example: Merchant-Initiated Incremental Transaction
    - Merchant-Initiated Reauthorization Transactions
      - Required Fields for Merchant-Initiated Reauthorization Transactions
      - Card-Specific Required Field
      - REST Example: Merchant-Initiated Reauthorization Transactions
    - Merchant-Initiated Resubmission Transaction
      - Required Fields for Authorizing a Merchant-Initiated Resubmission
      - Card-Specific Required Field
      - REST Example: Merchant-Initiated Resubmitted Authorization Transactions
    - Merchant-Initiated No-Show Transactions
      - Required Fields for Merchant Initiated No-Show Charges
      - Card-Specific Required Field
      - Optional Field for Authorizing Merchant Initiated No-Show Charges
      - REST Example: Merchant-Initiated No-Show Transaction
  - Standing Instruction Transactions
    - Installment Payments
      - Installments for Installment Payments
      - Initial CIT Installment Payment with a PAN
        Required Fields for Authorizing Initial Installment Payments Using REST API
        REST Example: Initial Customer-Initiated Transaction Installment Payment
      - Subsequent MIT Installment Payments
        Required Fields for Authorizing Subsequent Installment Payments Using REST API
        Card-Specific Required Field
        India-Specific Required Fields for Installment Payments
        REST Example: Subsequent Installment Payment Authorization
    - Recurring Payments
      - Recurring Billing for Recurring Payments
      - Initial CIT Recurring Payment with a PAN
        Required Fields for Authorizing Initial Recurring Payments Using REST API
        REST Example: Initial CIT Recurring Payment
      - Initial CIT Recurring Payment with an Instrument Identifier
        Required Fields for Authorizing Initial Recurring Payments with an Instrument Identifier
        REST Example: Initial CIT Recurring Payment with an Instrument Identifier
      - Initial CIT Recurring Payment with a Customer ID
        Required Fields for Authorizing Initial Recurring Payments with a Customer ID
        REST Example: Initial CIT Recurring Payment with a Customer ID
      - Subsequent MIT Recurring Payments
        Required Fields for Authorizing Subsequent Recurring Payments Using REST API
        Card-Specific Required Fields
        Country-Specific Required Fields
        REST Example: Subsequent MIT Recurring Payments
      - Subsequent MIT Recurring Payments with an Instrument Identifier
        Required Fields for Authorizing Subsequent Recurring Payments with Instrument Identifier
        Card-Specific Required Fields
        REST Example: Subsequent MIT Recurring Payments with an Instrument Identifier
      - Subsequent MIT Recurring Payments with a Customer ID
        Required Fields for Authorizing Subsequent Recurring Payments with a Customer ID
        Card-Specific Required Fields
        REST Example: Subsequent MIT Recurring Payments with a Customer ID
    - Mastercard Standing Order Payments
      - Mastercard Initial CIT Standing Order Payment
        Required Fields for Authorizing Standing Order Payments Using REST API
        REST Example: Initial CIT Standing Order Payments
    - Mastercard Subscription Payments
      - Mastercard Initial CIT Subscription Payment
        Required Fields for Authorizing Subscription Payments Using REST API
        REST Example: Initial CIT Subscription Payments
    - Unscheduled COF Payments
      - Initial CIT Unscheduled COF Payment
        Required Fields for Authorizing Initial Unscheduled COF Payments Using REST API
        REST Example: Initial CIT Unscheduled COF Payment
    - Subsequent MIT Unscheduled COF Payments
      - Required Fields for Authorizing Subsequent Unscheduled COF Payments Using REST API
      - Card-Specific Required Field
      - Country-Specific Required Fields
      - credentials-mit-unsched-optfields
      - REST Example: Subsequent Unscheduled COF Payment Authorization Using REST API

Processing Token Management Service Payments
- Authorize a Payment with a Customer Token
  - Required Fields for Authorizing a Payment with a Customer Token Using the REST API
  - REST Example: Authorizing a Payment with a Customer Token
  - REST Example: Authorizing a Payment Using a Customer Token Linked to a Network Token
- Authorize a Payment with a Non-Default Shipping Address
  - Required Fields for Authorizing a Payment with a Non-Default Shipping Address Using the REST API
  - REST Example: Authorizing a Payment with a Non-Default Shipping Address
- Authorize a Payment with Non-Default Payment Instrument
  - Required Fields for Authorizing a Payment with Non-Default Payment Instrument Using the REST API
  - Optional Fields for Authorizing a Payment with Non-Default Payment Instrument Using the REST API
  - REST Example: Authorizing a Payment with Non-Default Payment Instrument
- Authorize a Payment with a Payment Instrument
  - Required Fields for Authorizing a Payment with a Payment Instrument Using the REST API
  - Optional Fields for Authorizing a Payment with a Payment Instrument Using the REST API
  - REST Example: Authorizing a Payment with a Payment Instrument
- Authorize a Payment with an Instrument Identifier
  - Required Fields for Authorizing a Payment with an Instrument Identifier Using the REST API
  - REST Example: Authorizing a Payment with an Instrument Identifier
  - REST Interactive Example: Authorizing a Payment with an Instrument Identifier
- Authorize a Payment with Legacy Token
  - Required Fields for Authorizing a Payment with Legacy Token Using the REST API
  - REST Example: Authorizing a Payment with Legacy Token
  - REST Interactive Example: Authorizing a Payment with a Legacy Token
- Make a Credit with a Customer Token
  - Required Fields for Making a Credit with a Customer Token Using the REST API
  - REST Example: Making a Credit with a Customer Token
- Make a Credit with Non-Default Payment Instrument
  - Required Fields for Making a Credit with Non-Default Payment Instrument Using the REST API
  - Optional Fields for Making a Credit with Non-Default Payment Instrument Using the REST API
  - REST Example: Making a Credit with Non-Default Payment Instrument
- Make a Credit with a Payment Instrument
  - Required Fields for Making a Credit with a Payment Instrument Using the REST API
  - REST Example: Making a Credit with a Payment Instrument
- Make a Credit with an Instrument Identifier
  - Required Fields for Making a Credit with an Instrument Identifier Using the REST API
  - REST Example: Making a Credit with an Instrument Identifier
  - REST Interactive Example: Making a Credit with an Instrument Identifier
- Make a Credit with Legacy Token
  - Required Fields for Making a Credit with Legacy Token Using the REST API
  - REST Example: Making a Credit with Legacy Token

Level II Processing
- Captures with Level II Data
  - Required Fields for Capturing a Payment with Level II Data Using the REST API
  - Optional Fields for Processing a Sale with Level II Data Using the REST API
  - REST Example: Capturing a Payment with Level II Data
- Credits with Level II Data
  - Required Fields for Processing a Credit with Level II Data Using the REST API
  - Optional Fields for Processing a Credit with Level II Data Using the REST API
  - REST Example: Processing a Credit with Level II Data
- Sales with Level II Data
  - Required Fields for Processing a Sale with Level II Data Using the REST API
  - Optional Fields for Processing a Sale with Level II Data Using the REST API
  - REST Example: Processing a Sale with Level II Data

Level III Processing
- Captures with Level III Data
  - Required Fields for Capturing a Payment with Level III Data Using the REST API
  - Optional Fields for Capturing a Payment with Level III Data Using the REST API
  - REST Example: Capturing a Payment with Level III Data
- Credits with Level III Data
  - Required Fields for Processing a Credit with Level III Data Using the REST API
  - Optional Fields for Processing a Credit with Level III Data Using the REST API
  - REST Example: Processing a Credit with Level III Data
- Sales with Level III Data
  - Required Fields for Processing a Sale with Level III Data Using the REST API
  - Optional Fields for Processing a Sale with Level III Data Using the REST API
  - REST Example: Processing a Sale with Level III Data

Debit and Prepaid Card Processing
- Processing Debit and Prepaid Authorizations
  - Required Fields for Debit and Prepaid Authorizations Using REST APIs
    - Country Specific Required Fields for Processing Basic Authorizations Using REST APIs
  - Optional Field for Debit and Prepaid Authorizations Using REST APIs
  - REST Example: Debit and Prepaid Authorizations
- Enabling Debit and Prepaid Partial Authorizations
  - Required Field for Enabling Debit and Prepaid Partial Authorizations Using REST APIs
  - Optional Field for Enabling Debit and Prepaid Partial Authorizations Using REST APIs
  - Enabling Partial Authorizations
  - Example: Enabling Debit and Prepaid Partial Authorizations Using the REST API
- Disabling Debit and Prepaid Partial Authorizations
  - Required Field for Disabling Debit and Prepaid Partial Authorizations Using REST APIs
  - Optional Field for Disabling Debit and Prepaid Partial Authorizations Using REST APIs
  - Disabling Partial Authorizations
  - Example: Disabling Debit and Prepaid Partial Authorizations Using the REST API

Airline Processing Introduction
- Cybersource Airline Data Processing
- Airline Travel Legs
- Visa Platform Connect Airline Data
  - Visa Platform Connect Airline Authorizations
    - Required Fields for Authorizing an Airline Payment
    - REST API Example: Authorizing an Airline Payment
  - Visa Platform Connect Airline Captures for Ticket Purchases
    - Required Fields for Capturing an Airline Payment
    - Card-Specific Field for Capturing an Airline Purchases
    - Optional Fields for Capturing an Airline Payment
    - REST API Example: Capturing an Airline Payment
  - Visa Platform Connect Airline Captures for Ancillary Purchases
    - Required Fields for Capturing an Authorization for Ancillary Purchases
    - Ancillary Fields for Capturing a Purchase
    - REST API Example: Capturing an Ancillary Purchase
  - Visa Platform Connect Airline Refunds
    - Required Fields for Airline Refunds
    - Optional Fields for Airline Refunds
    - REST API Example: Processing Airline Refunds
  - Visa Platform Connect Airline Credits
    - Required Fields for Airline Credits
    - Optional Fields for Airline Credits
    - REST API Example: Crediting an Airline Payment
- Reference Information
  - Airline Document Type Codes
  - Ancillary Service Category Codes

On This Page

Introduction to Payments

This introduction provides the basic information that you will need to successfully process payment transactions. It also provides an overview of the payments industry and provides workflows for each process.