Before you integrate

DCC integration involves three components, each with its own credentials and configuration values. Most of these are provided by your Fexco project manager during setup.

Merchant boarding: registering merchants in Fexco’s system so they can accept DCC transactions.
Rate service: requesting currency conversion offers for foreign card transactions.
Transaction import: submitting completed transactions to Fexco for settlement and reporting.

This page lists the prerequisites for each component so you can confirm you have everything in place before you start building.

Prerequisites by component

Select a component below to see what you need before you start building.

Merchant boarding
Rate service
Transaction import

Make sure you have the following items before you start boarding merchants. Your Fexco project manager provides these during onboarding setup.

Prerequisite	Description	Required for
Acquirer ID	A three-letter code that identifies your organization across all DCC components.	All methods
Template ID	Controls which currencies, pricing, and rate configuration apply to your merchants.	Boarding API
File Group ID	Identifies your boarding file group. Used together with Base Currency and Rate Margin Description to select the correct template.	XML
Base Currency	The currency the merchant prices the transaction in.	XML
Rate Margin Description	Identifies the rate margin configuration.	XML
OAuth client ID and secret	Credentials for the Boarding API. Used with the OAuth 2.0 client credentials flow to obtain a bearer token.	REST API
SFTP credentials	Server URL, username, and authentication details.	XML

The combination of File Group ID, Base Currency, and Rate Margin Description must match exactly what Fexco configured for your acquirer. Incorrect values cause merchants to board on the wrong template, which leads to production issues that require rollback.

Make sure you have the following items before you start requesting rate offers. Your Fexco project manager provides the identifiers.

Prerequisite	Description	Required for
Acquirer ID	Used in rate request URLs and headers to identify your organization.	All methods
Card Acceptor ID	Identifies the merchant (MID) in rate requests. Sent as `x-card-acceptor-id` in Rate Service Connect or as a URL parameter in Rate Service Classic.	All methods
RSA certificate	Signed certificate for Certificate and JWT authentication. You generate the RSA key pair and CSR, then Fexco signs and returns the certificate.	Rate Service Connect only

Rate Service Classic does not require application-level authentication. If you are using Rate Service Classic for rate requests, you do not need an RSA certificate or JWT setup.

Make sure you have the following items before you start submitting transaction files. Fexco provides the SFTP credentials and GPG key during connectivity setup.

Prerequisite	Description
SFTP credentials	Server URL, username, and authentication details for uploading transaction files.
GPG public key	Fexco’s public key for encrypting transaction files before upload.
IP and SSH key whitelist confirmation	Fexco whitelists your IP addresses and SSH keys for SFTP access. Provide your IP ranges and SSH public keys during connectivity setup.

Next steps

Environments and URLs: review the certification and production base URLs and SFTP endpoints.
Set up secure connectivity: configure TLS, SFTP, GPG encryption, and IP whitelisting.
Your first DCC transaction: end-to-end quickstart using the recommended integration path.

Getting started

Merchant boarding

Rate service

Transaction import

Android app

Go live

Prerequisites by component

Next steps