Production Release Notes – Ally Management V13 (AN_ALMGMT_V13)

Adds dedicated Payments section to the Ally Portal

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

Parameter	Change Type	Resource / Endpoint
shopperStatement	Added (optional)	Secure Merchant Onboarding API (Create)

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