What’s New

The Anytime Payment Portal has been upgraded from Angular version 15 to version 20. This brings the portal in line with the current Angular release, incorporating the framework improvements, performance enhancements, and security patches introduced across the v16–v20 range.

Why It Matters

Before this upgrade, the portal was running on an Angular version that no longer receives active support. You can now build against and integrate with a portal that runs on a current, actively maintained Angular version, reducing compatibility friction and exposure to unpatched vulnerabilities.

Upgrade

1. Ensure any custom Angular components or libraries embedded in or alongside the portal are compatible with Angular v20.
2. Review any peer dependencies in your integration that declared a constraint on Angular v15 and update them accordingly.
3. Re-test any portal customizations or overrides that interact with Angular lifecycle hooks, routing, or change detection, as behavior in these areas evolved between v15 and v20.

Introduces a Centralized Shared NPM Package for Angular Micro-Frontends

What’s New

A new shared NPM package centralizes common Angular code — including services, interceptors, components, pipes, constants, and enums — that was previously duplicated across multiple micro-frontend applications. All Angular 19+ micro-frontends now consume this single package instead of maintaining their own copies of shared logic.

Why It Matters

Before this change, the same code existed in multiple places, meaning a bug fix or enhancement had to be applied and tested in every application separately. You can now rely on a single source of truth for shared functionality, making updates faster and reducing the risk of inconsistencies across applications.

Upgrade

1. Remove any locally duplicated copies of shared services, interceptors, components, pipes, constants, or enums from your micro-frontend application.
2. Add the new shared package as a dependency in your package.json.
3. Update import paths in your application to reference the shared package rather than local copies.
4. Run your test suite to confirm no regressions from the import path changes.

Updates the Shared NPM Package to Support Consumer Application Requirements

What’s New

The centralized shared NPM package has been extended to include additional common functionality required by the consumer-facing Angular application. These additions ensure the package covers the full breadth of shared logic needed across the application suite, not just the initial set of micro-frontends.

Why It Matters

You can now use the shared package as the single dependency for common Angular code across both existing micro-frontends and the consumer application, without needing to maintain parallel implementations.

Adds Client-Side Payload Encryption for Payment Submission

What’s New

The payment submission API now supports full client-side payload encryption. Before a payment request is sent, the entire request body is encrypted on the client using a public key. The payload is only decrypted by backend services upon receipt. This behavior is controlled by a feature flag named cryptography — when the flag is on, all payment request payloads are encrypted in transit; when off, payloads are sent as plain text matching the existing behavior.

Why It Matters

Before this change, payment request payloads were transmitted without client-side encryption, relying solely on transport-layer security. You can now enable end-to-end payload encryption for payment submissions, significantly reducing the risk of sensitive payment data being exposed at any intermediate layer.

Changes

Parameter: Request body of POST /payment Change type: Modified — when the cryptography feature flag is enabled, the entire request payload is encrypted before transmission and must be decryptable by the backend using the corresponding private key. When the flag is disabled, existing behavior is preserved.

Fixes Stale Inline Validation Errors When Switching Payment Method Tabs

What’s New

On the payment method selection page, inline validation error messages for Banking Type and Account Type fields were not cleared when a user navigated from the Card tab to the ACH tab. The form now correctly resets these error states on tab switch, so only errors relevant to the currently active tab are shown.

Why It Matters

Before this fix, users switching from the Card tab to the ACH tab would see leftover error messages from the Card form, creating a confusing and misleading experience. Validation errors now only appear in the context of the tab the user is actively filling out.

Release Date: Feb 26th, 2026

Release Status: Deployed to PROD

This release contains the technical upgrades such as angular version upgrade (v15 to v20), NPMPackage for common code from UI, NPM package update, Client-Side Payload Encryption.

[AN-38395] – Anytime Payments Angular Upgrade

Upgraded the Anytime Payment Portal from Angular v15 tov20.

No

[AN-30796] – NPM Package – for common code from UI

Introduced a centralized shared package for all Angular 19MFEs to eliminate duplicate common code (services,interceptors, components, pipes, constants, enums).

This change ensures:

Single source of truth
Improved consistency across MFEs
Simplified maintenance and bug fixes
Easier version upgrades for all applications

No

[AN-35616]- Update NPM Package to accommodate other application changes

Changes to the NPM package to support new commonfunctionality required for the consumer Angular application.

No

[AN-41602]- Client-Side Payload Encryption for PaymentSubmission

Changes made in {{BaseURL}}/payment API to ensure that entire payload is encrypted on the client using a secure public key before being transmitted and decrypted only bybackend services.

NoFeatures Deployed to UAT ClientFacingImpact

Launch darkly Flag “cryptography’ is created. If Flag is ON, then the payment API entire request payload will be encrypted to secure the requested details.

If flag is OFF, then the payment API request payload willbe shown as is as per existing.

This change is implemented on anytime portal as of now.

[AN-46112] – Bug fixes on anytime portal payment method page.

Existing Behavior: The Inline error of Banking Type andAccount Type remains as is if user navigate from Card tabto ACH tab.

Yes

Fixed Behavior: No error will be displayed if user navigatefrom CARD tab to ACH Tab.

The post PROD Release – Angular Version Upgrade (AN_ANGUPD_V1) appeared first on AndDone.

• Release date: 2026-02-16
• Release status: Deployed to UAT
• Version: AN_ANGUPD_V1

Highlights

• [AN-38395] Anytime Payments Angular Upgrade – Upgraded from Angular v15 to v20.
• [AN-30796] NPM Package for common code from UI – Centralized shared package for all Angular 19 MFEs; single source of truth for services, interceptors, components, pipes, constants, enums.
• [AN-35616] Update NPM Package – Changes to support new common functionality for the consumer Angular application.
• [AN-41602] Client-Side Payload Encryption for Payment Submission – Entire payment payload encrypted client-side via LaunchDarkly ‘cryptography’ flag; implemented on Anytime Portal.
• [AN-46112] Bug fixes on Anytime Portal payment method page – Inline error cleared when navigating from Card to ACH tab.

References

• AN-38395
• AN-30796
• AN-35616
• AN-41602
• AN-46112

The post UAT Release – Angular Version Upgrade (AN_ANGUPD_V1) appeared first on AndDone.

What’s new

A new System Notification management interface is now available in the admin portal. Admins can create, schedule, preview, edit, and cancel maintenance notifications through a guided wizard. Each notification supports a rich-text body, a defined maintenance window with start and end times, and two configurable lead-time alerts that trigger automated emails ahead of the maintenance event. Notifications have a lifecycle status (Pending or Active) that controls which actions are available.

Why it matters

You can now communicate planned downtime to merchants at scale without manual intervention. Scheduling is handled by an automated job that fires emails at the configured lead times, reducing the risk of missed or delayed notifications during maintenance windows.

Adds dedicated System Maintenance notification tab to the merchant portal

What’s new

The merchant portal’s notification section now includes a new “System” tab. This tab surfaces all maintenance notifications sent by the platform in a single, dedicated view. Each notification arrives as a formatted email containing the subject, body, maintenance timing, and all relevant details.

Why it matters

Merchants now have a consistent, predictable place to review maintenance communications. Previously, platform-wide maintenance alerts had no dedicated display location in the portal — they now appear in a structured view alongside the formatted email delivered to their inbox.

Fixes saved-login autofill appearing on the wrong field in the merchant portal

What’s new

The browser’s saved-login suggestion popup was incorrectly appearing on the Password field rather than the Username field on the merchant portal login screen. This has been corrected so that the popup triggers on the Username field as expected. Selecting a saved username now also auto-fills the corresponding password.

Why it matters

Before this fix, the autofill prompt appeared in the wrong place, causing confusion and potentially interrupting the login flow. Users relying on saved credentials can now select their username and have both fields populated automatically without extra steps.

Fixes card payment UI overflow on Android devices

What’s new

On certain Android devices, the card payment section within the embedded payment widget was rendering outside the widget’s boundaries on the Contact Information page. The layout has been corrected so the card payment UI is fully contained within the widget frame across all screen sizes.

Why it matters

Merchants and their customers using Android devices will no longer encounter a broken or clipped payment UI. The widget now renders correctly regardless of screen size or device, ensuring a consistent checkout experience.

Enforces ACH banking and account type classification UI when feature flag is enabled

What’s new

When the ACH classification enforcement feature flag is turned on for a merchant, the UI for selecting banking type (e.g., Business) and account type (e.g., Checking) was not rendering correctly. This has been resolved so the classification fields display and function as intended whenever the flag is active.

Why it matters

Integrations that rely on ACH classification — particularly those requiring merchants to specify their banking and account type — can now correctly present the required fields to end users. This unblocks compliant ACH collection flows that depend on this classification step being visible and interactive.

Production Release Notes – Support New Notification Type (AN_NOTTYP_V1)

Release Date: Feb 9, 2026

Release Status: Deployed to Prod

────────────────────────────────────────────

New Platform Notification Type: Maintenance on admin portal [AN-34779]

A comprehensive system maintenance notification platform enabling admins to schedule and manage downtime communications to merchants at scale.

• New “System notification” submenu with listing table featuring pagination, search, and bulk actions (create, edit, cancel, preview)
• “New notification” wizard for maintenance events with title, rich-text body, maintenance window (start/end), and dual lead-time scheduling
• Real-time email preview with populated date placeholders
• Automated scheduler job orchestration with status tracking
• Cancel capability for Pending schedules (disabled for Active)
• Inline preview from listing view

Client Facing: Yes

────────────────────────────────────────────

New Platform Notification Type: Maintenance on merchant portal [AN-34780]

• Adds a new “System” tab in the merchant portal’s notification section
• Displays all System Maintenance notifications in one dedicated location
• Sends formatted email notifications to merchants about platform maintenance
• Includes proper email template with subject, body, timing, and necessary fields
• Provides maintenance details directly to merchant inboxes

Client Facing: Yes

────────────────────────────────────────────

[Merchant portal] Saved merchant login option getting displayed on password field [AN-43347]

Issue Description:The “saved username and password” suggestion popup was appearing on the Password field instead of the Username field.

Expected behavior/fix:The saved-login popup should appear when the user clicks on the Username field. When a saved username is selected, both username and password should be auto-filled.

Client Facing: Yes

────────────────────────────────────────────

Card payment method UI overflows outside payment widget frame on Android [AN-39045]

Issue Description:When using the payment widget on certain Android devices, the Card Payment section on the Contact Information page is not fully contained within the widget frame. The card payment UI overflows beyond the widget boundary, causing layout breakage.

Expected behavior/fix:Card payment method UI remains fully within the widget frame, responsive across all screen sizes.

Client Facing: Yes

────────────────────────────────────────────

ACH – classification: 2 new type → banking and account type: Expected UI is not getting displayed [AN-44026]

Issue Description:When the ach-classification-enforcement feature flag is turned ON for a merchant, the expected UI for selecting “banking” and account types (e.g., Business & Checking) does not display correctly.

Expected behavior/fix:The new classification UI should be visible and fully functional, allowing selection of the appropriate banking and account type values.

Client Facing: Yes

The post Production Release Notes – Support New Notification Type (AN_NOTTYP_V1) appeared first on AndDone.