Getnet DocsGetnet Docs

Dynamic Currency Conversion (DCC)

View as MarkdownView this page as plain textOpen in ChatGPTAsk questions about this pageOpen in ClaudeAsk questions about this pageOpen in PerplexityAsk questions about this page
Connect to CursorUse these docs in CursorConnect to VS CodeUse these docs in VS Code

Dynamic Currency Conversion (DCC) allows cardholders to choose whether to complete a transaction in the merchant’s local currency or in the currency associated with their card. In Get Central, DCC is handled entirely by the TPVPC and the connected PIN pad, without requiring changes to the standard payment request.

This feature is available only for eligible cards and terminals and is enabled through configuration by the acquirer.

How DCC Works

DCC is evaluated automatically during a card-present payment operation. When a card is identified as eligible for currency conversion, the TPVPC manages the additional processing required to retrieve exchange information and determine whether a currency choice must be presented to the cardholder.

From the application’s perspective, the payment flow does not change:

  • The same payment operation is executed.
  • No additional request parameters are required.
  • The final transaction result is returned in the standard XML response.

Cardholder Currency Choice

When DCC applies, the cardholder may be prompted to select the preferred currency for the transaction. This interaction is handled by the PIN pad according to its configuration and capabilities.

The POS application does not control the presentation of the currency selection and does not explicitly send the cardholder’s choice back to the TPVPC. The decision is resolved internally before the authorization is finalized.

DCC Information in the Response

If a transaction is processed using DCC, the XML response may include additional data elements describing the currency conversion. The presence and structure of these elements depend on the terminal configuration and the transaction outcome.

Applications that store or display transaction details should be prepared to handle optional DCC-related fields in the response.

The exact set of DCC fields and their formatting are defined by the TPVPC and may vary. Applications should not assume that all DCC fields are always present.

Receipt and Compliance Considerations

For DCC transactions, receipts must include currency conversion information required by applicable regulations. Get Central manages the generation of compliant receipt data, ensuring that mandatory information is included when DCC is applied.

Applications that generate or print receipts should rely on the receipt data provided by the TPVPC rather than constructing DCC-specific content manually.

See Also