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 , Digital River UK Limited.
We added the ability to such as and .
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 .
We added the trigger
to the 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 in Global Commerce.
To use this feature, contact your Digital River representative.
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."
Corrected the API path domain in the examples. It's now api.digitalriver.com
.
PaymentOptionsResponseLegacy
PaymentOptionsResponseLegacyExpand
PaymentOptionsResponsePaymentSource
PaymentOptionsResponsePaymentSourceExpand
ApplyPaymentMethodLegacy
ApplyPaymentMethodPaymentSource
DefaultOrderLineItems
ExpandedOrderLineItems
lineItemStateDetails
We added the ability to .
We added the ability for a Customer Service Representative to in
We added the ability to for .
We added support for using the resource to using the tax resource.
We expanded the pay later options now available in the , including for German shoppers.
We added instructions on how to .
We added supportsStorage
to indicate whether a payment method supports storage to .
We expanded the pay later options 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.
You can customize and control your subscription email notifications through . This feature allows you to control your communications with your consumers, including integrating the capabilities of leading notification providers.
We added the ability to for a subscription product and configure trial renewal reminders in .
We added support for to the payment method.
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 added to help you when you're developing and testing the Commerce API and your commerce connector.
We updated the that provide you with:
Additional and metadata responses. You can then perform reporting and analytics to understand better why authorizations are declined so you can optimize your business.
We added to the Commerce API Reference that includes the following resources:
You can now programmatically retrieve a list of your site's or using your .
We replaced Supported geographies for each in with Supported markets. To find information on supported markets and currencies for Drop-in and DigitalRiver.js, go to:
Payment Method Guide:
Country Guide:
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 for the GET and POST orders APIs by adding In Review
, Pending Payment
, and Complete
.
Updated the customAttributes
for the .
Added chargeType
to , , apply, apply, , and .
We added information on how to and .
You can now use the in a Cart without a subscription line item to .
We added the continue
type to the list of button types for and make it the default type in .
We added information on .
We moved the Declined messages under and renamed it .
You can now find the In the doc.
We updated the information on .
We improved the 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 from the Commerce API Reference to .
You can now use the to determine whether the saved payment source selected by a customer during the checkout process requires (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 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.
We added information on using POST /v1/shoppers/me/carts/active/line-items
resource.
A note to stating this method requires an authenticated shopper token.
Added the following to the response schema for :
A sourceId
to .
The following to the response schema for :
The following to the response schema for :
A chargeType
to the subscriptionInfo
section in the request and response. See for more details.
We added the for using the Commerce API, which includes , , , , and .