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

Implementation


This section describes the tasks you must complete to implement the service. These tasks comprise these nine steps.

Create an Internal Project Plan

Work with your Visa Regional Implementation Manager to create an internal project plan and obtain and Visa ready dates.

The project plan should include tasks for internal departments, including any coding changes to host systems and their internal procedures.

To complete an internal project plan and task force, contact the appropriate internal business areas.

Request any required Visa documentation from your Visa Regional Implementation Manager and distribute it to the task force.

Because each acquirer's internal system and business needs are unique, you must determine all of the changes that are required to implement the service and include them in your internal project plan.

Share the completed project plan with your Visa Regional Implementation Manager.

Fulfill Internal System Requirements

You must have all of these installed in your host systems before implementation:

  • A BASE II connection using an EA Server or Direct Exchange OFD to support:
    • Receipt of TC 33.A Capture Files and TC 33 POS Authorization Files (optional)
    • Sending Draft Data TC 05 and TC 06 transactions
    • If using Direct Exchange, setup for the OFD file types
  • One or more of these Edit Package applications:
    • Mainframe Edit Package, Release 4.0
    • PC Edit Package for Windows, Version 4.00.0008 (or later)
  • An e-commerce license issued by Visa to implement the program. Contact your Visa representative if you do not have the e-commerce license.

Establish Merchant Relationships

You might have existing relationships with merchants who are using a authorization and capture platform.

Identifying the appropriate merchants and establishing a relationship with them is outside the scope of this guide. You must ensure that participating merchants submit the necessary data for configuring transaction processing through . Examples of the data required include MCC, terminal ID, and merchant IDs assigned by you or your networks.

You must ensure that merchants comply with all Visa operating regulations, PCI DSS, and PA-DSS. For more information, contact your Visa Regional Implementation Manager.

Request and Complete Forms

A Implementation Consultant assists you as needed in completing the required forms. After forms are complete, share them with your Implementation Consultant for processing.

  • Acquirer Enrollment Form (required): complete this form to enroll in the service. Request this form from your Sales Representative/Engineer, complete it, and submit it to your Visa Regional Manager.

  • Acquirer Implementation Questionnaire (VPC AIQ) (required): this form authorizes and initiates a authorization and capture project. The details can be filled out on the Acquirer Onboarding Automation (AOA) tool with the help of a Visa representative, which generates a PDF questionnaire. The signed questionnaire must be submitted on the AOA portal.

    Required information includes:

    • Client contact and officer information
    • Signature of Acquirer Officer form is accurate
    • Acquirer Authorization BIN for the AIQ
    • Destination ID (CIB, NCID, BIN, or another identifier) for the required TC 33.A Capture Files and the optional TC 33 POS Authorization Files
    • Delivery settings for TC 33.A Capture Files
    • Supported card brands on the Visa Gateway
    • Supported processing security features
    • Supported transaction currencies
    • Additional information such as time zones, maximum number of files that can be received in a day (more than one is necessary), maximum file sizes, maximum records in a batch file, and daily processing schedule
    • Additional processing service features (Original Credit Transactions, Dynamic Currency Conversion, and Forced Capture)
    • Supported TCRs for the TC 33.A Capture File
  • BIN License Agreement (optional): used to request a new BIN to process through . It might take two weeks from submission until a new BIN is assigned. Contact your Visa Regional Implementation Manager for additional information.

  • New Authorization Report Request (optional): this form sets up a subscription for and customizes the TC 33 POS Authorization File. These files are optional for and can be used for reconciliation, merchant billing, client support, and more. Submit this form to Visa through your Visa Account Manager or attach it to an email sent to V.I.P. Reporting at [email protected].

  • Test Request and Merchant Data Form (required): this form collects merchant data values for Acquirer VCMS Testing. This data ensures that merchant information used in the capture file during testing is correctly configured. Upload the form on the AOA portal with the help of a Visa representative. The form is divided into two main sections:

    • Section A: for acquirers to select service features for which they want capture test data.
    • Section B: for acquirers to provide override parameters for their test data.

Complete Internal Systems Updates

Complete all host system coding changes and procedural updates for the service according to your internal project plan.

Although internal system changes and procedures contained in internal project plans might vary greatly depending on your organization's needs, you must make these changes to your host systems for the service:

  • Code for the OFD file types if using Direct Exchange.
  • Process the TC 33.A Capture File to properly map and store the purchase and refund transaction data and then use your existing clearing and settlement process to create BASE II Draft Data TC 05 and TC 06 transactions that are submitted to Visa for clearing and settlement. Use data to submit proper clearing files for non-Visa transactions directly to the relevant schemes or network.
  • (Optional) Use authorization details in the TC 33 POS Authorization File to support activities such as merchant billing, reconciliation, and customer support.

Finish Testing

Your Visa Regional Implementation Manager assists you in developing a detailed test plan tailored to your needs. To finish testing, you:

  • Confirm the merchant test account configuration matches the Merchant Data form data.
  • Set up the BIN participation flag.
  • Set up the Edit Package.
  • Set up the TC 33.A Capture File.
  • Set up the TC 33 POS Authorization File.
  • Test the TC33 file.
  • Test the BASE II transaction.
  • Test settlement and reconciliation.

Merchant Test Account Setup

A Visa Regional Implementation Manager helps determine the parameters required to configure a test merchant account on your internal system.

Default values are available as part of the Test Request and Merchant Data form. Alternatively, you can populate the preferred parameters in the Test Request and Merchant Data form to be set up on your host system. There is limited flexibility in the currencies available for testing and in the use of multiple unique Merchant Identification numbers (Card Acceptor ID) and terminal IDs per card brand.

American Express requires that a brand-specific, network-assigned Card Acceptor value be used in processing. This merchant identifier, called the Service Establishment number, is different than the merchant identifier used for the other brands. In many cases, the Discover Network also requires a unique ID assigned by Discover. It is important to use production-like settings in the test merchant account for more comprehensive testing of your own internal processes.

The merchant does their own testing for their integration. Merchant testing is a separate, independent activity. The purpose of merchant testing is to enable the merchant to test the basic success and error conditions for each service they plan to use.

Flag and File Setup

Verify with your implementation manager that these items have been set up according to the options and parameters indicated on the Acquirer Implementation Questionnaire:

  • BIN Participation Flag Setup
  • TC 33.A Capture File Setup
  • TC 33 POS Authorization File Setup

TC33 File Testing

Visa generates test TC 33.A Capture Files and TC 33 POS Authorization Files based on the services and options you request.

Ensure that your Edit Package and internal systems can complete these actions:

  • Receive and process the TC 33.A Capture File.
  • Receive and process the TC 33 POS Authorization File (if elected).

BASE II Transaction Testing

Conduct testing before processing BASE II transactions in production. Regional testing support representatives must ensure that your BIN or CIB is set up in VCMS.

  • Use the data provided in the TC 33.A Capture File to develop and submit Draft Data TC 05 and TC 06 transactions to VCMS BASE II for clearing and settlement.
  • Submit Edit Package outgoing edit run reports (TC 05 and TC 06) to Visa.
  • Request that a Visa Global testing representative verify Edit Package outgoing edit run reports (TC 05 and TC 06) for a successful run. Confirm record, field validation, and content.

Settlement and Reconciliation Testing

You can perform reconciliation to validate your test processes. During testing, complete these settlement reconciliation tasks:

  • Accumulate transaction counts and amounts during transaction processing.
  • Calculate the net amount for the settlement day.
  • Verify counts, amounts, and the net settlement position on the appropriate VSS reports.

Establish a Go-Live Date

Contact your implementation manager to confirm that the production implementation date is valid. There is a 15-day lead time between the request date and the activation date.

Visa executes the agreed-upon implementation date unless the client changes the date. If the production implementation date must be changed, establish a new date with your implementation manager. Visa requires at least 15 business days before the implementation date to change the original date.

When an implementation date is established, the implementation manager arranges to have processing schedules set up according to information submitted in the Acquirer Implementation Questionnaire.

The implementation manager requests Operations to activate a batch group job for the gateway. Business Operations requires at least two weeks before the implementation date to set up processing schedules defined by the batch group.

Information to set schedules is based on information specified in Section I of the Acquirer Implementation Questionnaire. Verify with your implementation manager that Visa will help you monitor and verify that the production environment setup is correct.

Manage Merchant Boarding

Enroll merchants in by either working with to provide the necessary details or by boarding through tools provided in the .

Ensure that all participating merchants follow the Payment Card Industry Data Security Standards (PCI DSS), the Payment Application Data Security Standards (PA-DSS), and Visa Operating Regulations.

Monitor Production Activity

Verify with your implementation manager that starting with your go-live date, Visa performs quiet production to monitor and verify that the production environment setup is correct. Merchants must be boarded in production for monitoring to be effective.

Last published: November 18, 2026

Not available for your audience

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