Using DCC for an Order

This section guides you through the process of calling the DCC service for a credit card transaction.

For information about the CyberSource SCMP API, see Getting Started with CyberSource Advanced for the SCMP API.

 

Step 1

Request the DCC service.

a	Include the statement ics_applications=ics_dcc in your request.

b	Include the required DCC fields in your request:

●	amount: original amount

●	currency: local currency

●	customer_cc_number: first 6 to 10 digits of the credit card number

●	merchant_id

●	merchant_ref_number

For details about these fields, see Request-Level Fields for the DCC Service and Offer-Level Fields for the DCC Service.

c	Receive the DCC reply fields:

●	dcc_dcc_supported: flag that indicates whether DCC is supported for this order.

●	dcc_exchange_rate: exchange rate

●	dcc_exchange_rate_timestamp: exchange rate timestamp

●	dcc_foreign_amount: converted amount

●	dcc_foreign_currency: converted currency code

●	dcc_margin_rate_percentage: DCC markup

For details about these fields, see Reply Fields for the DCC Service.

Step 2

If necessary, process the order without DCC.

If the purchase is not eligible for DCC, or DCC processing is not available, proceed with the order in your local currency. In your transaction requests (authorization, capture, credit), include the DCC indicator set to 2, which indicates that the order amount could not be converted.

If you are using your local currency for the order, do not perform the rest of this DCC procedure.

Step 3

Query the customer.

If the purchase is eligible for DCC, you must get permission from the customer before you can proceed:

a	Explain to your customer that the order is a candidate for DCC.

b	Display the required DCC information to the customer. Contact your acquirer for these requirements.

c	Ask your customer if they would like to complete the order in their billing currency.

d

After your customer chooses a currency for the order, display a message about the DCC agreement in accordance with the payment card company rules. A typical message is, “I acknowledge that I was offered a choice of currencies in which to perform this transaction, and I understand that this choice is final.”

Before you can use DCC for a purchase, the cardholder must explicitly choose to have the purchases subjected to DCC. Because of this requirement, you cannot use DCC for recurring payments or a recurring subscription.

Step 4

If necessary, proceed in the local currency.

If the customer does not choose DCC, proceed with the order in your local currency:

■	In your transaction requests (authorization, capture, credit), include the DCC indicator set to 3, which indicates that the cardholder declined the currency conversion.

■	Continue with this procedure.

Step 5

Authorize the payment.

For information about creating an authorization request, see Credit Card Services Using the SCMP API.

The following table lists the DCC fields required for the authorization, capture, and credit services. These request field names are not exactly the same as the names of the DCC service reply fields. For details about these fields, see DCC Request-Level Fields for Credit Card Services.

 

Table 3

DCC Fields Required for the CyberSource Authorization, Capture, and Credit Services

Request Field Name for Authorization, Capture, and Credit Services	Reply Field Name for the DCC Service	Value
dcc_indicator	No corresponding field.	DCC indicator: If the customer chose DCC, set the indicator to 1. If the customer did not choose DCC, set the indicator to 3.
exchange_rate	dcc_exchange_rate	Exchange rate.
exchange_rate_timestamp	dcc_exchange_rate_timestamp	Exchange rate timestamp.
foreign_amount	dcc_foreign_amount	Converted amount.
foreign_currency	dcc_foreign_currency	Converted currency code.

Step 6

Display DCC information.

If the customer chose DCC, notify your customer that the transaction was successfully authorized, and display required DCC information to the customer.

Step 7

Capture the authorization.

For information about creating a capture request, see Credit Card Services Using the SCMP API.

If DCC data was included in the authorization request, it must also be included in the capture request:

■	If the capture amount is the same as the authorization amount, submit a capture request that includes the same DCC values that were included in the authorization request.

■	If the capture amount is different from the authorization amount, call the DCC service with the capture amount, and then submit a capture request that includes the new DCC values.

Step 8

Optional: credit the payment.

For information about creating a credit request, see Credit Card Services Using the SCMP API.

If DCC data was included in the capture request, it must also be included in the credit request:

■	For a follow-on credit with a credit amount that is the same as the capture amount, submit a credit request that includes the same DCC values that were included in the capture request.

■	For a follow-on credit with a credit amount that is different from the capture amount, call the DCC service with the credit amount, and then submit a credit request that includes the new DCC values.

■	For a stand-alone credit, call the DCC service with the credit amount, and then submit a credit request that includes the new DCC values.

If the customer did not choose DCC, use the DCC values that you already obtained.

Step 9

View the transaction results.

If the customer chose DCC, the following DCC values are included in the transaction results that are displayed on the Business Center:

■	Original amount

■	Converted amount

■	Exchange rate

The DCC values are also included in the XML version of the Payment Submission Detail Report. For a description of this report, see the Classic Reporting Developer Guide.

You must subscribe to the Payment Submission Detail Report in order to have access to it.