2021
Commerce API release notes for 2021.
Last updated
Was this helpful?
Commerce API release notes for 2021.
Last updated
Was this helpful?
We added the ability to .
We added the applyEmailToSubscriptions field to .
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 clicking a link or entering a coupon code.
You can set the trigger when you configure the offer type in Global Commerce.
We added the ability to set up the renew reminders for trial subscriptions.
We added the ability for a Customer Service Representative to cancel an order in Global Commerce.
We expanded the pay later options now available in the PayPal Wallet, including PayPal RatenZahlung for German shoppers.
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 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.
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.
To use this feature, contact your Digital River representative.
We added test and use cases to help you when you're developing and testing the Commerce API and your commerce connector.
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.
This feature provides data points to determine when you should or shouldn't retry a renewal attempt. It categorizes credit card decline reason codes into "soft" and "hard declines."
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:
Payment Method Guide: digitalriver.com/payment-method-guide
Country Guide: digitalriver.com/country-guide/
Updated the order states for the GET and POST orders APIs by adding In Review, Pending Payment, and Complete.
Corrected the API path domain in the examples. It's now api.digitalriver.com.
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 added information on initiating a charge.
We moved the Declined messages under Submitting a cart and renamed it Authorization declines.
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.
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 for. The parameter is available in both Drop-in payments 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 payments, 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.
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.
PaymentOptionsResponseLegacy
PaymentOptionsResponseLegacyExpand
PaymentOptionsResponsePaymentSource
PaymentOptionsResponsePaymentSourceExpand
A sourceId to GET /v1/shoppers/me/payment-options.
The following to the response schema for POST /v1/shoppers/me/carts/active/apply-payment-method:
ApplyPaymentMethodLegacy
ApplyPaymentMethodPaymentSource
DefaultOrderLineItems
ExpandedOrderLineItems
lineItemStateDetails
A chargeType to the subscriptionInfo section in the request and response. See Providing subscription information for more details.
We added the ability to use the Expired Card Optimizer (ECO) for .
We added support for using the resource to attach a tax ID to a cart using the tax resource.
We made the following changes to the :
In the response for , added shopper and renewalPrice to the subscription information attributes. We also added renewalPrice to the addOn object.
We made the following changes to the to allow you to suppress an order confirmation email.
Added the suppressorderconfirmationemail parameter to and .
We revised the statements for subtotal and discount at the order level for the .
We updated the that provide you with:
We added 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 .
We made the following to the :
Removed x-siteid and x-companyId headers for APIs. You only need to now.
Removed sku and displayName from the product object in the response for , , and resources.
Removed proratedUnitPrice from the resource.
Updated the payload for the request.
Updated the customAttributes for the .
Added chargeType to , , apply, apply, , and .
We added information on how to and manage subscriptions.
You can now use the in a Cart without a subscription line item to initiate a charge.
You can now find the In the Commerce API doc.
We moved the description of from the Commerce API Reference to .
Added the following to the response schema for :
The following to the response schema for :
We added the for using the Commerce API, which includes , , , Capturing the customer's IP address, and .