New features
The following topics outline the new features introduced in this release.
DA Store – International Content Support for CA & MX (4311969)
This feature extends DA Store support beyond U.S. tax content to include international (INTL) tax content, specifically for Canada (CA) and Mexico (MX).
Because DA Store is designed for physical retail locations, international tax content support is limited to localized content. Similar to existing U.S. behavior – where stores can be configured for either nationwide or single‑state tax rules – INTL support allows configuration for either CA or MX, one country at a time, based on the store’s transaction location.
DA Store – Dynamic Location Retrieval (4650542)
This feature enables the DA Store application to dynamically retrieve location values from Kubernetes ConfigMaps and Secrets at runtime, eliminating the need for store‑specific overlays.
Dynamic location retrieval simplifies deployment and configuration management across store environments by allowing reuse of standardized overlays, reducing operational complexity, and improving consistency across DA Store deployments.
Work with your PS ETS team to understand how to configure this capability.
Configurable Termination Grace Period (4651222)
This feature extends deployment overlays to allow configuration of container termination behavior specifically for the configuration sync process. The enhancement ensures config sync containers can shut down gracefully, preventing pods from becoming stuck in a terminating state and allowing clean unmounting of volumes during restarts, upgrades, or rescheduling.
This improvement includes:
Configurable terminationGracePeriodSeconds for DA config sync (TDSS) containers via Helm overlays.
Support for configurable pre‑stop hooks to enable clean shutdown and completion of in‑flight sync activity.
Continued execution of config sync containers during shutdown until the grace period expires, reducing the risk of data loss.
DA Client – Apigee Authentication Support Using Client Secret (4819610)
This update enhances Apigee‑based authentication for DA client‑side integrations with the DA Mothership by adding support for client secret–based authentication.
While client assertion remains the recommended authentication method, this enhancement provides an alternative option that may better align with certain deployment environments or security policies.
Work with your ETS team to understand how to configure this capability.
DA Client – Configuration to Prevent Split Brain Issues (4296866)
This update enhances the default database configuration for DA client‑side deployments to mitigate potential split‑brain scenarios.
Recommended PostgreSQL high‑availability settings – previously applied through environment‑specific overlays – are now included as default values in the DB Helm chart. This ensures consistent behavior across all client environments and eliminates the need for client‑specific overlays to apply these safeguards.
Enhanced OpenShift compatibility (4965056)
Previously, DA encountered startup issues when deployed in certain modern cloud environments such as OpenShift. This occurred due to a security mismatch – the application relied on a fixed user ID, while platforms like OpenShift enforce the use of randomly assigned user IDs to meet stricter security requirements.
This enhancement improves compatibility and flexibility by updating the container configuration to remove the dependency on a hardcoded user ID. DA now uses standard group‑level permissions, allowing it to run successfully as a non‑root user which is an industry‑recommended security best practice.
As a result, DA can now be deployed more seamlessly in secure, modern cloud environments like OpenShift, simplifying installation for customers and aligning with current platform security standards.
Uptime Monitoring Report for DA Mothership (4692478)
To provide greater transparency into the availability and resilience of the DA Mothership, we will begin publishing uptime metrics for the Production environment. These metrics are intended to help customers build confidence that the DA Mothership is actively available to receive transactions from their DA instance(s).
Uptime reporting will begin in May 2026, covering data from April 2026, and will be published monthly thereafter. These metrics are informational only and do not constitute a service‑level agreement (SLA). They are provided to align with the uptime metrics already published for Enterprise Cloud–hosted environments, available
here. The specific location of the DA Mothership uptime metrics will be shared shortly.
While the DA Mothership may be available, there may be instances where audited transaction data appears in reporting (NGRA) with a delay. This is due to a two‑step process in which transactions are first synchronized to the DA Mothership and recorded in the audit database, and then subsequently synchronized to NGRA.