1. Online payments scenes
EVO Payment Gateway API
  • Gateway Integration
    • Version Record
    • CardInfoLink Gateway API Integration Guide
      • Online payments scenes
        • DCC
        • Tokenization
        • Payment
        • 3DS Authentication
        • Capture
        • Cancel
        • Refund
        • Merchandise Credit
        • Network token management
        • Cancel or Refund
        • Recapture
        • Recurring
      • Security Requirements and Message Header
        • Message protocol
        • Signature
        • Card Information Encryption
        • PIN Encryption
      • Offline payments scenes
        • Pre-authorization
        • Payment
        • Capture
        • Refund
        • Merchandise Credit
        • Cancel
        • Reversal
        • DCC
        • Recurring
      • Appendix
        • Response code
        • FAQ
        • Mastercard-Merchant Advice Code
        • Product Code
    • Offline API Specification
      • Payment
        • Payment
        • Payment
      • StandaloneCapture
        • StandaloneCapture
        • StandaloneCapture
      • Reversal
        • Reversal
      • MerchandiseCredit
        • MerchandiseCredit
        • MerchandiseCredit
      • Capture
        • Capture
        • Capture
      • TipsAdjustment
        • TipsAdjustment
        • TipsAdjustment
      • Cancel
        • Cancel
        • Cancel
      • MultipleCapture
        • MultipleCapture
        • MultipleCapture
      • FXRateInquiry
        • FXRateInquiry
        • FXRateInquiry
      • Refund
        • Refund
        • Refund
      • DCCToNon-DCC
        • DCCToNon-DCC
        • DCCToNon-DCC
      • ZPK
        • ZPK
      • Notification
        • Asynchronous notification for StandaloneCapture
        • Asynchronous notification for MultipleCapture
        • Asynchronous notification for Payment
        • Asynchronous notification for Capture
        • Asynchronous notification for Refund
        • Asynchronous notification for MerchandiseCredit
        • Asynchronous notification for Cancel
    • Online API Specification
      • PaymentMethod
        • PaymentMethod
        • PaymentMethod
        • PaymentMethod
        • PaymentMethod
      • Payment
        • Payment
        • Payment
        • Payment
      • Refund
        • Refund
        • Refund
      • Cancel
        • Cancel
        • Cancel
      • Capture
        • Capture
        • Capture
      • PaymentInstrument
        • PaymentInstrument
        • PaymentInstrument
        • PaymentInstrument
        • PaymentInstrument
      • MerchandiseCredit
        • MerchandiseCredit
        • MerchandiseCredit
      • CancelOrRefund
        • CancelOrRefund
        • CancelOrRefund
      • TransactionHistoryInquiry Copy
        • TransactionHistoryInquiry
      • MultipleCapture
        • MultipleCapture
        • MultipleCapture
      • Cryptogram
        • Cryptogram
        • Cryptogram
      • StandaloneCapture
        • StandaloneCapture
        • StandaloneCapture
      • Recapture
        • Recapture
        • Recapture
      • AsynchronousNotification
        • Asynchronous notification for Multiple Capture
        • Asynchronous notification for PaymentMethod
        • Asynchronous notification for PaymentInstrument
        • Asynchronous notification for Payment
        • Asynchronous notification for Merchandise Credit
        • Asynchronous notification for Refund
        • Asynchronous notification for Capture
        • Asynchronous notification for Cancel
        • Asynchronous notification for Recapture
        • Asynchronous notification for Cryptogram
        • Asynchronous notification for Network Token update
        • Asynchronous notification for Standalone Capture
        • Asynchronous notification for Network Token authentication finished
      • HealthCheck
        • HealthCheck
      • FX Rate inquiry
        • FXRateInquiry
        • FXRateInquiry
  1. Online payments scenes

DCC

DCC#

Dynamic Currency Conversion (DCC) allows international consumers to choose whether to pay in local currency or their domestic currency. You can use the fx rate inquiry API to obtain the exchange rate between the transaction currency and the settlement currency.
The main process is as follows:
1.
First, you need to initiate the POST FXRateInquiry API to check if the consumer's card supports DCC. Your request must include, but not limited to, the following parameters. For detailed field information, refer to the API documentation:
paymentMethod.type:Indicates the payment method. For card transactions, use card.
paymentMethod.card:Object contains the consumer's card information and terminal details. Required when paymentMethod.type is card.
transAmount: Object contains the transaction amount and currency in local currency.
merchantTransInfo:Object contains the merchant's order number.
DCC FXRateInquiry Example
2.
Check the FXRateInquiry.status field in the EVO Cloud response. If the value is Success, it indicates that the consumer's card supports DCC. Additionally, you will receive, but not limited to, the following fields. For detailed field information, refer to the API documentation:
FXRateInquiry.DCCBillingAmount:Object contains the transaction amount and currency in the card billing currency.
FXRateInquiry.DCCBillingFXRate:Object contains the exchange rate information used to convert the transaction currency to the billing currency, including Markup.
3.
When you initiate the payment using the POST Payment API, you need to include the following additional fields to indicate that this is a DCC Payment:
origMerchantTransInfo.merchantTransID:The order number from the original exchange rate inquiry request, which must match the merchantTransInfo.merchantTransID field you provided in step 1.
DCCBillingAmount:Object contains the transaction amount and currency in the card billing currency. The amount and currency must match the values in the FXRateInquiry.DCCBillingAmount object received in step 2.
transAmount:Object contains the transaction amount and currency in the local currency. It must match the values in the transAmount object provided in step 1.
TIP
Both payment and pre-authorization transactions support DCC
Example
4.
Check the payment.status field in the EVO Cloud response. If the value is Captured, the transaction is successful. Otherwise, check the result.code and result.message to determine the reason for the failure.
5.
If you do not receive a response from EVO Cloud, you need to call GET Payment to query the transaction result. Upon receiving the query response, also check the payment.status field to determine the result, as described in step 4. If the transaction fails, use payment.failureCode and payment.failureReason to find the reason of the failure.
6.
If you included a webhook in your request, you can also get the transaction result through asynchronous notifications. Similarly, use the payment.status field to determine the result, as described in step 4.
7.
Present the payment result to the consumer.
Previous
Version Record
Next
Tokenization
Built with