PROD Release Notes – Ally Management V14(AN_ALMGMT_V14)

Adds Webhook Notifications for Merchant Payout Capability Status

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