Choose a boarding method

Fexco supports two methods for boarding merchants into the DCC system. Each method registers merchants in the same underlying Mercury template system, but they differ in format, automation level, and supported operations. This page helps you choose the right method. The Boarding API is the primary boarding method. If you need a file-based approach, use Boarding File Upload (XML).

Boarding API

JSON over HTTPS with real-time status polling

Boarding File Upload

Automated file-based boarding via SFTP

Boarding API

The Boarding API is the primary method for boarding merchants. You submit JSON requests over HTTPS and receive real-time status feedback through polling. It does not require SFTP or file encryption infrastructure.

When to choose	Limitations
You are building a new integration and want automated, API-driven boarding.	Does not support merchant updates. To update a boarded merchant’s configuration, use XML or contact Fexco.
You need real-time status feedback without waiting for file processing.	Does not support reactivation. Contact your Fexco project manager to reactivate a merchant.
You want to deactivate merchants programmatically.

See Board merchants via the Boarding API for the full guide.

Boarding File Upload

XML boarding uses the Boarding File Upload utility, an automated file-based method that supports the full range of operations (create, update, deactivate). You build an XML file, validate it against the Boarding File Upload XSD schema, and upload it via SFTP. Fexco processes the file and returns a confirmation file to your SFTP directory.

When to choose	Limitations
You have an existing XML-based integration and do not want to migrate to the Boarding API.	Requires SFTP connectivity and GPG encryption. You must complete secure connectivity setup before submitting files.
You need to update boarded merchants (template changes, currency changes) without contacting Fexco.	Requires XSD validation. Structural errors cause file-level rejections.
You already have SFTP and GPG infrastructure in place.	Status feedback is asynchronous via confirmation files rather than real-time polling.

See Board merchants via XML for the full guide.

Boarding method comparison

The table below compares both methods across format, authentication, supported operations, and infrastructure requirements.

	Boarding API	Boarding File Upload (XML)
Format	JSON over HTTPS	XML file via SFTP
Authentication	OAuth 2.0 (client credentials)	SFTP credentials
Processing model	Asynchronous batch with polling	Scheduled SFTP pickup
Batch size	Up to 1,000 merchants per request	No fixed limit
Status feedback	Real-time polling via API	Confirmation file via SFTP (~30 min)
Template identifier	Single `templateId`	File Group ID + Base Currency + Rate Margin Description
Create merchants	Yes	Yes
Update merchants	No	Yes
Deactivate merchants	Yes	Yes
XSD validation required	No	Yes
SFTP and GPG required	No	Yes

You can use different methods for different operations. For example, you could use the Boarding API for creating and deactivating merchants, and XML for updates.

Next steps

Once you have chosen a method, follow the guide for your boarding method:

Board merchants via the Boarding API: submit boarding requests over HTTPS with real-time status polling.
Board merchants via XML: build, validate, and upload an XML boarding file via SFTP.

Getting started

Merchant boarding

Rate service

Transaction import

Android app

Go live

Boarding API

Boarding File Upload

Boarding API

Boarding File Upload

Boarding method comparison

Next steps