Skip to main content
Download sample XML files to accelerate your integration. Each sample demonstrates the minimum required structure for a valid file. Replace the illustrative identifiers with configuration provided by your Fexco project manager before submitting to production.

Merchant boarding (XML MBU)

Creates a single merchant under one acquirer with a POS terminal. Validates against the Boarding File Upload XSD schema (V26.1).
The acquirer ID, merchant ID, file group ID, originator tag, and rate margin group name in this sample are illustrative. Replace them with the values assigned by Fexco during your onboarding.

Transaction import (XML I-file)

Each sample uses disposition="test", which marks the file as non-production data so it is not processed for settlement.

Sales by currency precision

Different currencies require different decimal formatting in the transactionAmount field. The samples below show how to handle 0, 2, and 3 decimal place currencies.
A standard DCC sale where the cardholder accepts the offer and pays in USD. Most currencies use 2 decimal places.
Japanese yen has zero decimal places. Do not include a decimal point in the transactionAmount field.
The baseAmount is still in the merchant’s base currency (EUR in this example, 2 decimals). Only the transactionAmount follows the cardholder’s currency precision, so JPY has no decimal point.
Kuwaiti dinar uses three decimal places. Include exactly 3 decimal places in the transactionAmount.

Sales by channel

An ecommerce transaction uses merchantType="eCommerce" at the merchant level and eCommerce as the customerInstructions entry method.

Refunds

A refund uses transactionCode value credit instead of debit. The exchange rate and amounts should match the original transaction.
Refunds must use the same exchange rate as the original transaction. The transactionAmount and exchangeRate should match the values from the original sale.

Multi-merchant examples by channel

The samples above show individual transaction types. The following files contain complete multi-merchant, multi-transaction I-files that demonstrate how different channels structure their data. Use them alongside the field mapping pages to understand how scheme data elements populate each field.
A complete I-file with three transactions across two merchants: a DCC-accepted contactless sale, a DCC-declined chip sale (rate 1.0000), and an eCommerce refund. Use this alongside the POS and eCommerce field mapping page.
A complete I-file with three ATM transactions across two merchants. Includes scheme settlement fields (schemeNE2ESettlementAmount, schemeNE2ESettlementRate, schemeNE2ESettlementCurrency) and dispensedAmount, which are specific to ATM transactions. Use this alongside the ATM field mapping page.
The merchant IDs, terminal IDs, and transaction IDs in these samples are test data. Replace them with the values assigned by Fexco during your onboarding before submitting to production.

Transaction import (flat I-file)

These are complete sample file sets for the legacy fixed-length I-file format. Each set includes the submitted I-file and the response files that Fexco returns after processing.
The .DAT files are plain text with fixed-length fields. Open them in a code editor with a column ruler (such as VS Code, UltraEdit, or Notepad++) so you can verify that each field starts at the correct position. The .DAT.TXT files are human-readable processing summaries that open in any text editor.
Every set contains five files:
A file containing only sale transactions (J1 transaction code). Use this to verify your system produces correct sale records.Download each file individually:
A file containing both sale (J1) and refund (J2) transactions in a single submission.Download each file individually:
A file containing only refund transactions (J2 transaction code).Download each file individually:
A file containing sales and refunds across multiple merchants in a single submission.Download each file individually:
A valid I-file with headers and trailer but no transaction records. Use this to verify that your system handles zero-transaction days correctly.Download each file individually:
The merchant IDs, acquirer IDs, and sequence numbers in these samples are test data. Replace them with the values assigned by Fexco during your onboarding before submitting to production.