Commerce API release notes for 2021.



We added a new legal entity, Digital River UK Limited.


We added the ability to create a refund for a delayed payment method such as Konbini, and Wire Transfer.


We added the ability to receive payment detail update notifications when a shopper updates their payment details for a subscription.


  • We added the ability to remove a tax identifier from a cart.

  • We added the trigger to the offer object response. The possible values are:

    • Always Triggered–The offer is available to any shopper in your store. Shoppers have to meet the conditions you set up in the offer for the offer to be triggered and redeemed by shoppers.

    • User Triggered–To redeem an offer, the shopper must take additional actions such as click a link or enter a coupon code.

    You can set the trigger when you configure the offer type in Global Commerce.

  • We added the ability to add or remove the organization identifier (client_reference_id) to a cart for the TreviPay payment method.


We added the ability to set the renew reminders for trial subscriptions.



We added instructions on how to get the inventory for a specific product.


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


We expanded the pay later options 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 containing instructions explaining how to complete payment for delayed payment types such as Konbini and Wire Transfer.


You can customize and control your subscription email notifications through events notifications and webhooks. This feature allows you to control your communications with your consumers, including integrating the capabilities of leading notification providers.


We added the ability to create a trial subscription for a subscription product and configure trial renewal reminders in Global Commerce.


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



  • We added test and use cases to help you when you're developing and testing the Commerce API and your commerce connector.

  • We updated the error codes that provide you with:

    • Additional credit card decline reason codes and metadata responses. You can then perform reporting and analytics to understand better why authorizations are declined so you can optimize your business.

    • Greater visibility into why a transaction failed, reducing the work you need to do to determine why the transaction failed.

    • Data points to determine when you should or shouldn't retry a renewal attempt. This feature categorized credit card decline reason codes into "soft" and "hard declines."


We added Site Management to the Commerce API Reference that includes the following resources:


You can now programmatically retrieve a list of your site's authorized billing or shipping countries using your Global Commerce user credentials.


We replaced Supported geographies for each payment method in DigitalRiver.js with Supported markets. To find information on supported markets and currencies for Drop-in and DigitalRiver.js, go to:



  • We added information on how to sell subscriptions with add-ons and manage subscriptions.

  • Digital River Clients can now 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 cash flow 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!


You can now use thechargeType in a Cart without a subscription line item to initiate a charge.


We 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.



We updated the information on landed cost.


  • We improved the error format for transactional errors using a credit card saved in the payment source and added a declined message (declinedMessage) to provide more information.

  • We moved the description of API keys from the Commerce API Reference to Best practices.


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).



We added information on creating a cart with a perpetual unit price using POST /v1/shoppers/me/carts/active/line-items resource.


A note to Apply shopper to cart stating this method requires an authenticated shopper token.


We added the best practices for using the Commerce API that include Authentication, Creating authenticated shopper tokens, Caching responses, Capturing the customer's IP address, and Elements.

Last updated