> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fexco.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Transaction type codes

> Transaction type codes for the V-file, I-file, XML I-file, and Transaction Commission (TCOM) file formats.

This page lists the transaction type codes used across DCC transaction
file formats. Use it when building or validating V-files, I-files,
XML I-files, or TCOM files.

## Two-character transaction codes

The V-file and I-file use two-character codes to identify each record.
The first character identifies the terminal environment or record
category. The second identifies the transaction direction or record
purpose.

### Transaction record codes

Each transaction in the file corresponds to a transaction record
identified by a two-character code. The I-file supports the `J1` and
`J2` codes only. The V-file supports all codes in the following table.

| Code | Description | File format |
| :- | :- | :- |
| `J1` | POS DCC sale | V-file, I-file |
| `J2` | POS DCC refund | V-file, I-file |
| `J3` | Cash advance (domestic) | V-file |
| `P1` | ICC DCC POS sale | V-file |
| `P2` | ICC DCC POS refund | V-file |
| `K1` | Airline DCC sale | V-file |
| `K2` | Airline DCC refund | V-file |
| `C1` | Chargeback sale | V-file, I-file |
| `C2` | Chargeback refund | V-file, I-file |

### Summary record codes

One summary record is required after each group of transactions sharing
the same terminal identifier and currency. Use `E4` when total sales
equal or exceed total refunds for the group. Use `E5` when total refunds
exceed total sales. The `E6` code applies only in V-files, where it
summarizes `J3` cash advance transactions in a separate group.

| Code | Description | When to use | File format |
| :- | :- | :- | :- |
| `E4` | Net sales summary | Total sales equal or exceed total refunds for the terminal and currency group. | V-file, I-file |
| `E5` | Net refund summary | Total refunds exceed total sales for the terminal and currency group. | V-file, I-file |
| `E6` | Net cash advance summary | Summarizes all `J3` cash advance transactions for the terminal and currency group. | V-file |

### Claim record codes

One claim record is required per merchant, placed after all summary
records for that merchant. The code depends on whether total sales equal
or exceed total refunds (`E8`) or total refunds exceed total sales (`E7`).

| Code | Description | When to use | File format |
| :- | :- | :- | :- |
| `E7` | Payment by merchant | Total refunds exceed total sales across all groups for the merchant. | V-file, I-file |
| `E8` | Claim by merchant | Total sales equal or exceed total refunds across all groups for the merchant. | V-file, I-file |

## XML I-file transaction codes

The XML I-file uses the `transactionCode` element to identify the
transaction direction. The element accepts one of two enumerated string
values.

| Value | Description |
| :- | :- |
| `debit` | Sale transaction. |
| `credit` | Refund transaction. |

## TCOM transaction type values

The Transaction Commission (TCOM) file uses the `Type` field to
classify each transaction for commission reporting. The field accepts
one of two plain text values.

| Value | Description |
| :- | :- |
| `Sale` | A completed DCC sale transaction. |
| `Refund` | A DCC refund transaction. |

## Next steps

The following references provide full field definitions for each format.

* [V-file reference](https://docs.fexco.com/dcc/developer-resources/file-formats/v-file.md):
  field definitions and segment structure for the V-file.
* [I-file reference](https://docs.fexco.com/dcc/developer-resources/file-formats/i-file.md):
  field definitions and record structure for the I-file.
* [XML I-file reference](https://docs.fexco.com/dcc/developer-resources/file-formats/xml-i-file.md):
  element reference for the XML I-file format.
* [TCOM file reference](https://docs.fexco.com/dcc/developer-resources/file-formats/tcom.md):
  field reference for the TCOM commission report.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.