Reference
This section provides useful resources for implementing .
Enhanced Capture File Specifications
This section contains the layout of the TC 33.A Capture File. For the most up-to-date specifications, see BASE II Clearing: Interchange Formats, TC 01 to TC 49 in the TC 33.A: Capture Transactions section.
Use the TC 33.A Capture File to:
- Obtain the purchase and refund transaction data the merchants intend to have funded.
- Create Draft Data TC 05 and Credit Voucher TC 06 transactions for Visa-authorized transactions that are then submitted to Visa for clearing and settlement.
- Submit clearing records for non-Visa authorization transactions that are sent to gateway processors.
- Reconcile transaction activity within their own host system.
Capture File Transaction Layout
Each capture file comprises three or more transaction component record (TCR) groups. These TCR groups are a file header (HEDR), a file trailer (TRLR), and a capture data TCR group (CPxx).
The capture data TCR groups, identified by an application code CPxx, contain one or more logical transactions, each of which is defined by a transaction code TC 33.A. Each TCR group contains one or more transaction component records (TCR). Each TCR is 168 bytes long.
The TCR group code identifies a group of related TCRs (TCR 0 through TCR E). All TCR groups (CPxx) for a given transaction are linked by the same message identifier (position 21-35), located only in TCR 0. TCR groups are identified by the application code located in position 17-20, only in TCR 0.
All TCRs in a transaction have the same two-character transaction code (positions 1 and 2). The Transaction Component Sequence Number (position 4) identifies the TCR number. Each TCR group must start with TCR 0. TCR groups and TCR numbers are not necessarily consecutive; that is, the TCR group or TCR sequence might skip a number. For example, a capture that has an EMV sales capture transaction might contain Header HEDR, Trailer TRLR, CP01 TCR 0, TCR 1, TCR 4, and CP02 TCR 1, TCR 2. The TCRs must be in ascending order within the transaction, however. Acquirers only receive the TCR records for which transaction data is available.
The incoming TC 33.A Capture File is transmitted with these Edit Package records: TC 90 (File Header), TC 91 (Batch Trailer), and TC 92 (File Trailer).
The standard file header (TC90), batch trailer (TC91), and file trailer (TC92) are used to identify the beginning of each capture file, the batch boundary at the end of each batch, and an end-of-file indicator, respectively.
The transaction count is not included in any TC91 records if a file is broken into multiple batches. A batch has fewer than 999 records.
The TC 33.A Capture File that Visa sends to EA Server acquirers cannot be larger than 4 GB.
Capture File Best Practices
After Visa transmits the TC 33.A Capture File (TC33-CAP) to you, you should perform file-level validations before processing the file. You must ensure that the file is not a duplicate and that the file is complete and correct.
Follow these steps to ensure that the TC33-CAP file is not a duplicate:
- Validate that the file name, file ID, and sequence numbers have not already been processed. The Direct Exchange (DEX) Open File Delivery (OFD) platform should allow only one version of the file at any time.
- If the file is identified as a duplicate, do not process the file.
Follow these steps to ensure that the TC33-CAP file is complete and correct:
- Examine the file header to confirm complete and accurate file transmission.
- Calculate the file record count and total hash amount of the records in the file.
- Compare the file record count and the total hash amount to the values found in these TC33-CAP file header fields:
- Total Transaction Amount, positions 146-165
- Total Transaction Count, positions 137-145
- If the totals do not match, do not process the file.
After ensuring that the file is not a duplicate and that the file is complete and correct, process the TC33-CAP file. When processing the TC33-CAP file, you must be able to determine whether a clearing record must be created. The Action Code field in the TCR 0, positions 135-146, provides information for this determination:
- A value of
01indicates an authorized purchase transaction (BASE II TC 05 clearing record). - A value of
02indicates an authorized merchandise credit transaction (BASE II, TC 06 clearing record).
The incoming TC33-CAP file includes these BASE II records:
TC 90: File HeaderTC 91: Batch FileTC 92: File Trailer
Reject and Response Codes
This section contains these reject and response codes:
- Reject codes that the Edit Package uses to communicate invalid contents in a BIN field in the TC 33.A Capture File.
- Response codes that a acquirer must use to communicate to Visa that the acquirer either encountered or did not encounter errors when processing the TC 33.A Capture File.
Edit Package Reject Codes
This table lists the Edit Package reject codes:
| Reject Code | Description | File |
|---|---|---|
| V1181 | Source BIN must be 481222 for TC 33 capture transactions. | TC 33 Capture File |
How to Get Help
Acquirers distributing products have access to the Visa Acceptance Solutions Support Center for these resources:
- Knowledge base articles, frequently asked questions, and supplemental documentation for platform and products
- Support request submission system
- Account-specific support resources
Contacting Client Services
For Client Services contact information, refer to the Support Center knowledge article How to Contact Client Services.
Developer information is available at the Visa Acceptance Solutions Developer Center.
Additional acquirer documentation is available from the Documentation Hub.
Thanks for your feedback!
Last published: November 18, 2026