Dynamic Currency Conversion (DCC)

DCC (Dynamic Currency Conversion) allows the cardholder, during payment in Webcheckout, to see a currency conversion based on the card BIN country of origin. If the BIN belongs to a country different from the merchant country, the user can view the conversion and choose whether to continue in the merchant local currency or in the cardholder currency.

What is DCC?

DCC (Dynamic Currency Conversion) is a feature focused on international purchases that allows users to see how much they could pay in their local currency and decide which currency to use for the payment.

The conversion shown by DCC is informational for the user and does not change the current processing logic. Amounts sent for authorization and settlement keep the merchant operational flow, and DCC information is included as additional data for the Transerver provider.

Key features

• Real-time calculation: shows the equivalent amount in the cardholder currency.
• User decision: the customer can accept or reject DCC.
• No processing changes: authorization and settlement amounts keep the current merchant flow.

When does it apply?

DCC applies when all these conditions are met:

• The integration method is Webcheckout.
• The configured processing provider is Transerver Costa Rica.
• DCC is enabled for the site payment method.
• The card belongs to a country different from the merchant country.
• The operation belongs to a supported flow.

If the BIN belongs to the same country as the merchant, DCC is not offered and the transaction continues with its normal flow.

Where is it supported?

What changes in the payment experience?

When DCC applies, Webcheckout shows an additional block so the payer can choose how to continue:

• The user sees the merchant local currency and the cardholder currency.
• The user sees the exchange rate, margin, and converted amount.
• The user can reject DCC by selecting the original transaction currency or accept DCC by selecting the converted currency.
• If DCC is accepted, the selection is reflected in the transaction and also shown on the result screen and in the payment receipt sent by email to the cardholder.
• If DCC is rejected, the transaction continues with the merchant normal flow, without changing the base Webcheckout experience.

In other words, what changes is the decision and display experience for the user; the merchant integration contract does not change.

DCC in preauthorization flows

In addition to sale payments, DCC has important implications in preauthorization flows:

Check-in

• In Check-in, the user can accept or reject DCC.
• If the user accepts, the transaction continues with DCC.
• If the user rejects, the transaction continues with its normal flow, without DCC.

Reauthorization

• In each Reauthorization, conversion information is queried again, as long as the user accepted DCC in the Check-in transaction.
• If the conversion query fails, reauthorization is processed without DCC.
• This avoids blocking the business flow due to a conversion query failure.

Checkout

• In Checkout, conversion information is also queried again, as long as the user accepted DCC in the Check-in transaction.
• If the query fails, checkout is processed without DCC.
• The goal is to keep operational continuity even when conversion information is not available at that moment.

DCC in other flows

For Void, Reverse, and Full Refund, conversion is not recalculated. In these cases, the DCC information obtained in the initial transaction is sent to maintain flow consistency.

Operations where it applies

Where it does not apply

• Partial payments
• Dispersion
• Recurrence
• Partial refund
• Credit operations
• Installments with interest