Skip to main content
This guide walks you through the fastest path to a working DCC integration. You will board a merchant using the REST API, then request a rate offer using Flex REST. By the end, you will have a live rate offer proving DCC is active for your merchant.
This guide uses the recommended integration path. If your integration uses different methods, see Choose a boarding method, Choose a rate API, or Choose a file format.

Before you start

This guide assumes you have completed onboarding and received your credentials from Fexco. You need the following values before you begin:
  • OAuth client ID and secret for the Boarding REST API.
  • Acquirer ID, a three-letter code that identifies your organization.
  • Template ID for the merchant configuration.
  • Boarding API base URL for your environment.
  • DHS host URL for Flex REST rate requests.
Your Fexco project manager provides all of these during onboarding. If you do not have them yet, contact your project manager or email DCCSupport@fexco.com. For the full list of prerequisites across all integration methods, see Before you integrate. For details on certification and production environments, see Environments.
1

Board a merchant

Before you can request a rate offer, you need at least one merchant registered in Fexco’s system. The Boarding REST API lets you create a merchant with a single request.First, request an OAuth access token:
Use the returned access_token to submit a boarding request to Create a batch of boarding requests with one merchant:
The baseCurrency field uses an ISO 4217 numeric currency code. For example, 978 is EUR and 840 is USD. See Currency codes for a reference.
Fexco validates and registers the merchant asynchronously. Poll Get boarding status until the batch shows COMPLETED before moving to the next step.
A 202 Accepted response with a boardingId means your merchant is being registered. If the request returns an error, see Troubleshoot merchant boarding.
For the full polling workflow and batch summary review, see Board merchants via REST API.
2

Request a rate offer

With your merchant boarded, you can request a DCC rate offer. The Flex REST API is a simple GET request with no application-level authentication.Replace TST with your acquirer ID and CA001 with the card acceptor ID you used when boarding. The posentrymode value is a three-character ISO 8583 code that describes how the card number was captured. In the example below, 071 means contactless ICC EMV with PIN entry capability.
A response containing foreignAmount and exchangeRate means DCC is working for your merchant. The card is eligible and you have a live conversion offer. If the response body is empty ({}), the card is not eligible. See Handle domestic and unsupported cards. If the request returns an error, see Troubleshoot rate service errors.
For the full field reference, see Request a DCC offer (Flex REST).
If you received a response containing foreignAmount and exchangeRate, you have successfully requested your first DCC rate offer. Your integration is returning real conversion data and DCC is active for your merchant. The receipt below shows what a completed DCC transaction looks like after the cardholder accepts the offer and the transaction is authorized.
POS sale receipt showing GBP 100.00 base amount, exchange rate 1 GBP = 1.3348 USD, 3.50% margin, and USD 133.48 total transaction amount.

A POS receipt for a completed DCC sale transaction. The receipt shows the base amount, exchange rate, margin, and the total in the cardholder's home currency.

Next steps

Explore the full guides to continue building out your integration.