Skip to main content
Rate Service Connect uses a single endpoint, Create DCC Rate Offer, for all DCC rate requests regardless of channel (POS, ATM, or e-commerce) or transaction type (purchase, refund, pre-authorization, and others). The transaction details are sent as a JSON body, and the merchant and acquirer are identified through request headers. Unlike Rate Service Classic, Rate Service Connect authenticates every request with a JSON Web Token (JWT) signed using your private key. It also returns ready-to-use offerText and receiptText fields, so you do not need to build the cardholder prompt or receipt line yourself.

Before you start

You need the following to request a DCC offer using Rate Service Connect:

Send a DCC offer request

The steps below cover building the request, reading the response, and presenting the offer to the cardholder. For the full list of parameters, response fields, and transaction types, see Create DCC Rate Offer in the API reference.
1

Build and send the request

Send a POST request to the Create DCC Rate Offer endpoint with the required headers and a JSON body containing the card Bank Identification Number (BIN), transaction amount, and transaction type. Replace the placeholder values with your own.The example below uses the PURCHASE transaction type. Rate Service Connect also supports REFUND, CASH_ADVANCE, REVERSAL, PREAUTHORIZATION, INCREMENTAL_AUTHORIZATION, and COMPLETE_AUTHORIZATION. See the API reference for details on each type.The posEntryMode value is a three-character code defined by ISO 8583 that indicates how the card number was captured and the PIN entry capability of the terminal. In the example below, 079 means ICC with no PIN entry capability specified.
For ATM integrations, the amount value must include both the withdrawal amount and any access fee charged to the cardholder.
The offerText field contains the DCC choice to present to the cardholder, and receiptText contains the DCC-compliant line for the printed receipt. Both are ready to use without additional formatting.The currency field uses an ISO 4217 alphabetic currency code (for example, EUR, USD, GBP).For the complete list of response fields, see Create DCC Rate Offer in the API reference.
A 201 response with foreignAmount, offerText, and receiptText means the card is eligible for DCC. Proceed to step 2. If the response is a 400 with an error code, the card is not eligible. Process the transaction in the merchant’s base currency instead. See Handle domestic and unsupported cards and Troubleshoot rate service errors.
2

Present the offer to the cardholder

Use the offerText field to display the DCC choice to the cardholder. The cardholder must accept or decline before the expiry timestamp in the exchangeRate object. If the offer expires before the cardholder responds, discard it and request a new one. See Handle rate expiry.If the cardholder accepts, use the receiptText field for the DCC-compliant receipt line.

Next steps