Digital River API release notes for 2021.


You can now use Global Logistics, an end-to-end cross-border delivery management solution.



Breaking changes

In version 2021-12-13, the following changes have been deployed:


We made the following changes to Digital River Dashboard:

  • You can now add, edit, and delete a fee from the SKU details page.

  • You can now view the metadata associated with an order from the Order details page. ****

  • The Checkout details page now displays the full checkout details.


We added the ability to download a credit memo from the Dashboard.


You're no longer allowed to attach non-reusable sources to customers.


You can now subscribe to the order.cancelled event.


Every physical SKU that is shipped cross-border into Switzerland, must now contain a weight and weightUnit. For details, refer to the weight and weightUnit section on the Managing SKUs page.


We added the ability to the ability to manage customers from the Dashboard. You can also attach a tax certificate or tax ID to a customer.



We added the ability to fulfill an order either partially or fully and cancel a fulfillment order either fully or partially from the Dashboard.


We now provide test tax identifiers.



We expanded the pay later options that are now available in the PayPal Wallet, including PayPal RatenZahlung for German shoppers.


You can now use applicability to filter tax identifiers.


Digital River now supports the use of SEPA Direct Debit with Store Credit.


You can now group products that share a basic Harmonized System code and are exported to the same set of countries.


You can now use Digital River's subscription service to schedule and process recurring payments.


We added supportsStorage to indicate whether a payment method supports storage to Retrieving available payment methods.


We expanded the pay later options that are now available in the PayPal Wallet, including PayPal Pay in 4 for shoppers in Australia and France, as well as PayPal Pay in 3 and PayPal Credit for UK shoppers.


You can now use the Delayed Payment Instructions element to generate a template that contains the instructions that explain how to complete payment for delayed payment types such as Konbini and Wire Transfer.


Digital River now supports the use of Online Banking with Store Credit.


We added the ability to manage payment methods. You can now view payment methods and their details, enable currencies, manage countries, and disable a payment method.


We added support for Pay in 3 to the PayPal payment method.



You can now use POST/invoices/{id}/sources/{sourceId} and DELETE/invoices/{id}/sources/{sourceId} to attach and detach sources from invoices.


Digital River now supports the use of bPay with Store Credit.



Digital River now supports the use of Konbini with Store Credit.


In the Invoices resource, you can now access details on product-level fee amounts.


We added OAuth as an additional authentication method when you create or edit a webhook in the Dashboard.


Digital River now supports Alipay with Store Credit allowing you to offer Alipay with store credit on an order.


You can no longer issue order-level fee refunds. In addition to standard refunds, the types of order-level and product-level refunds we support are listed here.


You can now include bill to information in a POST/invoices request. Additionally, when we give you back an Invoice, it now contains a billTo value. This is true even when you did not send billTo in the payload of a POST/invoices.


The following physical attributes have been added to the Sales summaries and Transactions in Dashboard: client upstream ID, payment type, ship from country, ship to country, bill to country, and SKU tax code. These attributes appear when you export transactions or sales summary details in the Finance section.


You can now access details on product-level fee amounts.


For troubleshooting purposes, we have implemented the following HTTP request headers: upstream-id, upstream-session-id, and upstream-application-id. As a best practice, we recommend that you include these headers in your requests.


You can now configure SKUs for Digital River managed fulfillments. Once properly configured, you can then use them in the Digital River fulfillment model.


  • We made the following changes to the Dashboard:

    • We now provide the order ID, upstream ID, status, tax type, tax ID, and tax state on the Order Details page in the Dashboard.

    • We also add fees, landed cost (including importer duty and importer tax), discount, and tax for a line item on the Order Details page in the Dashboard.

    • You can now download an invoice on the Order Details page.

  • Digital River Clients now can extend a branded, fully managed line of credit program to their business buyers that is engineered to increase purchase frequency, average order values, brand loyalty, and cashflow, while mitigating risk. By offering TreviPay you cultivate a consumer-like purchase experience for buyers, so they can purchase what they need now and pay later with net terms – all online. Learn how you can offer TreviPay to your buyers!


When performing testing, you can now receive mock tax invoices and credit memos.


Breaking changes

In version 2021-03-23, the Checkout and Order resources now return the first-class payment attribute. This attribute contains the array of applied payment sources, the array of charges created from those sources, and additional payment session information. You can use this new session information to determine when to convert a checkout to an order.


Added the continue type to the list of button types for Drop-in and made it the default type in Customizing the text of the Drop-in button.


When sequencing address information in your checkout workflows, you can now use billTo to obtain an accurate tax calculation before you attach a payment source to the checkout.


Breaking changes

We made the following changes in version 2021-02-23:

  • You can now access the tax identifiers resource.

  • Tax identifiers must be created using the Tax Identifiers API. You can no longer use the Customers API to perform this operation.

  • Once you've upgraded, any tax identifiers you previously created with the Customers API will no longer be available. Please contact us to have your data migrated.


For Digital River coordinated fulfillments, you should now send shipment identifiers in POST/fulfillments requests.


You can now use the Digital River API to manage an order's physical fulfillment.


You can now use the authenticateSource method to determine whether the saved payment source selected by a customer during the checkout process requires Strong Customer Authentication (SCA).


Last updated