Recent Revisions to This Document

About This Guide

Introduction to Payments
- 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
- 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 Services
  - Authorizations
    - Micropayment Authorizations
    - Online Authorizations
    - Offline Authorizations
    - Incremental Authorizations
    - Payment Network Token Authorizations
    - Authorization Workflow
  - Authorization Reversals
  - Captures
    - Capture Workflow
  - Credits
    - Credit Workflow
  - Voids
  - Sales
    - Dual Message Processing
      - Partial Authorizations
    - Single Message Processing
- Payment Features
  - Debit and Prepaid Card Payments
  - Payer Authentication
  - Stored Credentials
  - Visa Bill Payments

Standard Payments Processing
- Basic Authorizations
  - Declined Authorizations
  - Required Fields for Processing a Basic Authorization
- Authorizations with Line Items
  - Required Fields for Processing an Authorization with Line Items
- Authorizations with Payment Network Tokens
  - Required Fields for Authorizations with Payment Network Tokens
  - Optional Fields for Authorizations with Payment Network Tokens
- Authorizations with a Card Verification Number
  - Required Fields for Processing an Authorization with a Card Verification Number
  - Optional Fields for Processing an Authorization with a Card Verification Number
- Authorizations with the DCC Gateway Service
- Zero Amount Authorizations
  - Required Fields for Processing a Zero Amount Authorization
- Final Authorization Indicator
  - Requirements for Final Authorizations
  - Pre-authorizations
  - Unmarked Authorizations
    - Requirements for Unmarked Authorizations
  - Undefined Authorizations
    - Requirements for Undefined Authorizations
  - Required Fields for Final Authorizations
- Capture
  - Required Fields for Capturing an Authorization
- Forced Captures
  - Required Fields for Forced Captures
- payments-processing-basic-refund-intro
  - Required Fields for Processing a
- payments-processing-basic-credit-intro
  - Required Fields for Processing a Credit
- Voids
  - Required Fields for Processing a Void

Debit and Prepaid Card Processing
- Additional Documentation
- Processing Debit and Prepaid Authorizations
  - Required Fields for Processing Debit and Prepaid Authorizations
  - payments-debit-prepaid-auth-optional
- Enabling Debit and Prepaid Partial Authorizations
  - Required Fields for Enabling Debit and Prepaid Partial Authorizations
  - Optional Field for Enabling Debit and Prepaid Partial Authorizations
- Disabling Debit and Prepaid Partial Authorizations
  - Required Field for Disabling Debit and Prepaid Partial Authorizations
  - Optional Field for Disabling Debit and Prepaid Partial Authorizations

Payer Authentication Processing
- Additional Documentation
- Providing Payer Authentication Information for Authorization
- Mastercard Identity Check
  - Required Fields for Processing an Authorization Using Mastercard Identity Check
- Visa Secure
  - Required Fields for Processing an Authorization Using Visa Secure

Processing Payments Using Credentials
- Additional Documentation
- Customer-Initiated Transactions with Credentials on File
  - Storing Customer Credentials with a CIT and PAN
    - Required Fields for Storing Customer Credentials During a CIT
  - Using Stored Customer Credentials During a CIT
    - Required Fields for Retrieving Customer Credentials During a Customer-Initiated Transaction
      - Card-Specific Required Field for Retrieving Customer Credentials During a CIT

Visa Bill Payments Processing
- Visa Bill Payments Authorizations
  - Required Fields for Processing a Visa Bill Payment Authorization
- Visa Bill Payments Captures
  - Required Fields for Capturing a Visa Bill Payment

On This Page

Secure Acceptance | TSYS Acquiring Solutions

Authorizations with Payment Network Tokens

This section shows you how to successfully process an authorization with payment network tokens.

Due to mandates from the Royal Bank of India, Indian merchants cannot store personal account numbers (PAN). Use network tokens instead. For more information on network tokens, see the Network Tokenization section of the Token Management Service Guide.

Fields Specific to This Use Case

Include these fields with a standard authorization request:

This field is supported only for Elavon Americas, FDC Compass, RuPay, and Visa Platform Connect.

Endpoint

Back to top