Release Notes for 1.8.1-GA

Added extension point for determining tax provider id

Introduced debug logging for checkout completion

CartOperationServices, MicroSecurityCommon

Introduced support for persisting values to order’s internal attributes

TaxCommon

Added support for displaying total fees in customer order history and admin order view

OrderClient, AdminWeb, Commerce NextJS Starter

Copy cart item type to order item type during order generation

CartOperationServices, OrderServices, CartClient, OrderClient, Commerce SDK, Commerce NextJS Starter

Added APPLE_PAY payment type to support ApplePay integration with Checkout.com

CartOperationServices, Checkout.com, Commerce SDK, NextJS Starter, OrderOperationServices, Payment Gateway Common, Payment SDK, PaymentTransactionServices

Improve WebClient extensibility and providers error handling

CartOperationServices, OrderOperationServices, PaymentTransactionServices, CustomerServices

Introduced support for payment distribution

OrderClient, OrderServices, AdminWeb

Introduce fulfillment cancellation payment priority to order payments by type, regardless of whether a refund or reverse-authorize needs to be executed.

OrderOperationServices

Introduced the ability to refund AUTHORIZE_AND_CAPTURE transactions when cancelling a fulfillment

OrderOperationServices

Introduced optional durable message sending to Order Operations

OrderOperationServices

Added support for the usage of the adjustment quantity field of line items

CartOperationServices, MicroservicesCommonDependencies, OfferClient, OrderCommon, OrderOperationServices, PromotionServices

Introduced updates to support working with payments that were flagged for manual fraud review & potentially captured via the review process

CartOperationServices, Checkout.com, Commerce SDK, OrderOperationServices, Payment Gateway Common, PaymentTransactionServices

Fixed fulfillment costs not included in tax calculation

Fixed calculation of the captured payment amount in FulfillmentCaptureWebhookListener#determineCaptureResultStatus when there are the AUTHORIZE_AND_CAPTURE transactions

Fixed payment priority sorting issue for captures by merging entries with the same keys