2021
Digital River API release notes for 2021.
Last updated
Digital River API release notes for 2021.
Last updated
You can now use Global Logistics, an end-to-end cross-border delivery management solution.
When sending product data in checkouts, you can now use productDetails.
When Digital River receives a chargeback request, we now move the associated order's to dispute.
Breaking changes
In 2021-12-13, the following changes have been deployed:
In registered checkouts, Digital River no longer, by default, uses the associated data to populate certain undefined attributes. For each attribute common to customers and checkouts, you must now define that attribute in checkouts.
Digital River has removed allowOversell from SKUs.
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. Refer to the weight and weightUnit section on the Managing SKUs page for details.
We added the ability to manage customers from the Digital River Dashboard. You can also attach a tax certificate or tax ID to a customer.
We added a new legal entity, Digital River UK Limited.
We added the ability to fulfill an order either partially or fully and cancel a fulfillment order either fully or partially from the Digital River Dashboard.
We now provide test tax identifiers.
We now conduct enhanced validation of SKU group identifiers.
We created new rules for deleting SKU groups.
You can now use query parameters to return a list of SKU groups.
We expanded the pay later options 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 countries.
You can now schedule and process recurring payments using Digital River's subscription service.
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, and PayPal Pay in 3 and PayPal Credit for UK shoppers.
You can now use the Delayed Payment Instructions element to generate a template containing instructions for completing payments 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 add, edit, and delete a SKU from the Digital River Dashboard.
You can now accept a return from the Digital River Dashboard.
Digital River now supports the use of bPay with Store Credit.
You can now search, filter, and view your SKUs on the Digital River Dashboard.
Digital River now supports the use of Konbini with Store Credit.
We added OAuth as an additional authentication method when creating or editing a webhook in the Digital River 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 the Digital River 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.
You can now configure SKUs for Digital River managed fulfillments. Once properly configured, you can 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), discounts, 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.
You can now receive mock tax invoices and credit memos when performing testing
Breaking changes
We now provide you the ability to:
Create secondary payment sources with POST /sources.
Attach multiple secondary sources to a checkout.
Use POST /checkouts/{id}/sources/{sourceId} to attach a source to a checkout.
Use DELETE /checkouts/{id}/sources/{sourceId} to detach a source from a checkout.
When combining primary and secondary sources, you should know how to sequence their application in guest and registered checkout workflows.
Added the continue type to the list of button types for Drop-in and make 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
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. 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).
When creating a source, you can now configure the usage parameter. It allows you to specify the type of transaction the source will likely be used in the future. The parameter is available in both Drop-in and DigitalRiver.js. We recommend you use it when building purchase and account management workflows that allow customers to save their credit card information.
When creating an instance of Drop-in, you can now customize the button's text. Additionally, we created new Drop-in options that allow you to set the showTermsOfSaleDisclosure and disableAutomaticRedirects parameters.
You can now .
You can now use and to attach and detach sources from invoices.
Using the Files API, the you can upload to Digital River's servers is 10 MB.
You can now access details on product-level fee amounts from the resource.
For troubleshooting purposes, we have implemented the following HTTP request headers: , , and . As a , we recommend including these headers in your requests.
In 2021-03-23, the and 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.
We made the following changes in 2021-02-23: