Merchant boarding (XML MBU)
Create a merchant with a POS terminal
Create a merchant with a POS terminal
Creates a single merchant under one acquirer with a POS terminal. Validates against the Boarding File Upload XSD schema (V26.1).
Transaction import (XML I-file)
Each sample usesdisposition="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 thetransactionAmount field. The samples below show how to handle 0, 2, and 3 decimal place currencies.
Sale with a 2-decimal currency (USD)
Sale with a 2-decimal currency (USD)
A standard DCC sale where the cardholder accepts the offer and pays in USD. Most currencies use 2 decimal places.
Sale with a 0-decimal currency (JPY)
Sale with a 0-decimal currency (JPY)
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.Sale with a 3-decimal currency (KWD)
Sale with a 3-decimal currency (KWD)
Kuwaiti dinar uses three decimal places. Include exactly 3 decimal places in the
transactionAmount.Sales by channel
Ecommerce sale (eDCC)
Ecommerce sale (eDCC)
An ecommerce transaction uses
merchantType="eCommerce" at the merchant level and eCommerce as the customerInstructions entry method.Refunds
Refund (credit)
Refund (credit)
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.POS and eCommerce (dual message)
POS and eCommerce (dual message)
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.ATM (single message)
ATM (single message)
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.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.Sales only
Sales only
A file containing only sale transactions (
J1 transaction code). Use this to verify your system produces correct sale records.Download each file individually:- ITST20261012000001.DAT (I-file)
- ATST20261012000001.DAT (A-file)
- BTST20261012000001.DAT (B-file)
- CTST20261012000001.DAT (C-file)
- CTST20261012000001.DAT.TXT (Processing summary)
Sale and refund mix
Sale and refund mix
A file containing both sale (
J1) and refund (J2) transactions in a single submission.Download each file individually:- ITST20261012000002.DAT (I-file)
- ATST20261012000002.DAT (A-file)
- BTST20261012000002.DAT (B-file)
- CTST20261012000002.DAT (C-file)
- CTST20261012000002.DAT.TXT (Processing summary)
Refunds only
Refunds only
A file containing only refund transactions (
J2 transaction code).Download each file individually:- ITST20261012000003.DAT (I-file)
- ATST20261012000003.DAT (A-file)
- BTST20261012000003.DAT (B-file)
- CTST20261012000003.DAT (C-file)
- CTST20261012000003.DAT.TXT (Processing summary)
Sale and refund mix (multiple merchants)
Sale and refund mix (multiple merchants)
A file containing sales and refunds across multiple merchants in a single submission.Download each file individually:
- ITST20261012000004.DAT (I-file)
- ATST20261012000004.DAT (A-file)
- BTST20261012000004.DAT (B-file)
- CTST20261012000004.DAT (C-file)
- CTST20261012000004.DAT.TXT (Processing summary)
Empty file (no transactions)
Empty file (no transactions)
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:
- ITST20261012000005.DAT (I-file)
- ATST20261012000005.DAT (A-file)
- BTST20261012000005.DAT (B-file)
- CTST20261012000005.DAT (C-file)
- CTST20261012000005.DAT.TXT (Processing summary)
Related pages
- Board merchants via XML: step-by-step guide for building and submitting an MBU file.
- Validate an XML file before submission: check your MBU file against the XSD before uploading.
- Build and submit an XML I-file: step-by-step guide for building a transaction import file.
