Skip to main content
PCI Booking supports several file formats for file transfer tokenization and file transfer token replacement. This page provides format specifications and downloadable examples.

Supported Formats

TADC (Travel Agency Data Capture)

TADC is an XML format used by American Express for travel industry card data reconciliation. PCI Booking can tokenize card numbers within TADC files during SFTP/FTPS transfer, and replace tokens with real card data when sending TADC files outbound.

TADC XML Schema (XSD)

The full XML Schema Definition for validating TADC files is available for download: Download TADC XML Schema (tadc-schema.xsd) The schema defines the complete structure including:
  • Message root element with version, submitter ID, and sequence numbers
  • TravelBatch elements containing provider and currency info
  • TravelTran elements with transaction details, card data, and travel segments
  • Date, amount, and card number format restrictions

TADC Example File

A complete example TADC XML file with realistic (masked) data is available for download: Download TADC Example File (tadc-example.xml) The example includes multiple travel batches with air, hotel, and car rental transactions.

AMEX CSV

The AMEX CSV format is a semicolon-delimited file used for AMEX card data exchange. Each row represents one transaction.

Example

The card number field (second column) is tokenized/detokenized by PCI Booking during file transfer. Download AMEX CSV Example (amex-csv-example.csv)

Delimited Formats (CSV, TSV)

For standard delimited files, PCI Booking identifies card numbers by column position or pattern matching. Configure the column mapping through target profiles or tokenization profiles.

File Transfer Tokenization

Tokenize card data in SFTP/FTPS file transfers

File Transfer Token Replacement

Replace tokens with card data in outbound file transfers