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 , you can now use .
When Digital River receives a , we now move the associated order's to dispute
.
Breaking changes
In 2021-12-13
, the following changes have been deployed:
In , Digital River no longer, by default, uses the associated data to populate certain undefined attributes. For each , you must now define that attribute in checkouts.
Digital River has removed from SKUs.
We made the following changes to :
You can now add, edit, and delete a fee from the page.
You can now view the metadata associated with an order from the page.
The page now displays the full checkout details.
You can now use query parameters to return a list of SKU groups.
Breaking changes
We now provide you the ability to:
Breaking changes
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.
We added the ability to from the Dashboard.
You're no longer allowed to .
You can now subscribe to the event.
Every physical SKU that is shipped cross-border into Switzerland must now contain a weight
and weightUnit
. Refer to the section on the page for details.
We added the ability to from the . You can also or to a customer.
We added a new , Digital River UK Limited.
We added the ability to and from the .
We now provide .
We now conduct enhanced .
We created new .
You can now .
We expanded the pay later options now available in the , including for German shoppers.
You can now .
Digital River now supports the use of .
You can now that share a basic Harmonized System code and are exported to the same countries.
You can now schedule and process recurring payments using .
We added supportsStorage
to indicate whether a payment method supports storage to .
We expanded the pay later options that are now available in the , including for shoppers in Australia and France, and and for UK shoppers.
You can now use the 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 .
We added the ability to . You can now and their , , , and .
We added support for to the payment method.
You can now , , and from the .
You can now from the .
You can now use and to attach and detach sources from invoices.
Digital River now supports the use of .
Using the , the you can upload to Digital River's servers is 10 MB.
You can now , , and your SKUs on the .
Digital River now supports the use of .
You can now from the resource.
We added OAuth as an additional authentication method when or in the .
Digital River now supports , 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 .
You can now include 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 or in the section.
You can now .
For troubleshooting purposes, we have implemented the following HTTP request headers: , , and . As a , we recommend including these headers in your requests.
You can now . Once properly configured, you can use them in the .
We made the following changes to the :
We now provide the order ID, upstream ID, status, tax type, tax ID, and tax state on the 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 page in the Dashboard.
You can now on the Order Details page.
You can now when performing testing
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 .
with POST /sources
.
Attach to a checkout.
Use to attach a source to a checkout.
Use to detach a source from a checkout.
When , 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 and make it the default type in .
When , you can now use to obtain an accurate tax calculation before you attach a payment source to the checkout.
We made the following changes in 2021-02-23
:
You can now access the .
For , you should now send in POST/fulfillments
requests.
You can now use the Digital River API to .
You can now use the to determine whether the saved payment source selected by a customer during the checkout process requires .
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 and . We recommend you use it when building and workflows that allow customers to save their credit card information.
When , you can now . Additionally, we created new that allow you to set the showTermsOfSaleDisclosure
and disableAutomaticRedirects
parameters.