Dynamic Currency Conversion

Dynamic Currency Conversion (DCC) is a service that allows eligible international shoppers to pay for their goods or services in their home currency (the currency of their payment card) rather than the local currency of the merchant.

This feature is mutually beneficial: it provides transparency for the customer and an additional revenue stream for the merchant.

Prerequisites and Setup

DCC is not automatically enabled. To utilize this feature:

  • Onboarding and Contract: DCC must be explicitly enabled during the onboarding process. You must have a valid contract in place with Market Pay or a compatible third party that supports DCC functionality.

  • Card Eligibility: The service works only for payment cards issued outside of the merchant's local currency market.

 

DCC_A35.png

How the DCC Flow Work

When an international card is presented at the POI, the process is handled in real-time before authorization:

  1. Card Recognition: The POI detects an eligible international card.

  2. Rate Lookup: The POI immediately queries the payment network for the current, valid exchange rate and any associated markup/fees.

  3. Customer Choice: The POI presents the customer with the choice to pay in one of two ways:

    • Local Currency (e.g., EUR)

    • Cardholder's Home Currency (e.g., USD, GBP)

  4. Transaction Execution:

    • If the customer chooses the Home Currency (DCC), the transaction is processed for that exact amount.

    • If the customer chooses the Local Currency, the transaction proceeds normally, and the card issuer performs the conversion later.

 

 

Developer Integration Notes

Since DCC occurs at the POI level, the integration requirements are minimal unless you need to override the default behavior.

  • Standard Flow: If DCC is enabled, it is managed entirely by the POI's software. The standard /payment request does not require any extra fields to trigger the DCC offer.

  • Result Data: The final PaymentResponse will contain details about the currency conversion, including the customerApprovedFlag and convertedAmount (currency and amountValue) and the converted amount, which is crucial for generating the receipt and for reconciliation.

  • Receipt Requirement: Due to regulatory requirements, POS has to keep the receipt generated by the POI as it is.

Extract included in Payment Response

"CurrencyConversion": {
  "customerApprovedFlag": true,
  "convertedAmount": {
    "currency": "USD",
    "amountValue": "12"
  },
  "rate": "",
  "markup": "",
}