# 2022 ## 2022/12/29 Digital River adds Afterpay to the payment method roster! By leveraging Afterpay, your shoppers can buy now and pay for their purchases in 4 interest-free installments over 6 weeks. Learn how you can add Afterpay [here](/commerce-api/payments/supported-payment-methods/afterpay.md). ## 2022/11/08 * You can now bank on BLIK in Poland. BLIK is the must-have payment method for Polish shoppers. BLIK transactions accounted for 75% of ecommerce volume and a 60% market share of all ecommerce in Poland for 2021. BLIK boasts over 10.1 million active users and is continuing to grow. See [BLIK ](/commerce-api/payments/supported-payment-methods/blik.md)to add BLIK to your checkout. * We added support for Financial Process Exchange (FPX). FPX lets Malaysian shoppers pay for online purchases directly from their bank account. See [FPX Online Banking](/commerce-api/payments/supported-payment-methods/fpx-online-banking.md) to add FPX to your checkout. ## 2022/10/3 You can now [get all applied offers](/commerce-api/shopper-apis/cart/managing-offers-in-a-cart/getting-all-applied-offers.md), [remove a specific applied offer](/commerce-api/shopper-apis/cart/managing-offers-in-a-cart/removing-an-applied-offer.md) at the user level, or [remove all eligible offers](/commerce-api/shopper-apis/cart/managing-offers-in-a-cart/removing-eligible-offers.md), including site level and user level, from a customer's cart. We also added information on [reconciling conflicting offers](/commerce-api/shopper-apis/cart/managing-offers-in-a-cart/reconciling-conflicting-offers.md). ## 2022/9/9 You can now [update a subscriber's email address](/commerce-api/admin-apis/subscription-management/subscription-notifications/updating-the-subscribers-email-address.md#changing-the-billing-and-shipping-email-addresses-in-the-cart-before-placing-the-order) so they can receive [future notifications](https://help.digitalriver.com/help/gc/Administration/Email-Notifications/Email-notifications.htm) using their preferred email address. ## 2022/9/1 We added support for the [Trustly ](/commerce-api/payments/supported-payment-methods/trustly.md)payment method. Shoppers can use Trustly to make fast, simple, and secure payments directly from their bank accounts without the risk of fraud. ## 2022/8/24 We updated instructions to the [Global Commerce Help](https://help.digitalriver.com/internal-help/gc.htm) that explain how to [test the email notification](https://help.digitalriver.com/internal-help/gc/Administration/Email-Notifications/Email-notifications.htm#HowToTestTheEmailNotification) and [enable or disable email notifications](https://help.digitalriver.com/internal-help/gc/Administration/Email-Notifications/Email-notifications.htm#HowToEnableOrDisableEmailNotifications). ## 2022/8/19 You can now create an [iDEAL element](/commerce-api/resources/reference/elements/ideal-element.md) automatically, getting a user's agreement and [IBAN number ](/commerce-api/resources/reference/elements/iban-element.md#creating-an-iban-element)for single-use and recurring transactions. ## 2022/7/27 * We expanded our Klarna Pay Later offering with the addition of payment options in Canada, France, Ireland, Poland, and Portugal. You can learn more [here](/commerce-api/payments/payments-solutions/digitalriver.js/payment-methods/klarna.md). ## 2022/7/23 We added Flex Term Monthly Billing to our subscription platform. This feature allows you to [set up a subscription product and sell a monthly subscription with an annual commitment](https://help.digitalriver.com/help/gc/Products/All-Products/Creating-a-product.htm#HowToCreateAFlexTermRenewal). When a shopper uses Flex Term Monthly Billing, they will be billed once a month for their purchase. The shopper can choose any kind of commitment, such as 3, 6, 12, 24, or 36 months. Charges occur automatically every month until the commitment period is complete, at this point, the shopper can renew their subscription. ## 2022/6/30 * Fair Consumer Contracts Act (FCCA) enhancement \ We added support for the [German Fair Consumer Contracts Act (FCCA)](https://www.lexology.com/library/detail.aspx) by adding a dedicated cancellation page in German and English to the footer on-site "defaults" that allow sending a cancellation request without signing in. Notifications for request confirmation and reminders are available in German and English. [Learn more about FCCA](https://digitalriver.service-now.com/kb?id=kb_article_view\&sysparm_article=KB0010508). * Webhook service for Commerce API\ We released the [Webhook service](https://help.digitalriver.com/help/gc/Administration/Webhook-Service/Webhook-service.htm) for Commerce API. The Webhook service now supports events covering the entire [subscription lifecycle](https://docs.digitalriver.com/commerce-api-references/commerce-api-reference-guide/admin-apis-reference/subscriptions#subscription-lifecycle). You can manage the service through the [Global Commerce](https://gc.digitalriver.com/gc/ent/login.do) interface or the [Webhooks API](https://docs.digitalriver.com/commerce-api-references/admin-apis/webhook-management/manage-webhook-events). You can now integrate the Webhook service for Commerce API with endpoints to get an instant update on events throughout the entire [subscription lifecycle](https://docs.digitalriver.com/commerce-api-references/commerce-api-reference-guide/admin-apis-reference/subscriptions#subscription-lifecycle). We also updated the list of [webhook events](/commerce-api/events/events.md) in the Webhook service. You can now choose from more subscription events. ## 2022/6/29 * We added `precondition-failure` error codes to [409 Conflict](https://docs.digitalriver.com/commerce-api-references/warnings-and-error-codes/error-codes/error-codes-for-shopper-apis/409-conflict) in the [Error codes](https://docs.digitalriver.com/commerce-api-references/warnings-and-error-codes/error-codes) section. * We updated the following APIs: * Renamed "API Trigger Offer" to "[Trigger offer by cart](https://docs.digitalriver.com/commerce-api-references/shopper-apis/cart/api-trigger-offer#v1-shoppers-me-carts-active-api-trigger-offer)". * Added the [Trigger offer by line item](https://docs.digitalriver.com/commerce-api-references/shopper-apis/cart/api-trigger-offer#v1-shoppers-me-carts-active-line-items-api-trigger-offer). Use this API to trigger a product-level offer. * Updated the descriptions for the [Order lookup](https://docs.digitalriver.com/commerce-api-references/shopper-apis/orders/order-lookup#v1-shoppers-order-lookup) API. ## 2022/6/16 * We added support for [applying store credit](/commerce-api/shopper-apis/shopper-basics/common-use-cases/applying-store-credit.md) to non-recurring transactions. Store credit allows merchants to offer customers a store credit as a payment type at checkout. * We now support [two payments in a cart](/commerce-api/payments/sources/using-the-source-identifier.md). * You can now [detach a payment from a cart](/commerce-api/payments/sources/using-the-source-identifier.md#detaching-payment-sources-from-a-cart). * You can now create [secondary sources](/commerce-api/payments/sources/using-the-source-identifier.md#creating-secondary-sources) through the [Sources API](https://docs.digitalriver.com/commerce-api-references/admin-apis/payment-source/source-management#sources) by sending your confidential API key in a POST /sources request. ## 2022/6/1 We restructured the API tags and descriptions for the Shopper API as follows: * Renamed Apply Payment Methods to [Apply or Detach Payment Methods](https://docs.digitalriver.com/commerce-api-references/shopper-apis/cart/apply-or-detach-payment-methods) and added the [Detach all applied payment methods from the cart.](https://docs.digitalriver.com/commerce-api-references/shopper-apis/cart/apply-or-detach-payment-methods#v1-shoppers-me-carts-active-payment) * Restructured the offer API tags and revised their descriptions for [Retrieve all POP offers for a cart](https://docs.digitalriver.com/commerce-api-references/shopper-apis/cart/cart-offers#v1-shoppers-me-carts-active-point-of-promotions-popname-offers) and [Retrieve all offers](https://docs.digitalriver.com/commerce-api-references/shopper-apis/browse-product-discovery/offers#v1-shoppers-me-offers). * Updated the sample payload for [Retrieve cart applied offers](https://docs.digitalriver.com/commerce-api-references/shopper-apis/cart/cart-offers#v1-shoppers-me-carts-active-applied-offers). * Added [Update shopper payment options](https://docs.digitalriver.com/commerce-api-references/shopper-apis/shoppers/payment-options#v1-shoppers-me-payment-options-paymentoptionid-1). * We moved the following webhook APIs under [Webhook Management](https://docs.digitalriver.com/commerce-api-references/admin-apis/webhook-management/manage-webhook-events): * [Get all webhook subscriptions](https://docs.digitalriver.com/commerce-api-references/admin-apis/webhook-management/manage-webhook-events#webhooks) * [Create a new webhook](https://docs.digitalriver.com/commerce-api-references/admin-apis/webhook-management/manage-webhook-events#webhooks-1) * [Get a specific webhook by ID](https://docs.digitalriver.com/commerce-api-references/admin-apis/webhook-management/manage-webhook-events#webhooks-webhookid) * [Delete a webhook](https://docs.digitalriver.com/commerce-api-references/admin-apis/webhook-management/manage-webhook-events#webhooks-webhookid-1) * [Update a webhook](https://docs.digitalriver.com/commerce-api-references/admin-apis/webhook-management/manage-webhook-events#webhooks-webhookid-2) * We added [Payment Source](https://docs.digitalriver.com/commerce-api-references/admin-apis/payment-source/source-management) and added the following source APIs: * [Get a source by identifier](https://docs.digitalriver.com/commerce-api-references/admin-apis/payment-source/source-management#sources-id) * [Create a secondary source](https://docs.digitalriver.com/commerce-api-references/admin-apis/payment-source/source-management#sources) * Added `cart-charge-failure` to the list of [409 Conflict errors](https://docs.digitalriver.com/commerce-api-references/warnings-and-error-codes/error-codes/error-codes-for-shopper-apis/409-conflict) in [Error codes](https://docs.digitalriver.com/commerce-api-references/warnings-and-error-codes/error-codes). ## 2022/5/6 * We updated the [authorization decline codes](/commerce-api/shopper-apis/cart/submitting-a-cart/authorization-declines.md) for customer-initiated and merchant-initiated transactions. * We added more [error codes](https://docs.digitalriver.com/commerce-api-references/warnings-and-error-codes/error-codes), including the [credit card error codes](https://docs.digitalriver.com/commerce-api-references/warnings-and-error-codes/error-codes) and a DNS[ outage error message](https://docs.digitalriver.com/commerce-api-references/warnings-and-error-codes/error-codes). ## 2022/4/1 We upgraded Google Pay to offer the up-to-date Google Pay wallet experience. You can now [configure the dynamic Google Pay button](/commerce-api/resources/reference/elements/google-pay-elements.md#google-pay-element-styles-and-customization) by applying your preferred button styles. ## 2022/3/28 We added support for the [iDEAL ](/commerce-api/payments/payments-solutions/digitalriver.js/payment-methods/configuring-ideal.md)payment method. ## 2022/3/16 We added support for the [Bancontact ](/commerce-api/payments/payments-solutions/digitalriver.js/payment-methods/configuring-bancontact.md)payment method. ## 2022/1/26 We added support for the [Boleto ](/commerce-api/payments/payments-solutions/digitalriver.js/payment-methods/configuring-boleto.md)payment method. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.digitalriver.com/commerce-api/general-resources/release-notes/2022.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.