- v1.0.0-latest-prod
Added support for Payment Transaction Service managed saved payments
Also in 1.4.2
Saved payments were formerly managed by the Customer Service
Added SavedPaymentClient to support saved payment management via PTS
Added support for Account management
Accounts can have Saved Payments, Addresses, and Orders like customers
Added AccountClient to handle related API interactions Can handle
reading the accounts a customer is a member of
managing account members if the customer is an account admin
managing account addresses
reading account order history
handling cart approval workflow where an approver reviews a cart before it can be submitted as an order
Account saved payments are handled by SavedPaymentClient
Saved Payment Methods and Saved Address also now have a visibleToChildren field indicating if sub-accounts can inherit parent accounts' payment and addresses.
Inherited payments and addresses are read-only
Added support for new PaymentMethodOption domain that defines what payment methods are supported by the backend and should be handled on the frontend, e.g., credit card, gift card, store credit
Also in 1.4.2
Added support for 3DS payment endpoint
Also in 1.4.2
Added support for using Content Service endpoints
Also in 1.4.2
Added support for reading all of a customer’s non-finalized carts.
This allows a customer to have multiple in-process carts and also see any carts requiring approval or rejected by an approver.
Fixed issues with encoding search params
Also in 1.4.2
Updated ClientFilter#values to be an array of strings, to ensure that multiple facet values don’t get encoded together when they should be separate params
Updated stringifyParams to also encode for filters with complex structure
Added missing displayTemplate field on Product type
Also in 1.4.2
Fixed issues with pageable params page and size if the values passed were 0.
Previously they were being ignored.