Release date: March 26, 2026

Adds Email Notifications for Sub-Merchant Lifecycle Events

What’s New

Allies can now receive email notifications whenever key lifecycle events occur for the sub-merchants they manage. Covered events include onboarding, activation, deactivation, and other merchant status changes. This gives Allies a passive, real-time awareness of their portfolio without requiring them to actively check the portal.

Why It Matters

Before this change, Allies had no automated way to learn when a sub-merchant’s status changed — they had to log in and check manually. You can now rely on email alerts to stay informed about merchant lifecycle activity as it happens, reducing the risk of missing critical changes.

Sends Notifications When Webhook Configurations are Added or Removed

What’s New

Allies receive an email notification whenever a webhook is added to or deleted from their account. This ensures that any change to webhook configuration — whether intentional or unexpected — is surfaced to the Ally promptly.

Why It Matters

Webhook changes can silently break downstream integrations if they go unnoticed. You can now detect configuration changes immediately and investigate or respond before any integration impact escalates.

Restricts Merchant Management Webhook Module to IPFS Allies Only

What’s New

The Merchant Management webhook module in the Ally Portal is now only visible and accessible to Allies who are set up as IPFS Allies. Non-IPFS Allies no longer see this module in their webhook subscription interface.

Why It Matters

Previously, non-IPFS Allies could see webhook modules that were not applicable to their account type, leading to confusion. You can now expect the webhook subscription UI to reflect only the options relevant to your Ally configuration.

Fixes Recurring Scheduler Errors Caused by Special Characters in Merchant References

What’s New

The transaction correction scheduler previously failed every 30 minutes when processing records where the Merchant Reference field contained special characters, including single quotes. The underlying SQL update logic has been corrected to handle these characters safely.

Why It Matters

Transactions containing special characters in the Merchant Reference field were getting stuck and never advancing to the correct status. Those transactions now process reliably, and the scheduler no longer produces recurring errors.

Displays Split Reference Identifiers in the Payment Details UI

What’s New

When a payment is split into multiple portions, each split’s merchant-provided reference identifier is now stored and displayed in the UI. This appears in both the standard payment intent flow and the secure payments flow, within the split payment details view.

Why it Matters

You can now verify and cross-reference each portion of a split payment against the merchant-assigned reference — useful for reconciliation, auditing, and tracking individual splits through your own systems.

UAT Release: Ally Management V15 (AN_ALMGMT_V15) Release Ticket:

Release Date: Mar 26, 2026

Release Status: Done

Summary

Ally Sub‐merchant Activity Notifications – Ally notification capabilities are extended so Allies can receive email updates about key sub‐merchant activities (such as onboarding, activation, deactivation and other changes), helping them stay informed about merchant lifecycle events.

Ally Portal Webhooks & Admin UI Consistency – The Ally Portal webhook subscription experience is refined so IPFS‐specific modules are no longer shown to non‐IPFS Allies, and Admin portal Ally table visuals are aligned for a more consistent UI.

Transactions, Monitoring & Front‐end Hardening – Transaction correction handling is made robust for special characters, Additional UI support is added for displaying split references on split payments.

AN-45805: UAT Release – Ally Management (AN_ALMGMT_V15)

POST DEPLOYMENT MONITORING

Ally Notifications | Sub‐merchant related updates (Epic AN-41458) Enables Allies to receive email notifications for activity related to their sub‐merchants (such as activations, deactivations or other updates), so they are aware of important lifecycle changes for the merchants they manage.

Client Facing Impact: YES

Ally Notifications | Ally webhook Added/deleted (AN-36995) Sends Ally notifications when a webhook is added or deleted for an Ally, ensuring Allies are informed whenever webhook configurations they rely on are changed.

Client Facing Impact: YES

Ally Portal | Hide Merchant Management Webhook Module (Non‐IPFS Allies) (AN-46091) Restricts the Merchant Management webhook module

Client Facing Impact: YES

in Ally Portal so it is only listed and available for IPFS Allies, preventing non‐IPFS Allies from seeing or subscribing to IPFS‐specific webhook modules.
[PROD] – Console statement “Angular is running in development mode.” is visible on production environment (AN-46887)
Cleans up the UI console in production so the “Angular is running in development mode.” message and related development‐mode logs are no longer shown, aligning browser console behavior with production standards.

Client Facing Impact: NO

Regression Ally: Inconsistent UI on Allies table in Admin portal (AN- 46404)

Fixes a UI regression on the Allies table in the Admin Portal by restoring the missing divider line above the Actions menu, ensuring a consistent and polished table layout.

Client Facing Impact: NO

Encountered the scheduler error Transaction Entity Correction Handler for every 30 minute. (AN-45359)
Fixes an issue in Transaction Entity Correction Handler where SQL updates failed when the Merchant Reference field contained certain special characters (including single quotes), preventing recurring scheduler errors and ensuring affected transactions move to the correct status without failures.

Client Facing Impact: NO

Ability to display Split Reference in UI (AN-44749) Stores and displays each split’s merchant‐provided reference in the UI for split payment details (via existing payment intent and secure payments flows) so users can verify and track the reference associated with each split portion of a payment.

Client Facing Impact: YES

The post Production Release Notes – Ally Management V15(AN_ALMGMT_V15) appeared first on AndDone.

• Release date: 2026-03-26
• Release status: Deployed to UAT
• Version: AN_OUTPAY_V9

Highlights

• Outbound Payment Notifications – New Event Name ‘Outbound Payments’ under Notifications; event types: Vendor Approved, Vendor Denied, Vendor Approval Status Changed by Admin.
• Vendor Approval Notification Template – Email includes event timestamp, Merchant DBA, Company Name, Vendor Name, Vendor ID, and Legal Entity Type.
• Outbound Payment Status Notifications – Merchants receive notifications for status changes: Printed, Mailed, Transit, Delivered, Cancelled, Failed.
• Merchant Configuration – Merchants can enable/disable notifications, edit email templates, and update distribution lists via Merchant Portal.

The post UAT Release Notes – Outbound Payments (AN_OUTPAY_V9) appeared first on AndDone.

What’s New

Allies can now subscribe to webhook notifications that fire when payout capabilities are confirmed for one of their merchants. When a merchant’s payout capability status changes, the event is pushed directly to the Ally’s configured webhook endpoint.

Why It Matters

Before this change, Allies had no automated signal to confirm that a merchant was ready to receive payouts — they had to poll or check manually. You can now use these webhooks to gate payout initiation logic in your integration, ensuring payouts only go out once the capability is confirmed.

Introduces a Dedicated Reporting Section in the Ally Portal

What’s New

The Ally Portal now includes a standalone Reporting section where Allies can view and download their reports. Reports are accessible directly from the portal without requiring separate tooling or manual exports.

Why It Matters

You can now access and download Ally reports from a single, consistent location in the portal rather than relying on out-of-band delivery or external tools.

Delivers Remaining Notification Management APIs for the Ally Portal

What’s New

The full set of Ally notification management APIs is now available. These APIs allow the Ally Portal to manage notification templates, distribution lists, and notification statuses, bringing the Ally notification experience into parity with how merchant notifications are managed elsewhere in the platform.

Why It Matters

The final API endpoints needed to fully manage Ally notifications — including creating and updating templates and controlling distribution lists — are now available. You can now build or configure complete notification management workflows without hitting missing endpoints.

Sends Notifications When a Sub-Merchant Is Created

What’s New

Allies now receive a notification whenever a new sub-merchant is created under their account. The notification is delivered using the Ally’s existing distribution lists and subscription preferences.

Why It Matters

You can now react programmatically or operationally to new sub-merchant creation as it happens, rather than discovering new merchants only through manual portal checks.

Sends Notifications When a Sub-Merchant Completes Onboarding

What’s New

When a sub-merchant finishes the full onboarding process, Allies receive a notification that includes the merchant’s virtual account details. This notification is delivered to Allies who have subscribed to this event type.

Why It Matters

You can now use this notification as the trigger for initiating payouts to a newly onboarded merchant, eliminating the need to poll for onboarding completion or manually confirm virtual account availability.

Sends Notifications When a Sub-Merchant Is Activated

What’s New

Allies receive a notification when one of their sub-merchants is activated and becomes eligible to process payments. Delivery follows the Ally’s configured subscription and distribution list settings.

Why It Matters

You can now automate downstream workflows — such as enabling payment flows or updating merchant status in your own systems — immediately upon merchant activation, without manually monitoring the portal.

Sends Notifications When a Sub-Merchant Is Deactivated

What’s New

Allies receive a notification when one of their sub-merchants is deactivated. The notification gives Allies an immediate signal to follow up with the platform or communicate proactively with the affected merchant.

Why It Matters

You can now detect merchant deactivation events in real time and respond — whether that means investigating a potential error, pausing related workflows, or reaching out to the merchant — rather than discovering the change after the fact.

Enforces API Versioning on Ally Secure and Payout APIs

What’s New

Ally secure merchant and payout APIs are now baselined at version 2.3. The x-version header is mandatory for Ally merchant APIs. Payout APIs support versions 2.0 and 2.3, with 2.3 as the default. Requests that supply an unrecognized or unsupported version are rejected with an explicit error.

Why It Matters

Unversioned or incorrectly versioned requests to Ally merchant APIs will now be rejected rather than silently processed. Review your integration to ensure the x-version header is present and set to a supported value before this change affects your traffic.

Changes

Parameter: x-version header Change type: Now required (previously optional) Affects: Ally secure merchant APIs

Parameter: x-version header Change type: Modified — defaults to 2.3; valid values are 2.0 and 2.3; unsupported values return an error Affects: Ally payout APIs

Restricts Merchant Management Webhooks to IPFS Allies

What’s New

The Merchant Management webhook module in the Ally Portal is now only visible and subscribable for IPFS Allies. Non-IPFS Allies no longer see this module in their webhook configuration interface.

Why It Matters

Non-IPFS Allies were previously exposed to a webhook module that had no relevance to their account type, creating confusion. The webhook subscription UI now reflects only the modules applicable to your Ally configuration.

Enforces Correct Partner Sell Rate Behavior for Default Account Transactions

What’s New

When a transaction uses an AndDone Default account, the Partner Sell Rate is now explicitly set to NULL rather than inheriting an incorrect value. Additionally, Partner Profitability reports and statements are suppressed for IPFS Allies, ensuring profitability calculations follow the correct business rules for each scenario.

Why It Matters

Before this change, profitability data could reflect incorrect Partner Sell Rate values when default accounts were involved. You can now rely on Partner Profitability reports to accurately represent only the transactions and configurations they are designed to cover.

Adds a View Ally Details Page in the Admin Portal

What’s New

A new View Ally Details page is available in the Admin Portal. It surfaces a comprehensive view of an Ally’s configuration, including allowed payment methods, enabled fees, active features, and quick-action links such as viewing the Ally’s associated merchants.

Why It Matters

Previously, Ally configuration details were scattered or required navigating multiple screens. You can now inspect the full state of any Ally’s setup from a single page in the Admin Portal.

Allows Admins to Add and Edit IPFS Provisioning Data for Sub-Merchants

What’s New

Admin users can now enter and update IPFS Payments provisioning fields — such as Agency ID and Branch ID — for Ally sub-merchants directly from the Admin Portal. This covers cases where the data was not supplied during the secure onboarding flow.

Why It Matters

When provisioning data is missing after onboarding, IPFS payment features cannot be activated. You can now unblock those merchants by supplying the missing identifiers through the Admin Portal without requiring a re-onboarding flow.

Adds Ally Admin Lockout Visibility and Unlock Action in Admin Portal

What’s New

When an Ally Admin account is locked out, the Admin Portal now shows a lock icon and a tooltip indicating the locked state. Admins can trigger an Unlock Ally Admin action with a confirmation step to restore access immediately, without waiting for automatic unlock.

Why It Matters

Previously, there was no visual indicator of a locked Ally Admin, and restoring access required waiting for an automatic timeout. You can now identify and resolve lockouts proactively, reducing disruption for Ally Admins who need immediate access.

Corrects Transaction ID Linking in the Quote Timeline

What’s New

The quote timeline now correctly links the transaction ID to the “Downpayment Authorized” event. Previously, the link was incorrectly attached to the “Sent for Booking” event, which did not reflect the actual sequence of backend operations.

Why It Matters

The transaction ID link in the timeline now points to the correct event, making it straightforward to trace a downpayment transaction from authorization through to booking without being directed to the wrong step.

Updates Quote Timeline State Sequence for Down Payment Flows

What’s New

The quote timeline has been updated for both standard and Autopay flows to consistently record “Downpayment Authorized” — with the transaction ID attached — before progressing to “Sent for Booking,” “Quote Booked,” and “Loan Account Created” where applicable. This aligns the displayed timeline with the actual backend processing order.

Why It Matters

Before this fix, the timeline sequence could be inconsistent or out of order for down payment events, making it difficult to track payment progress accurately. The timeline now provides a reliable, ordered view of each stage in the quote lifecycle.

UAT Release: Ally Management V14(AN_ALMGMT_V14)

Release Ticket: AN-43591 – UAT Release – Ally Management (AN_ALMGMT_V14)

Release Date: Feb 26, 2026

Release Status: Post Deployment Monitoring

Summary

Ally Merchant Notifications & Webhooks – New Ally notifications inform Allies whensub‐merchants are created, onboarded, activated or deactivated, and Admins can now seelocked‐out Ally Admins and unlock them directly from the Admin Portal. Merchant Management webhooks are restricted to IPFS Allies only.

Ally Portal Configuration, Fees & Reporting – Ally APIs are versioned and standardized at2.3 for secure Ally and payout APIs; IPFS‐specific behavior for AndDone default accounts inPartner share and profitability reporting is now enforced; Al Admins can view detailed Allyconfiguration (features, fees etc ) through view ally details page on Admin portal.

IPFS & Provisioning Improvements – Admins can capture and edit mandatory IPFSPayments provisioning data (like agency/branch identifiers) for Ally sub‐merchants directlyfrom the UI when it’s not provided via secure onboarding.

Quote Timeline & UI Fixes – The quote timeline around downpayments is corrected so thetransaction ID is linked to “Down Payment Authorized”, and the UI now correctly shows theupdated timeline states.

Features Deployed to UAT

Ally Payout capability status webhooks

(Epic AN-42836)

Enables Allies to receive payout status updates for their merchantsvia webhooks so they can confirm that payout capabilities are inplace before initiating payouts.

Client facing impact: YES

Ally Portal | Reporting Section

(Epic AN-38481)

Introduces a dedicated Reporting section on the Ally Portal so Allies can quicklyview and download their reports for further analysis.

Client facing impact: YES

Ally Notifications | AllyPortal APIs

(Epic AN-38639)

Delivers the remaining Ally notification APIs from V13 release needed by AllyNO Portal to manage Ally notifications (templates, distribution lists,statuses) in alignment with the Merchant notification experience.

Client facing impact: NO

Ally Notifications | Submerchant Onboarded

(AN-41462)

Sends an Ally notification when a sub‐merchant is fully onboarded,including virtual account details so Allies can initiate payouts to thatmerchant when subscribed to this notification.

Client facing impact: YES

Ally Notifications | Submerchant Activated

(AN-41460)

Notifies Allies when one of their sub‐merchants is activated, allowing themto start processing payments for that merchant once they aresubscribed and distribution lists are configured.

Client facing impact: YES

Ally Notifications | Submerchant Deactivated

(AN-41461)

Notifies Allies when a sub‐merchant is deactivated so they can reach out to AndDone in case of errors or proactively communicate with the merchant.

Client facing impact: YES

Ally API Versioning | Secure APIs

(AN-40411)

Baselines Ally secure merchant and payout APIs to version 2.3, making x-version mandatory for Ally merchant APIs and supporting 2.0/2.3 (with defaulting) for payouts, while rejecting invalid versionswith explicit errors.

Client facing impact: YES

Ally Webhooks | Hide Merchant Management module fornon‐IPFS Allies

(AN-41791)

Restricts the Merchant Management webhook module in Ally Portal so it is only visible and subscribablefor IPFS Allies, preventing other Allies from receiving IPFS‐specific boarding events.

Client facing impact: NO

Ally Fees | Partner Sell Rate – IPFS & AndDone Default scenarios

(AN-38998)

Ensures Partner Sell Rate is left NULL when an AndDone Default account is used on a transaction and suppresses Partner Profitability reports/statements for IPFS Allies, so profitability calculations reflect the correct business rules.

Client facing impact: YES

Ally Management | Admin Portal – View Ally Details

(AN-41113)

Adds a View Ally Details page in Admin Portal showing Ally details, allowed payment methods, enabled fees/features and actions (e.g.,View merchants), giving Admins a single place to inspect Ally onfiguration.

Client facing impact: YES

Ally Notifications | Submerchant Created

(AN-44003)

Sends a notification to Allies whenever a new sub‐merchant is created under them, acknowledging creation and using Ally‐managed distribution lists and subscriptions.

Client facing impact: YES

[CR] – Ally Submerchant feature – IPFS Payments – provisiondata

(AN-44621)

Allows Admin users to add and edit IPFS Payments provisioning data (e.g., Agency ID, Branch ID) for Ally sub‐merchants in the Admin Portal when it is not provided as part of secure onboarding, enabling feature activation.

Client facing impact: YES

Ally Management – Admin Portal | Unlock Ally

(Admin user) (AN-36482)

Shows a lock icon and tooltip when an Ally Admin is locked out, and provides an Unlock Ally Admin action with confirmation soAdmins can quickly restore access without waiting for automatic unlock.

Client facing impact: YES

Update Transaction Id link to down payment in quote timeline

(AN-44826)

Corrects the quote timeline so the transaction ID is linked to the “Downpayment Authorized” event instead of “Sent for booking”, aligning the UI with backend behavior.

Client facing impact: YES

Update Quote timeline when Down payment is processed

(AN-43310)

Updates quote timeline flows (with and without Autopay) so “Downpayment Authorized” is always recorded with the transaction ID, followed by “Sent for booking”, “Quote Booked” and “Loan Account Created” as applicable.

Client facing impact: YES

Migrate Monitoring from Lumigo to Dynatrace – PremiumFinance Project

(AN-38785)

Client facing impact: NO

Migrate Monitoring from Lumigo to Dynatrace -InfrastructureECS Project

(AN-38796)

Client facing impact: NO

Merchant portal – Report – GeneratedOn timestamp does not change when the timezone is updated

(AN-44667)

Bug fix for the correct date time format

Client facing impact: NO

The post PROD Release Notes – Ally Management V14(AN_ALMGMT_V14) appeared first on AndDone.

• Release date: 2026-02-26
• Release status: Post Deployment Monitoring
• Version: AN_ALMGMT_V14

Highlights

• Ally Payout capability status webhooks (AN-42836) – Allies receive payout status updates for their merchants via webhooks.
• Ally Portal | Reporting Section (AN-38481) – Dedicated Reporting section on Ally Portal for viewing and downloading reports.
• Ally Notifications | Submerchant Onboarded (AN-41462) – Ally notified when sub-merchant is fully onboarded.
• Ally Notifications | Submerchant Activated/Deactivated (AN-41460, AN-41461) – Lifecycle notifications for Ally merchants.
• Ally API Versioning | Secure APIs (AN-40411) – Baselines Ally secure APIs to version 2.3; mandatory x-version header.
• Ally Management | Admin Portal – View Ally Details (AN-41113) – Single-page view of Ally config, fees, features, and actions.
• [CR] Ally Submerchant IPFS Payments provision data (AN-44621) – Admins can add/edit IPFS provisioning data for Ally sub-merchants.
• Ally Management – Admin Portal | Unlock Ally (AN-36482) – Unlock locked-out Ally Admins directly from Admin Portal.
• Update Transaction Id link for down payment in quote timeline (AN-44826) – Transaction ID linked to ‘Downpayment Authorized’ event.

References

• AN-42836
• AN-38481
• AN-38639
• AN-41462
• AN-41460
• AN-41461
• AN-40411
• AN-41791
• AN-38998
• AN-41113
• AN-44003
• AN-44621
• AN-36482
• AN-44826
• AN-43310

The post PROD Release Notes – Ally Management V14 (AN_ALMGMT_V14) appeared first on AndDone.

• Release date: 2026-02-12
• Release status: Post Deployment Monitoring
• Version: AN_ALMGMT_V14

Highlights

• Ally Payout capability status webhooks (AN-42836) – Allies receive payout status updates for their merchants via webhooks.
• Ally Portal | Reporting Section (AN-38481) – Dedicated Reporting section on Ally Portal for viewing and downloading reports.
• Ally Notifications | Submerchant Onboarded/Activated/Deactivated/Created (AN-41462, AN-41460, AN-41461, AN-44003) – Full sub-merchant lifecycle notifications for Allies.
• Ally API Versioning | Secure APIs (AN-40411) – Baselines Ally secure merchant and payout APIs to version 2.3; mandatory x-version header.
• Ally Webhooks | Hide Merchant Management module for non-IPFS Allies (AN-41791) – IPFS-specific webhook module restricted to IPFS Allies only.
• Ally Fees | Partner Sell Rate – IPFS & AndDone Default scenarios (AN-38998) – Partner Sell Rate left NULL for AndDone Default accounts; profitability reports suppressed for IPFS Allies.
• Ally Management | Admin Portal – View Ally Details (AN-41113) – View Ally Details page with config, payment methods, fees, features, and actions.
• [CR] Ally Submerchant IPFS Payments provision data (AN-44621) – Admins can add/edit Agency ID, Branch ID for Ally sub-merchants in Admin Portal.
• Ally Management – Admin Portal | Unlock Ally (AN-36482) – Lock icon and Unlock Ally Admin action with confirmation dialog.
• Update Transaction Id link / Quote timeline for down payment (AN-44826, AN-43310) – Transaction ID correctly linked to ‘Downpayment Authorized’ event.
• Migrate Monitoring from Lumigo to Dynatrace (AN-38785, AN-38796) – Premium Finance and Infrastructure ECS projects migrated.
• Merchant portal Report GeneratedOn timestamp fix (AN-44667) – Correct date-time format when timezone is updated.

References

• AN-42836
• AN-38481
• AN-38639
• AN-41462
• AN-41460
• AN-41461
• AN-40411
• AN-41791
• AN-38998
• AN-41113
• AN-44003
• AN-44621
• AN-36482
• AN-44826
• AN-43310

The post UAT Release Notes – Ally Management V14 (AN_ALMGMT_V14) appeared first on AndDone.

What’s new

A new Payments section is now available on the Ally Portal, giving Allies a dedicated view of payments received by their merchants. The section includes filtering and search options to help Allies analyze payment activity across their merchant portfolio.

Why it matters

You can now view and analyze merchant payment data directly from the Ally Portal without needing to rely on separate reporting tools or API calls. Allies have a single, purpose-built interface for monitoring payment activity across all their merchants.

Converts Ally Monthly Profitability Report to merchant-level summary

What’s new

The Ally Monthly Profitability Report CSV has been restructured from a transaction-level report to a merchant-level summary, broken down by payment method (ACH, Debit, Credit). The file is now significantly smaller and easier to open while retaining all profitability insights.

Why it matters

Before this change, the report contained one row per transaction, making it unwieldy for allies with high transaction volumes. The new format condenses data to the merchant level, making the file practical to open and analyze in standard spreadsheet tools.

Exposes secure Payment Intent Timeline API to Ally users

What’s new

Allies can now access the existing secure Payment Intent Timeline API using an Ally user API key, with an optional app key. The API enforces proper authorization boundaries, returning appropriate errors when an Ally attempts to access payment intents outside their merchant portfolio.

Why it matters

You can now trace the full timeline of payment intents for your merchants directly via the Ally API, enabling deeper transaction analysis without requiring custom integrations or elevated access credentials.

Introduces Ally Portal notification APIs for listing and retrieving notifications

What’s new

Two new Ally Portal notification APIs are now available: one to list all notifications configured for an Ally, and one to retrieve the full details — including templates — for a specific notification by ID. These APIs mirror the existing Merchant notification API contract.

Why it matters

Allies can now programmatically inspect their notification configurations, making it easier to audit, debug, and integrate notification management into internal tooling or workflows.

Adds notification status management APIs for Ally Portal

What’s new

New Ally Portal APIs allow Allies to enable or disable individual notifications and pause or unpause all notifications in a single call. This gives Allies self-service control over notification delivery without requiring admin intervention.

Why it matters

Before this change, Allies had no programmatic way to manage the active state of their notifications. You can now build controls into your own tooling to pause notifications during maintenance windows or enable them as part of onboarding flows.

Adds API to list all template variables for Ally notification templates

What’s new

A new Ally Portal API returns all available template variables for a given notification template. This allows Allies to discover what variables are supported when customizing notification content, without needing to reference separate documentation.

Why it matters

You can now query available variables at runtime when building template customization UIs or automation, reducing guesswork and the risk of referencing unsupported variables in notification templates.

Introduces distribution list management APIs for Ally Portal notifications

What’s new

New Ally Portal APIs allow Allies to retrieve and update distribution lists (DLs) for notifications, including the email addresses within each list. The API contract matches the existing Merchant notification distribution list APIs for consistency.

Why it matters

You can now manage who receives Ally notifications programmatically, using the same patterns already established for Merchant notifications. This makes it straightforward to keep distribution lists in sync with your own contact management systems.

Adds template update and creation APIs for Ally Portal notifications

What’s new

New Ally Portal APIs support updating existing notification templates — both plain text and HTML — and creating new templates. These APIs are aligned with changes initiated from the TinyMCE editor and mirror the behavior of the existing Merchant-side template APIs.

Why it matters

Allies can now manage the full lifecycle of their notification templates via API, enabling programmatic template updates as part of onboarding flows or content management workflows.

Extends secure merchant onboarding API with optional shopper statement field

What’s new

The secure merchant onboarding API now accepts an optional shopperStatement field, allowing Allies to configure shopper statements for their merchants at the time of onboarding. The field applies the same validations as existing shopper statement configurations.

Changes

Why it matters

You can now include shopper statement configuration as part of a single onboarding API call, rather than requiring a separate follow-up update after the merchant is created.

Aligns Ally sub-merchant feature inheritance with Ally feature configuration

What’s new

Ally sub-merchant feature inheritance has been corrected so that features enabled or disabled at the Ally level are reflected consistently across all relevant Admin portal views — including the sub-merchant details page, the confirm edit screen, and the features access page.

Why it matters

Before this fix, enabling or disabling a feature at the Ally level could result in inconsistent states across portal views, making it difficult to verify what was actually configured for a sub-merchant. Feature state is now reliable and consistent wherever it is displayed.

Migrates Domain project monitoring from Lumigo to Dynatrace

What’s new

Monitoring for Domain project services — including MerchantKeyExpirationExecutor, MerchantSettingsCacheSyncService, and Domain.API — has been migrated from Lumigo to Dynatrace. The migration includes agent setup, traces, metrics, dashboards, alerts, and removal of existing Lumigo configuration.

Why it matters

Observability for Domain project services now runs through Dynatrace. Teams relying on Lumigo dashboards or alerts for these services should update their monitoring workflows accordingly.

Migrates Infrastructure project monitoring from Lumigo to Dynatrace

What’s new

Monitoring for key Infrastructure services — including InfrastructureAllyHandler, InfrastructureMerchantHandler, and Infrastructure.API — has been migrated from Lumigo to Dynatrace, standardizing observability across the platform.

Why it matters

Infrastructure service monitoring now runs through Dynatrace. Teams using Lumigo for alerts or dashboards on these services should transition their observability setup to Dynatrace.

Continues Transaction project monitoring migration to Dynatrace (Part 3)

What’s new

Additional Transaction project services — including TransactionAllyHandler and related components — have been migrated from Lumigo to Dynatrace, ensuring consistent tracing and metric coverage across the Transaction project.

Why it matters

This continues the incremental migration of Transaction project monitoring to Dynatrace. Teams should verify that alerting and dashboard coverage for TransactionAllyHandler is now configured in Dynatrace.

Completes Transaction project monitoring migration to Dynatrace (Part 5)

What’s new

This release completes additional migration steps for Transaction project monitoring in Dynatrace, including dashboard and alert parity with the previous Lumigo setup.

Why it matters

The Transaction project monitoring migration to Dynatrace is now at full parity with the previous Lumigo configuration. Any remaining Lumigo references for this project can be decommissioned.

Migrates Invoice project Lambdas to ARM64 (Graviton) processor

What’s new

Invoice project Lambda functions — including PaymentLinkHandler, ReceivableHandler, and MerchantHandler — have been migrated from x86 to ARM64/Graviton processors. This is an infrastructure-level change with no impact on API behavior or response contracts.

Why it matters

The migration to Graviton reduces compute costs and improves performance for Invoice project functions. No changes to integration code are required.

Fixes repeated NACHA notification emails after scheduler run

What’s new

A bug was causing NACHA notification emails to be sent repeatedly every 15 minutes for the same transaction batch after the 4:30 AM IST scheduler run. This has been resolved so that only the expected single notification is sent per transaction batch.

Why it matters

Before this fix, merchants and recipients were receiving duplicate NACHA emails in rapid succession, creating confusion and potential compliance concerns. Notification delivery is now consistent with expected behavior.

Fixes notifications not triggering for transaction events on QAT

What’s new

A defect was preventing subscribed users on QAT from receiving notifications for transaction events — including Failed and Authorization event types. This has been resolved and expected notification delivery has been restored.

Why it matters

Before this fix, transaction event notifications were silently failing on QAT, making it impossible to validate notification behavior during testing. Notifications now fire correctly for all subscribed event types.

Fixes page becoming unresponsive when entering Shift + Hyphen in Last Name field

What’s new

A UI bug on the Create Payment Link page caused the page to become unresponsive when a long numeric string followed by Shift + Hyphen was entered in the Last Name field. This has been resolved and the field now handles all input combinations without freezing.

Why it matters

Before this fix, specific keyboard input sequences on the Create Payment Link page could lock up the UI entirely, blocking the user from completing the payment link creation flow. The page now remains responsive under all input conditions.

Production Release Notes – Ally Management V13 (AN_ALMGMT_V13)UAT Release: Ally Management V13 (AN_ALMGMT_V13) Release Date: Feb 9, 2026 Release Status: Production

Summary

Ally Portal Payments & Reporting – Allies can now use a dedicated Payments section on the Ally Portal to view merchant payments. Payment intent timelines are also exposed via secure Ally APIs for deeper transaction analysis.

Ally Notification Self-Service – A full set of Ally Portal notification APIs is introduced, which will help in enabling Ally Portal to list notifications, manage statuses (including pause/unpause all), work with template variables, maintain distribution lists, and update/create templates, aligned with existing Merchant notification behavior.

Configuration, Inheritance & Observability – Ally sub-merchant onboarding and feature inheritance are improved to align configurations across portals, while monitoring is standardized by migrating multiple projects from Lumigo to Dynatrace. Additional UAT/production defects around notifications, NACHA emails and UI responsiveness are also addressed.

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

Ally Portal | Payments Section (AN-37771)

Provides a dedicated Payments section on the Ally Portal so Allies can view payments received by their merchants and analyze them using filters and search options.

Client Facing: Yes

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

[CR] Ally Fees | Changes to Ally profitability report.csv (AN-33858)

Changes the Ally Monthly Profitability Report from a transaction-level report to a merchant-level summary per payment method (ACH, Debit, Credit), making the file smaller and easier to open while preserving profitability insights.

Client Facing: Yes

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

Ally Payments | Secure Payment Intent Timeline (AN-36488)

Enables Allies to access the existing secure Payment Intent Timeline API using an Ally user API key (app key optional) so that they can trace payment intents for their own merchants and receive appropriate authorization errors otherwise.

Client Facing: No

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

Ally Portal Notification APIs | Get Notifications & Notification by Id (AN-39507)

Introduces Ally Portal notification APIs to list all notifications configured for an Ally and retrieve the details (including templates) for a specific notification, aligned with the Merchant notification APIs.

Client Facing: No

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

Ally Portal Notification APIs | Update status of a notification (AN-39509)

Adds Ally Portal notification APIs that allow Allies to enable or disable individual notifications and pause or unpause all notifications, giving them self-service control over notification delivery.

Client Facing: No

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

Ally Portal Notification APIs | List all Template Variables (AN-39511)

Provides an Ally Portal API to list all template variables for a given notification template so Allies can understand what variables are available when customizing notification content.

Client Facing: No

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

Ally Portal Notification APIs | Distribution List (Get & Put) (AN-39512)

Introduces Ally Portal APIs to create and manage distribution lists (DLs) for notifications, allowing Allies to retrieve and update email addresses within a DL using the same contract as Merchant notification APIs.

Client Facing: No

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

Ally Portal Notification APIs | Update template (AN-39513)

Adds Ally Portal APIs for updating existing templates (plain text and HTML) and creating new templates for Ally notifications, supporting changes initiated from the TinyMCE editor and mirroring Merchant-side behavior.

Client Facing: No

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

[CR] – Ally Submerchant Onboarding | Secure Onboarding API (Create) – Shopper Statement (AN-33725)

Extends the secure merchant onboarding API with an optional shopperStatement field so Allies can configure shopper statements for their merchants via API, with the same validations as existing shopper statements.

Client Facing: Yes

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

Ally Submerchant Feature Inheritance (AN-42726)

Aligns Ally sub-merchant feature inheritance with Ally feature configuration so that enabled features appear consistently across Admin portal views (sub-merchant details, confirm edit screen, and features access page) when Ally features are enabled or disabled.

Client Facing: Yes

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

Migrate Monitoring from Lumigo to Dynatrace – Domain Project (AN-38782)

Migrates monitoring for Domain project services (such as MerchantKeyExpirationExecutor, MerchantSettingsCacheSyncService and Domain.API) from Lumigo to Dynatrace, including agent setup, traces, metrics, dashboards, alerts and removal of existing Lumigo configuration.

Client Facing: No

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

Migrate Monitoring from Lumigo to Dynatrace – Infrastructure Project (AN-38781)

Migrates monitoring for key Infrastructure services (InfrastructureAllyHandler, InfrastructureMerchantHandler, Infrastructure.API, etc.) from Lumigo to Dynatrace, standardizing observability across the platform.

Client Facing: No

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

Migrate Monitoring from Lumigo to Dynatrace – Transaction Project – Part 3 (AN-41672)

Continues migration of Transaction project services to Dynatrace (including TransactionAllyHandler and related components), ensuring consistent tracing and metric coverage.

Client Facing: No

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

Migrate Monitoring from Lumigo to Dynatrace – Transaction Project – Part 5 (AN-41717)

Completes additional migration steps for Transaction project monitoring in Dynatrace, including dashboards and alert parity with the previous Lumigo setup.

Client Facing: No

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

Migrate Invoice Project Lambdas to ARM64 (Graviton) Processor (AN-41760)

Migrates Invoice project Lambdas (such as PaymentLinkHandler, ReceivableHandler and MerchantHandler) to ARM64/Graviton to improve performance and cost efficiency.

Client Facing: No

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

NACHA notification emails triggered every 15 minutes after scheduler run at 4:30 AM IST for the same transaction (AN-44537)

Fixes an issue where NACHA notification emails were repeatedly sent every 15 minutes for the same transaction batch after the scheduler run, ensuring only the expected notification is sent.

Client Facing: No

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

Notifications Not Triggering for Failed, Authorization or any Transactions event type on QAT (AN-44539)

Resolves a defect where subscribed users on QAT were not receiving notifications for transaction events (such as Failed or Authorization), restoring expected notification behavior.

Client Facing: No

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

[UAT] – Page Becomes Unresponsive When Entering Shift + Hyphen in Last Name Field (AN-40941)

Fixes a UI issue on the Create Payment Link page where entering a long numeric string followed by Shift + Hyphen in the Last Name field caused the page to become unresponsive.

Client Facing: Yes

The post Production Release Notes – Ally Management V13 (AN_ALMGMT_V13) 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.

• Release date: 2026-01-19
• Release status: Post Deployment Monitoring
• Version: AN_ALMGMT_V13

Highlights

• Ally Portal | Payments Section (AN-37771) – Dedicated Payments section for Allies to view merchant payments with filters and search.
• [CR] Ally Fees | Ally profitability report.csv changes (AN-33858) – Report changed from transaction-level to merchant-level summary per payment method.
• Ally Payments | Secure Payment Intent timeline (AN-36488) – Allies access Payment Intent Timeline API using Ally user API key.
• Ally Portal Notification APIs (AN-39507, AN-39509, AN-39511, AN-39512, AN-39513) – Full suite: list, update status, template variables, distribution lists, update templates.
• [CR] Ally Submerchant Onboarding | shopperStatement field (AN-33725) – Optional shopperStatement added to secure onboarding API.
• Ally Submerchant Feature Inheritance (AN-42726) – Aligns feature inheritance with Ally configuration across all Admin portal views.
• Migrate Monitoring from Lumigo to Dynatrace (AN-38782, AN-38781, AN-41672, AN-41717) – Domain, Infrastructure, and Transaction project migrations.
• Migrate Invoice Project Lambdas to ARM64 (AN-41760) – Graviton processor migration for cost and performance.
• NACHA notification email fix (AN-44537) – Stops repeated emails every 15 minutes for the same transaction batch.
• Notifications not triggering fix (AN-44539) – Resolves defect where subscribed users did not receive transaction event notifications on QAT.
• [UAT] Page unresponsive on Shift+Hyphen in Last Name field fix (AN-40941) – Prevents page freeze on Create Payment Link page.

References

• AN-37771
• AN-33858
• AN-36488
• AN-39507
• AN-39509
• AN-39511
• AN-39512
• AN-39513
• AN-33725
• AN-42726
• AN-38782
• AN-38781
• AN-41672
• AN-41717
• AN-41760
• AN-44537
• AN-44539
• AN-40941

The post UAT Release Notes – Ally Management V13 (AN_ALMGMT_V13) appeared first on AndDone.