Configure the Salesforce B2C LINK Cartridge

Set up the Salesforce B2C LINK Cartridge and Business Manager.

Custom site preferences

After successfully importing the metadata, select BM Merchant Tools, select Site Preferences, and then select Custom Preferences to see Custom Site Preferences Groups.

Click Digital River to see the cartridge setup fields.


Field Title



Enable Digital River

Turns on/off Digital River integration


*API Key

Digital River publishable API key


*Digital River public key

Your public API key



Manufacturer ID number


Digital River ship from country

The ship-from country for physical products


Digital River ship from state

The ship-from state for physical products


Digital River ship from city

The ship-from city for physical products


Digital River ship from address line 1

The ship-from address line 1 for physical products


Digital River ship from address line 2

The ship-from address line 2 for physical products


Digital River ship from pos

*Digital River provides the values for these fields.

tal Code

The ship-from postal code for physical products


SKUs update requested

The switch for the possibility of performing the job OptionalDigitalRiverSKUsUpdate. If you configure the job to run according to a schedule, then the Yes value will allow the job to perform its actions. See the user guide for information.

*Digital River provides the values for these fields.

Business Manager roles and permissions

To enable the Digital River Business Manager extensions, add the Write permission to the targeted access role. This is optional to enable the Digital River Service Checker and Request SKUs to update modules.

In Business Manager, select Administration, and then select Roles and Permissions. To add the Digital River modules to a role, click the role you want to modify (or create a new one). Then click one or more checkboxes to select the Business Manager modules for that role.

In the next menu, add the Write permission to the Digital River group as indicated below.

See Business Manager for more information about Digital River modules.

Lastly, the order status webhook must be able to access the order to update the status of the order properly. To enable this webhook, you must change the site settings.

  1. Select Merchant Tools, select Site Preferences, and click Order.

  2. Set Limit Storefront Order Access to No.

  3. Set Storefront Order Filter by Customer Session to No.

Custom code

IMPORTANT: Follow the instructions below only when you can’t use the cartridge directly, or you need to resolve conflicts with other cartridges on your project. Otherwise, you must compile the client-side scripts and styles, upload the cartridge, and add it to your storefront cartridge path. Cartridge int_digitalriver_sfra already contains all templates and script changes described in Custom code.


Make the following changes to the template files:

  • Template: cartridge\templates\default\account\payment\addPayment.isml Add this Digital River script to Drop-in functionality on the page.

And apply the changes to Drop-in styles.

<script src="">

And apply the changes to Drop-in styles.


Put the following condition inside the card-body div.

<iscomment> Include Digital River Drop-In </iscomment>
<isset name="useDigitalRiverDropIn" value="${require('dw/system/Site').getCurrent().getCustomPreferenceValue('drUseDropInFeature')}" scope="page" />
<isif condition="${useDigitalRiverDropIn}">
<isinclude template="account/payment/dropinForm"/>
<iscomment> Default Payment form </iscomment>
<isinclude template="account/payment/paymentForm"/>
  • Template: cartridge\templates\default\cart\cartTotals.isml. Include the Digital River Duty section in the cart totals template after the discount section.

<!-- Digital River Duty -->
<isif condition="${require('dw/system/Site').getCurrent().getCustomPreferenceValue('drUseDropInFeature')
&& pdict.totals.duty.value !== 0}">
<div class="row">
<div class="col-8">
<p>${Resource.msg('label.order.sales.duty','digitalriver', null)}</p>
<div class="col-4">
<p class="text-right duty-total">${pdict.totals.duty.formatted}</p>
  • Template: cartridge\templates\default\checkout\billing\paymentOptions\paymentOptionsSummary.isml. Extend the condition with the ‘DIGITAL_RIVER_DROPIN’ payment method.

<iselseif condition="${payment.paymentMethod === 'DIGITAL_RIVER_DROPIN'}" />
<isinclude template="checkout/billing/paymentOptions/dropInSummary" />
  • Template: cartridge\templates\default\checkout\billing\billing.isml. Include the Digital River payment options template.

<isif condition="${pdict.digitalRiverUseDropInFeature}">
<isinclude template="digitalriver/checkout/billing/paymentOptions" />
<isinclude template="checkout/billing/paymentOptions" />
  • Template: cartridge\templates\default\checkout\billing\storedPaymentInstruments.isml. Extend the card-image class condition as follows:

<img class="card-image ${!pdict.digitalRiverUseDropInFeature && loopState.first ? 'checkout-hidden' : ''}"

Also, wrap the security-code-input div with the following condition:

<isif condition="${!pdict.digitalRiverUseDropInFeature}"> <iscomment> Digital River - if enabled no cvv needed thus pictures are always shown instead of input </iscomment>
… security-code-input goes here
  • Template: cartridge\templates\default\checkout\shipping\shippingAddress.isml. Extend the shipping address form with the email address input field.

<isif condition="${pdict.digitalRiverUseDropInFeature}">
<div class="row">
<div class="col-sm-12">
<div class="form-group
<isif condition=${ === true}>required</isif>
<label class="form-control-label" for="email">${Resource.msg('','checkout',null)}</label>
<button type="button" class="info-icon">
<span class="icon" aria-hidden="true">i</span>
<span class="sr-only">${Resource.msg('','common',null)}</span>
<span class="tooltip d-none">
<input type="text" class="form-control email" id="email"
value="${pdict.order.orderEmail||''}" <isprint value=${} encoding="off"/>
aria-describedby="emailInvalidMessage" >
<div class="invalid-feedback" id="emailInvalidMessage"></div>
  • Template: cartridge\templates\default\checkout\checkout.isml. Include the Digital River styles.


Add a condition that will control the submit payment button display.

<isset name="submitPaymentShow" value="${!pdict.digitalRiverUseDropInFeature || (pdict.customer.registeredUser && pdict.customer.customerPaymentInstruments.length) ? '' : 'digitalriver-hide'}" scope="page" />
  • Template: cartridge\templates\default\checkout\orderTotalSummary.isml. Add the Digital River Duty section.

<!--- Digital River Duty --->
<isif condition="${require('dw/system/Site').getCurrent().getCustomPreferenceValue('drUseDropInFeature')}">
<div class="row leading-lines duty-item ${pdict.order.totals.duty.value === 0 ? 'hide-order-discount': ''}">
<div class="col-6 start-lines">
<p class="order-receipt-label"><span>${Resource.msg('label.order.sales.duty','digitalriver', null)}</span></p>
<div class="col-6 end-lines">
<p class="text-right"><span class="duty-total">${pdict.order.totals.duty.formatted}</span></p>

Client scripts

Make the following changes to the client script files:

Note: Do not forget to compile client-side scripts after implementing changes in the source code.

  • Script cartridge\client\default\js\checkout.js Include the drDropIn script on the checkout page.

  • Script cartridge\client\default\js\checkout\checkout.js Add the following code to the shipping submit success handler.

if (!data.error) {
$('body').trigger('digitalRiver:dropIn', data.digitalRiverConfiguration); // Digital River integration: call dropIn feature after checkoutCreate

Extend the code on line 222 as follows:

var paymentMethod = $('.payment-information').data('payment-method-id');
if (paymentMethod === 'CREDIT_CARD' || paymentMethod === 'DIGITAL_RIVER_DROPIN') { // Extended by Digital River Drop-in integration
  • Script cartridge\client\default\js\checkout\billing.js Extend the condition inside the function.

if (!$('#dropInContainer').data('enabled')
&& billing.payment && billing.payment.selectedPaymentInstruments
&& billing.payment.selectedPaymentInstruments.length > 0) {

Add the <getCreditCardPaymentInfoHtml> function.

* Creates html to display payment summary for credit card payment
* @param {Object} order current order model
* @param {Object} selectedPaymentInstrument selected payment instrument model
* @returns {string} html for credit card payment
function getCreditCardPaymentInfoHtml(order, selectedPaymentInstrument) {
return '<span>' + order.resources.cardType + ' '
+ selectedPaymentInstrument.type
+ '</span><div>'
+ selectedPaymentInstrument.maskedCreditCardNumber
+ '</div><div><span>'
+ order.resources.cardEnding + ' '
+ selectedPaymentInstrument.expirationMonth
+ '/' + selectedPaymentInstrument.expirationYear
+ '</span></div>';

And use it for creating HTML inside the <updatePaymentInformation> function.

var selectedPaymentInstrument = order.billing.payment.selectedPaymentInstruments[0];
if (selectedPaymentInstrument.paymentMethod === 'DIGITAL_RIVER_DROPIN') {
switch (selectedPaymentInstrument.paymentType) {
case 'creditCard':
htmlToAppend += getCreditCardPaymentInfoHtml(order, selectedPaymentInstrument);
default: // extend switch with new cases or extend default if you want to show extended data for non-card payment types
htmlToAppend += '<span>' + selectedPaymentInstrument.paymentType
+ '</span>';
} else {
htmlToAppend += getCreditCardPaymentInfoHtml(order, selectedPaymentInstrument);

Wrap the <clearCreditCardForm> function content with the following condition.

if (!$('#dropInContainer').data('enabled')) {
… function content goes here

Wrap the <handleCreditCardNumber> content with the following condition.

if ($('.cardNumber').length > 0) { // if Digital River enabled card form will be replaced with Drop-in functionality
cleave.handleCreditCardNumber('.cardNumber', '#cardType');

Add the condition inside the <selectSavedPaymentInstrument>.

if (!$('#dropInContainer').data('enabled')) { // Digital River - if enabled no cvv needed thus pictures are always shown instead of input
$('.saved-payment-instrument .card-image').removeClass('checkout-hidden');
$('.saved-payment-instrument .security-code-input').addClass('checkout-hidden');
+ ' .card-image').addClass('checkout-hidden');
$('.saved-payment-instrument.selected-payment '
+ '.security-code-input').removeClass('checkout-hidden');

Add the following code in the <addNewPaymentInstrument> function.

// Digital River Drop-in section
if ($('#dropInContainer').data('enabled')) {
$('.drop-in-container').removeClass('checkout-hidden'); // show drop-in form to enter new payment
$('.submit-payment').addClass('digitalriver-hide'); // next step will be launched from drop-in button instead

Add the following code in the <addNewPaymentInstrument> function.

// Digital River Drop-in section
if ($('#dropInContainer').data('enabled')) {
  • Script cartridge\client\default\js\paymentInstruments.js Add the Drop-in script to the page.


External interfaces

The cartridge uses the Digital River API endpoints. You can find API service documentation on the Digital River website:

There is a service sharing one profile and one credential.

  • DigitalRiver.http.service

Also, this cartridge uses the Digital River Drop-in external script to handle client payments.

Important: The DIGITAL_RIVER_DROPIN payment integration represents not one but multiple payment types such as credit card, PayPal, Wire Transfer, and so on. The Drop-in integration provides the selection of payment types, and the client-side/backend scripts handle it. We designed this cartridge mainly to handle the credit card payment type, though it will also successfully process any other payment type provided by the Drop-in integration. To add any business logic for a specific payment type or provide shoppers with a better customer experience, you can extend Drop-in data handlers as described below:


  • switch(source.type) in function saveDropInPaymentToWallet—to save any specific payment data from Drop-in to the customer wallet which will be used in further checkouts.

  • switch(paymentType) in function getPaymentInformationFromPaymentInstrument—to handle any payment type specific data which was saved in the customer profile.

  • switch(source.type) in function getPaymentInformationFromDropIn—to handle any payment type-specific data which was provided by Drop-in.


  • function extendDigitalRiverInfo—extract all information you want to be available in templates or be provided to the client-side as JSON.


  • switch(selectedPaymentInstrument.paymentType) in function updatePaymentInformation—add payment information to html. Make sure you have the necessary data provided by the Payment model.

Business Manager

We added new Business Manager menu options under Merchant Tools.

  • Request SKU's update—Click this button to request an SKU update on the Digital River-side with the next run of OptionalDigitalRiverSKUsUpdate. The button will show the corresponding text indicating that you can launch the job or that the job is running.

Note: Clicking Request SKUs update will not launch the job immediately, but it will raise a flag that must perform an update with the next run of OptionalDigitalRiverSKUsUpdate. If you haven't scheduled the job (in advance) in the Business Manager or (as an administrator) launched the job manually, clicking the button will have no impact at all.

  • Digital River Service Tester—A button in Business Manager to test Digital River service availability.

Clicking the Test Services button will make calls to the indicated web services and evaluate response codes.

Order information

The Digital_River_Dropin payment processor provides the following order information in Business Manager:

  • Select Merchant Tools, select Orders, choose an order, and click Payments.

    • Payment type (creditCard, PayPal, and so on) is mentioned.

    • Hyperlink to order on Digital River Dashboard.

  • Select Merchant Tools, select Orders, choose an order, and click Notes. A Digital River “create order” response is being saved in order notes.

  • Added drExportedDate custom attribute to the Product. It is updated each time the job runs.

Storefront functionality

The DigitalRiver.js library replaces the Salesforce built-in payment method forms and also renders Digital River Drop-in payment integration to fulfill the payment process. The payment methods will display on the billing page. The payment methods that display depend on the configuration of your LINK cartridge key by Digital River. Visit our Drop-in documentation for an updated listing of payment methods available.

Below is how payment methods will appear on the billing page:

  • Cartridge logic determines what additional fields will appear on the billing form.

  • When the customer clicks the Add New link in the My Account section, the Drop-in form with the specific configuration will appear. The form allows the customer to add a new payment within Drop-in and create a new source.