Skip to main content
Welcome to the preview portal — This is an early release of the new Doc Hub experience, with more content coming soon.
Acquirer & Reseller

Payments Implementation


This guide outlines the steps you should follow to successfully deploy as part of your solution.

This guide supplements the Partner Portfolio Overview for the . The Partner Portfolio Overview provides general acquirer implementation and administration information. The boarding guide provides API-based merchant and scale boarding requirements. For details about portfolio ownership and functional usage, see the Partner Portfolio Overview.

Solution Overview

, which includes and Cybersource, offers full-service payment management for merchants. It combines global payment connectivity with processing, fraud management, and payment security services.

How Visa Platform Connect Works

establishes a direct connection between and VisaNet to process authorization transactions into VisaNet and to send batch capture files through Visa to the acquirer so they can maintain their existing settlement processing.

Currently, supports Visa, Mastercard, Diners Club, Discover, American Express, and JCB card products. Brand restrictions apply by acquirer country.

The partnership with and direct connection to Visa helps acquirers provide their customers with highly reliable and secure payment connectivity as well as a wide range of value-added payment services.

Supported Channels, Services, and Segments

supports these channels, services, market segments, card brands, PIN debit networks and gateways, and value-add services.

Supported Channels
  • Contactless (Visa payWave and non-Visa contactless)
  • E-commerce
  • EMV
  • Face to face
  • Installment
  • Mobile POS (MPOS)
  • Mail order or telephone order (MOTO)
  • Recurring
  • Tap to phone
Supported Services
  • Account verification
  • American Express Level II Data
  • Authorizations/purchases
  • Balance Inquiry
  • Balance returns
  • Capture
  • Capture VOID (prior to capture batching)
  • Cash back
  • Japan payment option (JPO, Visa only)
  • Merchandise return/credit
  • Partial authorizations
  • Push payments (Visa and Mastercard)
  • Quasi cash
  • Recurring payments
  • Reversals
  • Visa and American Express Installment Payments
  • Visa and Mastercard Incremental Authorizations (Lodging)
  • Visa and Mastercard Level II Data
  • Visa and Mastercard Level III Data
Supported Market Segments
  • Airline
  • Car rental
  • E-commerce
  • Electronic Benefits Transfer (EBT for US market)
  • Lodging
  • Mass transit
  • Mobile POS
  • MOTO
  • Restaurant
  • Retail
  • Tap to Phone
Supported Card Brands
  • American Express
  • Diners Club
  • Discover
  • JCB
  • mada (Saudi Arabia)
  • Mastercard
  • Meeza (Egypt)
  • PayPak (Pakistan)
  • Union Pay (US only)
  • Visa
Supported PIN Debit Networks and Gateways
  • Accel
  • AFFN
  • CUAlliance
  • EBT (US) PIN Debit Gateway Service
  • Interlink
  • Maestro
  • NYCE
  • Pulse
  • Shazam
  • Star
  • Visa
Supported Value-Add Services

supports multiple services, including:

  • Decision Manager
  • Hosted order pages
  • Tokenization
  • Recurring Billing
  • Acquirer Risk Controls
  • Tax service
  • Dynamic Currency Conversion
  • Invoicing

Contact your account manager for additional information.

Authorization and Capture Service Data Flow

Data Flow Diagram

This figure shows the data processing flow for merchants, , VisaNet, and acquirers.

For authorizations, the merchant sends a request to , which routes both Visa and non-Visa transactions to VisaNet. The authorization response is returned to the merchant.

Data capture follows a different process. The merchant sends a capture request to , which sends it to VisaNet. Visa sends the acquirer a capture file. The acquirer processes the file and follows their standard clearing process to send the file to the appropriate card network.

Merchant reporting and payment activity are provided by with standardized data presentation. Reports and data are available for online viewing or download with full transaction search and query in the .

Processing Data Flow

Processing Flow Overview

This section describes the processing data flows for .

Authorization Processing

  1. The merchant submits an authorization request through an API request directly or through the payment technology provider.
  2. maps the merchant authorization request into an outbound Visa ISO-formatted 0100/0200 authorization request and submits it to VisaNet.
  3. determines the transaction destination and routes it either to the Visa issuer (or STIP) or through the Visa Gateway Service to a non-Visa gateway for authorization.
  4. The issuer (or network) responds to Visa with an 0110/0210 authorization response.
  5. Visa matches the authorization response to the original request and returns the 0110/0210 authorization response to .
  6. The gateway receives the 0110/0210 authorization response and maps the Visa ISO message to the respective API response back to the merchant.

Capture Processing

  1. The merchant submits individual XML capture requests to as follow-on transactions or at the same time as the authorization request.
  2. accumulates transactions until a predetermined batch cutoff is met. This cutoff time is configured at during acquirer boarding.
    • The merchant might have some flexibility to select its batch cutoff time, as long as it fits within the acquirer's preconfigured batch cutoff time options.
    • Acquirers might have multiple merchants that process transactions through the front end. Capture data from all merchants is included.
  3. creates the capture files and sends them to VisaNet for delivery to acquirers.
  4. VisaNet transforms the file into a BASE II TC 33.A Capture File and delivers it to the acquirer according to the acquirer's file delivery profile.
  5. The acquirer processes the TC 33.A Capture Files and submits clearing drafts to the respective payment networks for clearing and settlement processing.
  6. The acquirer funds their merchants.

Merchant Services

This section describes additional solutions available to merchants.

Global Payment Acceptance

  • Account Updater: automatically updates card information to reduce authorization declines and maintain accurate, up-to-date card data.
  • Payer Authentication: integrates authentication services like Verified by Visa to reduce interchange costs and shift liability.
  • Payment Processing Worldwide: enables merchants to accept a wide range of global and regional payment types through a single connection to maximize sales reach and conversion.
  • Payment Security: enhances brand protection and streamlines PCI compliance by eliminating contact with sensitive payment data throughout the transaction process.
  • Token Management Service (TMS): replaces sensitive payment data with tokens to enhance security and reduce risk.
  • Secure ERP and System Centralization Services: moves payment-centric ERP modules out of scope and consolidates payment infrastructure for improved security management.
  • Support for Multiple Sales Channels and Business Models: supports IP-based transactions from various sales channels and complex recurring billing schedules and terms.
  • Taxes Calculated Worldwide: provides real-time, accurate tax calculations for global sales, including US sales tax, GST, and VAT, with precise jurisdiction identification by address.
  • Unified Checkout (Secure Acceptance) Services for Web, Mobile, and Call Center: allows merchants to securely capture payment data directly on the payment network, bypassing their systems.

Fraud Management

  • Analytics and Administration: offers merchants extensive reporting and visibility into the entire payment lifecycle for better reconciliation and chargeback management.
  • Billing Management Services: automates and secures subscription and installment payment processes, minimizing data storage risks.
  • Outsourcing Solutions: enables merchants to fully outsource fraud screening or augment manual review capacity during peak times, with performance guarantees.
  • Platform Integrations and Developer Services: is preintegrated with popular enterprise platforms and accessible through an API for payment processing.
  • Process Management Solutions: provides a fraud detection and case management system with real-time monitoring and comprehensive analytics.
  • Professional Services: provide expert consulting to design, streamline, and integrate enhanced payment architectures for merchants.

Primary Service Features

This section describes the primary features of the service.

TC 33.A Capture File

Visa sends the TC 33.A Capture File to you in an enhanced TC 33.A record format, consolidated with other files through the Extended Access (EA) server or through the Direct Exchange (DEX) Open File Delivery (OFD) platform.

The TC 33.A Capture File contains purchase and refund transactions that have approved authorizations.

Refer to BASE II Clearing: Interchange Formats, TC 01 to TC 49 under the TC 33.A: Capture Transactions chapter for the record layout of the TC 33.A Capture File records.

Use the data in this file to create clearing records for the approved authorization transactions for settlement purposes.

The TC 33.A Capture File supports authorization activity for these brands:

  • Visa
  • Mastercard
  • Diners Club
  • JCB
  • American Express (limited regions per American Express)
  • Discover (limited regions)
  • China Union Pay (US only)
  • mada (Saudi Arabia only)

Clear Visa transactions only through VisaNet. Use the capture file data to clear non-Visa transactions through other processors or networks.

Capture File Contents

The TC 33.A Capture File contains purchase and refund transactions that were previously approved during authorization. These transactions are:

  • Authorizations that have been captured.
  • Installment/recurring payment.
  • Credit/returns.

Optional TCRs and Fields for TC 33.A Capture Files

Specify which Transaction Component Records (TCRs) to add to your subscription in the Acquirer Implementation Questionnaire. Select any or all conditional TCR groups or TCR records used for specific types of transactions. Mandatory TCRs are selected automatically, and optional TCRs are selected based on your needs. A TCR is only included in the file if there is relevant transaction data.

Acquirer Required and Conditional TCR Groups and Records

For every transaction in the TC 33.A Capture File, you always receive CP01 and CP12 Transaction Data.

CP01 Transaction Data
TCRTCR DescriptionY/NComments
CP01 TCR 0Transaction DataYMandatory
CP01 TCR 1Additional DataYMandatory
CP01 TCR 2Billing and ShippingYMandatory
CP01 TCR 3Billing and Shipping (continued)YMandatory
CP01 TCR 4Merchant DataYMandatory
CP01 TCR 5Installment PaymentYMandatory
CP01 TCR 6Gateway DataYMandatory
CP01 TCR 7Gateway Data (continued)YMandatory
CP01 TCR 8Supplemental DataYMandatory
CP01 TCR 9Argentina Domestic ProcessingNMandatory for Argentina processors
CP01 TCR 9Intra-Country Data: Brazil National DataNMandatory for Brazil processors
CP01 TCR 9Intra-Country Data: Chile National DataNMandatory for Chile processors
CP01 TCR 9Intra-Country Data: Colombia National DataNMandatory for Colombia processors
CP01 TCR 9Intra-Country Data: Japan National DataNMandatory for Japan processors
CP01 TCR 9Intra-Country Data: Mexico National DataNMandatory for Mexico processors
CP01 TCR 9Intra-Country Data: South Africa National DataNMandatory for South Africa processors
CP01 TCR 9Intra-Country Data: India National DataNMandatory for India processors
CP01 TCR 9UruguayNMandatory for Uruguay processors
CP01 TCR ACurrency ConversionYMandatory
CP01 TCR BGateway Data (continued)YMandatory
CP02 EMV Data
TCRTCR DescriptionY/NComments
CP02 TCR 0EMV DataNConditional
CP02 TCR 1EMV Data (continued)NConditional
CP02 TCR 2EMV Data (continued)NConditional
CP03 Lodging Data
TCRTCR DescriptionY/NComments
CP03 TCR 0Lodging SummaryNConditional
CP03 TCR 1Lodging Summary (continued)NConditional
CP03 TCR 2Lodging Summary (continued)NConditional
CP03 TCR 3Lodging Summary Additional AmountsNConditional
CP03 TCR 4Lodging Summary Additional Amounts (continued)NConditional
CP04 Level 2 and 3 Data
TCRTCR DescriptionY/NComments
CP04 TCR 0Level II DataNConditional
CP04 TCR 1Level II Data: American ExpressNConditional
CP04 TCR 2Level III Data: Purchasing Transaction SummaryNConditional
CP04 TCR 3Level III Data: Purchasing Transaction SummaryNConditional
CP05 Air Passenger Itinerary Data
TCRTCR DescriptionY/NComments
CP05 TCR 0Passenger Itinerary DataNConditional
CP05 TCR 1Passenger Itinerary Data (continued)NConditional
CP05 TCR 2Passenger Itinerary Data (continued)NConditional
CP05 TCR 3Passenger Itinerary Data (continued)NConditional
CP05 TCR 4Passenger Itinerary Data (continued)NConditional
CP05 TCR 5Passenger Itinerary Data (continued)NConditional
CP05 TCR 6Passenger Itinerary Data: Industry Specific Data: Passenger TransportNConditional
CP05 TCR 7Passenger Itinerary Data (continued)NConditional
CP06 Enhanced Data Detail
TCRTCR DescriptionY/NComments
CP06 TCR 0Enhanced Data: Purchasing Transaction Line-Item DetailNConditional
CP06 TCR 1Enhanced Data: Purchasing Transaction Line-Item Detail (continued)NConditional
CP07 Country Data
TCRTCR DescriptionY/NComments
CP07 TCR 0Country DataNMandatory for Brazil processors
CP07 TCR 1Brazil Country Data: PARCNMandatory for Brazil processors
CP07 TCR 2Brazil Country Data: BNDESNMandatory for Brazil processors
CP07 TCR 3Brazil Country Data: American Express Installment PaymentsNMandatory for Brazil processors
CP07 TCR 4Commercial Mastercard Installment PaymentsNConditional
CP07 TCR 5Consumer Mastercard Installment PaymentsNConditional
CP07 TCR 6Brazil Country Data: Mastercard BNDES1NMandatory for Brazil processors
CP07 TCR 7Debt Repayment InformationNConditional
CP07 TCR 8Japan's Mastercard Additional DataNMandatory for Japan processors
CP07 TCR 9EU Specific ProcessingNMandatory for Europe processors
CP07 TCR APoland: Mastercard Specific, Commercial CardsN—
CP07 TCR BIntra-Country Data: Colombia——
CP08 Discretionary Data
TCRTCR DescriptionY/NComments
CP08 TCR 0Discretionary Data: Default TCRNConditional
CP08 TCR 1Free Form TextNConditional
CP09 Push Payment
TCRTCR DescriptionY/NComments
CP09 TCR 0Push Payment: DefaultNConditional
CP09 TCR 1Push Payment: Original Credit TransactionNConditional
CP09 TCR 2Push Payment: Original Credit Transaction, Additional DetailsNConditional
CP09 TCR 3Sender Name (Split)NConditional
CP09 TCR 4Recipient Name (Split)NConditional
CP09 TCR 5Canada/Colombia OCT and AFT in GeneralNConditional
CP09 TCR 6Account Funding Transaction DetailsNConditional
CP10 Car Rental
TCRTCR DescriptionY/NComments
CP10 TCR 0Car Rental DefaultNConditional
CP10 TCR 1Car Rental (continued)NConditional
CP10 TCR 2Car Rental (continued)NConditional
CP10 TCR 3Car Rental (continued)NConditional
CP10 TCR 4Car Rental (continued)NConditional
CP12 Transaction Data
TCRTCR DescriptionY/NComments
CP12 TCR 0Transaction DataYMandatory
CP12 TCR 1Merchant DataYMandatory
CP12 TCR 2Gateway DataYOptional
CP12 TCR 3Gateway Data (continued)YOptional
CP12 TCR 4Gateway Data (continued)YOptional
CP12 TCR 5Transaction Data (continued)YOptional

Edit Package

The Edit Package application is software provided by Visa that is installed by acquirers and issuers in their internal systems.

For the service, you must use the Edit Package to receive the TC33 Capture File.

The incoming (receive) TC 33.A Capture File is transmitted with these Edit Package records: TC 90 (File Header), TC 91 (Batch File), and TC 92 (File Trailer).

For more information about the Edit Package file header, batch trailer, or file trailer records, refer to the BASE II Clearing Interchange Formats TC 01 to TC 49 manual. Contact your Visa Account Manager for additional questions about record formats.

The Edit Package is also used to validate that the BASE II TC 05 (Sales Draft) and TC 06 (Credit) transactions that are created from the TC33 Capture File are correct before submitting them to Visa for clearing and settlement.

If you are processing through the Authorization and Capture platform, you must use one of these Edit Package applications:

  • Mainframe Edit Package, Release 4.0
  • PC Edit Package for Windows, Version 4.00.0008 (or later)

File Delivery Options

This section describes delivery options for TC33-CAP files.

Customized File Delivery

With customized file delivery, TC33-CAP files are always expedited and sent by Visa to you as soon as they are provided by . The file creation time, including transaction cutoff time and file delivery to Visa, is customizable and configured based on information populated in the Acquirer Implementation Questionnaire.

The customized delivery files are delivered separately from all other files. The customized delivery file can be identified by the value VCAPF in the Customized Delivery File Type field, ITF TC 90, TCR 0, position 109-113.

Contact your Visa Regional Implementation Manager for setting up customized file delivery. This delivery option is recommended for easier differentiation of capture records during processing.

Non-Customized File Delivery

With non-customized file delivery, TC33-CAP files can be received as either non-consolidated and expedited, or consolidated and not expedited:

  • Non-consolidated and expedited: capture records are contained in an undifferentiated file that is delivered to you as soon as it is provided by .
  • Consolidated and unexpedited: capture records are mixed with other transactions in an undifferentiated file and delivered to you after settlement for the day is complete.

Again, the file creation time, including transaction cutoff time and file delivery, is customizable and configured at based on information populated in the Acquirer Implementation Questionnaire.

Undifferentiated files are identified by a value of UNDIF in the BASE II Customized Delivery File Type field, positions 100-113 of the TCR 0: Incoming ITF record in the TC 90: Header Record.

This table shows the delivery options for the TC33-CAP file:

Custom File DeliveryConsolidate FilesExpeditedITF TC90 Header RecordComments
Y—YVCAPFDelivery of the TC33-CAP file is expedited. The Consolidate Files setting is ignored when Custom File Delivery is selected.
NYNUNDIFRecords from the TC33-CAP file are consolidated with other TC 33 records within an acquirer's consolidated undifferentiated (UNDIF) file, which is delivered after settlement has completed.
NNYUNDIFOnly the records from the TC33-CAP file are contained within an acquirer's UNDIF file that is delivered as though it were expedited.

Last published: November 18, 2026

Not available for your audience

This page isn't available for your current audience selection.