Last update 20/04/2016

3. DCC Payment request

After you've obtained the possible DCC details and displayed this to the customer, the customer should have the choice whether or not to use it, e.g. pay in his own currency (a conversion happens between his own card currency and the merchant's (your) currency) or pay in your default currency (no currency conversion will be done).

Below we explain the case when the customer has chosen to pay in his own currency, which means he will make use of the proposed currency conversion. This is the most advanced case since you will be required to add additional parameters to the DirectLink request, in order to provide the chosen DCC values.

In both cases though (DCC accepted or not), you're obliged to provide a common additional parameter which is the DCC indicator. This DCC indicator indicates whether or not the customer accepted the DCC proposal.

3.1 Parameters

The parameters that the merchant has to provide are the following:

Field
Description
Format
Mandatory
DCC_COMMPERC
Commission percentage
Numeric
N
DCC_CONVAMOUNT
Converted amount
Numeric Y
DCC_CONVCCY
Converted currency
Alphanumeric, max. 3
Y
DCC_EXCHRATE
Exchange rate
Numeric Y
DCC_EXCHRATETS
Exchange rate date
[yyyy-mm-dd hh:mm:ss]
Y
DCC_INDICATOR
DCC indicator (indicates whether or not the customer accepted the DCC proposal).

Possible values:
  • 0: Customer pays in the merchant’s currency (no conversion done)
  • 1: Customer pays in his own currency (conversion is accepted)
This parameter is always mandatory to indicate DCC was used for this transaction.
0 or 1
Y
DCC_MARGINPERC
Margin percentage
Numeric
Y
DCC_REF
Reference of the DCC
Alphanumeric, max. 80
N
DCC_SOURCE
Exchange rate source
Alphanumeric, max. 32
Y
DCC_VALID
Exchange rate validity (expressed in hours)
Numeric
Y
ORDERID*
Merchant's order reference
Alphanumeric
Y

(* The ORDERID should match the one used during the DCC API call. If the ORDERID is not provided or does not match the one used during an API call, the transaction will be blocked.)

All of these values are provided through the Ingenico ePayments DCC API when doing the DCC request (stage 1).

3.2 Expired DCC offer validity

Every DCC offer has its own validity time, which can be calculated by adding the DCC_VALID parameters (validity period expressed in hours) to the datetime value provided in DCC_EXCHRATETS. If we detect that a DCC offer was provided alongside the transaction which had already expired, there are two possible outcomes, depending on your configuration. Note that this is only relevant in case the customer accepted the DCC offer (DCC_INDICATOR = 1). If he did not accept the DCC offer it is of no importance to Ingenico ePayments to review the validity of the declined offer.

The first case occurs when you've configured to block the transaction when the DCC offer has expired. Ingenico ePayments then simply does so, and the general error number 50001111 is returned.

In the second case we do not block the transaction. Instead we retrieve a new DCC offer ourselves. For this we make use of the currency and amount provided to us in the original transaction, and this offer will automatically be accepted (note that the rates may be different from the expired ones you've sent).

3.3 Possible errors

Error ID
Description
50001111
General error code
50001118
Unknown or inactive PSPID
50001122
Invalid or inactive currency
50001120
Unknown currency code
50001144
Acquirer not found based on input
50001146
DCC configuration not found for PSPID + Brand
50001184
SHA mismatch
30131001
Invalid amount

There are a few possible issues when a merchant uses DCC in DirectLink. All of them speak for themselves but since we use a general error code (50001111) for some of them, some explanation is required.

Possible errors:

  • The validity of the DCC offer expired. This is calculated based on DCC_EXCHRATETS plus DCC_VALID (expressed in hours).
  • An incorrect value is used in one of the fields, e.g. DCC_INDICATOR should be 0 or 1, DCC_EXCHRATETS should be a well formatted date, DCC_CONVAMOUNT should be numeric, etc.
  • The DCC parameters provided by the merchant do not match the ones that were retrieved through the DCC API call
  • The brand of the requested card does not match the one provided in the BRAND parameter
  • The DCC option is not enabled in the merchant’s account
  • The card provided is not eligible for DCC transactions
  • Invalid currency provided through DCC_CONVCCY

This website uses cookies to be able to give you the best user experience. If you don't want to accept these cookies, we allow you to change the cookie settings. Click 'Accept' to allow all cookies from this website.

Cookie settings

Introduction

Functional

Functional cookies are required for the website to operate correctly. These cookies cannot be disabled.

Optimized

Optimization cookies allow us to analyze site usage so we can measure and improve our website.
This is the default level.

Personalized

Personalization cookies are used for social media and advanced personalization. They allow us to show you information related to your company.


Example functionality allowed

  • Store country preference
  • Store language preference

Example functionality not allowed

  • Saving personal data
  • Anonymous tracking via Google Analytics
  • Tracking for remarketing purposes

Example functionality allowed

  • Store country preference
  • Store language preference
  • Anonymous tracking via Google Analytics

Example functionality not allowed

  • Saving personal data
  • Tracking for remarketing purposes

Example functionality allowed

  • Store country preference
  • Store language preference
  • Anonymous tracking via Google Analytics
  • Serve content relevant to your interests
  • Serve ads relevant to your interests
  • Tracking for remarketing purposes

Example functionality not allowed

  • Saving personal data