Testing Support
This section describes the testing support requirements and activities required to process transactions through a authorization and capture platform for .
The goal of the acquirer testing effort is to ensure that you can:
- Receive the new TC 33.A Capture File from Visa.
- Submit Draft Data TC 05 and TC 06 to Visa for clearing and settlement.
To confirm that you can successfully process the TC 33.A Capture File and clearing and settlement files, read the TC 33.A Capture File data and generate corresponding TC 05 clearing records in the VCMS BASE II environment.
Direct Connect Testing comprises two components:
- Acquirer testing component in the Visa Certification Management System (VCMS).
- Merchant testing component using simulators in .
Use these documents as reference materials for the testing process:
- VCMS Testing Guide: BASE II, Client Version
- VCMS Testing Guide: V.I.P., Client Version
- Testing Best Practices (Visa clients)
Acquirer Testing
Before you begin testing, a test capture file must be generated by and then submitted to VCMS.
Acquirers Testing in VCMS
The goal of testing is to ensure that you can receive the new TC 33.A Capture File from Visa, process the capture data within the file, and generate the corresponding clearing data for the settlement file.
Complete these tasks to test in VCMS:
- Test activities on behalf of a test merchant.
- Test acquirer configuration of each environment and prepare the test plan. A predetermined set of transactions is used and filtered based on information in the Acquirer Implementation Questionnaire and the Merchant Test Data Form.
- Define merchant parameters to configure a test merchant account. The data is requested in the Merchant Test Data Form.
Acquirer Testing Overview
You must support TC 33.A Capture File processing and subscribe to the TC 33 POS Authorization File.
Complete these pretest tasks to ensure you can receive and process TC 33.A Capture File records in its incoming BASE II test file:
- Complete and return all required questionnaires and forms.
- Establish a connection to either the EA Server or Direct Exchange OFD.
- Implement the Edit Package or PC Edit Package for Windows Release 4.0, using a version implemented with, or after, the October 2011 business release, to receive the incoming TC 33.A Capture File.
Required Testing Process
You must conduct required testing of the TC 33.A Capture File.
You must test for authorization and capture with . You must demonstrate that your host system is ready to send and receive data required for clearing and settlement for each transaction.
TC 33.A Record Testing
Ensure that your Edit Package and internal systems can receive and process the complete TC 33.A Capture File.
Edit Package
The Edit Package application is software provided by Visa.
You must use the Edit Package to receive TC 33.A Acquirer Capture and Flexible Authorization Reporting files and to send TC33-ACK files.
The Edit Package is also used to validate the BASE II TC 05 and TC 06 transactions created from the TC 33.A Acquirer Capture File before submitting them to Visa for clearing and settlement.
To participate in , use one of these Edit Package applications:
- Mainframe Edit Package, Release 4.0. Include
FILETYPE=ACKFLin the run control options file (ddname//TMPOPT) for special routing. - PC Edit Package for Windows, Version 4.00.0008 (or later). Specify the
ACKFLfile type for special routing: from the main menu, select Settings > Run Control Options > Outgoing, enterACKFLon File Type under File Header Information, and click Save.
BASE II Transactions
Conduct BASE II testing before processing the Capture File and resulting BASE II transactions in production. Regional testing support representatives must ensure that your BIN or CIB is set up in VCMS. The Visa Global Client testing team validates the TC 05 and TC 06 transactions you create against the TC33A file.
To complete this testing, you must:
- Use the data provided in the TC 33.A Capture File, and, if elected, in the TC 33 POS Authorization File, to store, develop, and submit BASE II Draft Data transactions to VCMS BASE II for clearing and settlement.
- Submit Edit Package reports to Visa.
- Request that a regional testing representative verify Edit Package reports for a successful run, confirm record and field validation, and confirm content.
Settlement and Reconciliation Testing
Perform reconciliation to validate test processes. You can review settlement reports to confirm that transaction activity reconciles to the VSS settlement reports and that reported activity matches expected financial data.
Complete these settlement reconciliation tasks during testing:
- 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.
Acquirer Testing Connectivity
You must complete connectivity testing with Visa at least 24 hours before the initial scheduled testing window.
Test Merchant Account (Optional)
Your implementation team works with you to determine the merchant parameters required to configure a test merchant account on your system. Default values are provided as part of the test data.
Merchant testing is an independent activity that is not included in standard acquirer setup and certification. Merchant details provided in the form are used as sample data in the capture file.
Test files are created manually by the product team, who use the internal simulator on the lower test environment. The transactions executed in the Customer Acceptance System (CAS) environment cannot be batched in TC33A for certification purposes.
Merchant Testing
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. Merchants integrate separately using different connectivity options.
Merchant Testing Preparation
Merchant testing is done using simulators in a Customer Acceptance System (CAS) environment and can occur only after acquirer integration is complete and the service is in production or in CAS.
A separate merchant account can be created post-production in the CAS environment for merchant testing of card payment services using API calls, Secure Acceptance web/mobile, Virtual Terminal, and other methods.
TCR Types
Select the TCRs you want to receive in the Acquirer Implementation Questionnaire. For more information about the TC 33.A Capture File, see TC 33.A Capture File.
All TCR fields are required for any selected TCRs. The TCR field list is available upon request.
Conditional TCR records appear only when you select the TCR group to be included in the TC-33 Capture File and when a relevant transaction is present.
Thanks for your feedback!
Last published: November 18, 2026