• Release date: April 17, 2026
• Release status: Deployed to UAT
• Source pages: ANDDONE-ALL RELEASE NOTES.pdf pp. 291–291

References

• AN-25194
• AN_ALMGMT_V4

Original release notes excerpt

UAT Release Notes – Ally Management (AN_ALMGMT_V4)
UAT Release: Ally Management (AN.ALMGMT.V4)
Release Date: UAT APR 17,2025
Release Status: Deployed to UAT
With this version of release, Ally Payout APIS and webhooks will be delivered that are key for
Ales to be able to payout the required amounts to their sub-merchants
Features Deployed to Production Client Facing Impact
AndDone Aly Ver 1 Payouts (AN-25194) ves
Following capabilities are included into ths epic
Allys able to make payouts to thelr sub merchants using the
secure payouts api
Allis able to receive updates after subscribing to the
PAYOUT webhook module

Source: Compiled internal release notes PDF (ANDDONE-ALL RELEASE NOTES.pdf), pages 291–291.

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

• Release date: April 07, 2026
• Release status: Deployed to UAT
• Source pages: ANDDONE-ALL RELEASE NOTES.pdf pp. 288–290

Highlights

• Alles can submit payments on behalf oftheir sub merchants

References

• AN_ALMGMT_V3

Original release notes excerpt

UAT Release Notes – Ally Management (AN_ALMGMT_V3)
UAT Release: Ally Management (AN.ALMGMT.V3)
Release Date: UAT APR 07,2025
Release Status: Deployed to UAT
With this version of release, All the Ally changes required for IPFS Total pay migration will be
released to UAT enabling IPFS to perform an integration testing with AndDone environment.
Features Deployed to Production Client Facing Impact
AndDone Ally Ver1 Secure Payment APIs Changes (AN- YES
25193)
« Alles can submit payments on behalf oftheir sub merchants
For an Ally to submit @ payment, he would need an API key (
associated with Ally user) and a APP key (associated with
the sub-merchan)
This epic encompasses all the changes to be made tothe

Source: Compiled internal release notes PDF (ANDDONE-ALL RELEASE NOTES.pdf), pages 288–290.

The post UAT Release Notes – Ally Management (AN_ALMGMT_V3) 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.

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: March 18, 2026
• Release status: Deployed to UAT
• Source pages: ANDDONE-ALL RELEASE NOTES.pdf pp. 286–287

Highlights

• Ally Webhooks (AN-24831 & AN-23848) YES (Not Immediately)

References

• AN-23848
• AN-24831
• AN-25935
• AN_ALMGMT_V2

Original Release Notes Excerpt

UAT Release Notes – Ally Management (AN_ALMGMT_V2)

UAT Release: Ally Management (AN_ALMGMT.V2)

Release Date: UAT Mar 18,2025Release Status: Deployed to UAT

With this version of release, Ales shall be able to create secure payment intents, subscribe to a webhook and get list of subscribed webhooks. A new secure APIs also crested for Ales to onboard sub-merchants on to AndDone platform, Features Ally Payments, Changes to Secure Payment Intents API. YES (Not Immediately) aN-25935) Ailes shall be able to use secure payment intent API to create payment intents.

They will need to use the Private API key assigned to them Ally Webhooks (AN-24831 & AN-23848) YES (Not Immediately)

Source: Compiled internal release notes PDF (ANDDONE-ALL RELEASE NOTES.pdf), pages 286–287.

The post UAT Release Notes – Ally Management (AN_ALMGMT_V2) 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.

What’s New

The phone number field is now optional when creating or updating a vendor. This change applies consistently across both the user interface and backend APIs. Existing validation rules have been updated to allow vendor records without a phone number.

Why It Matters

You can now create and manage vendor records without requiring a phone number. This simplifies onboarding for vendors where contact numbers are unavailable or unnecessary, reducing friction in data entry.

Changes

• Parameter: phoneNumber
• Change Type: Modified (now optional)
• Affects: Vendor create and update endpoints

Allows Cancellation Of Checks In Print Queued Status

What’s New

Checks that are in a “Print Queued” state can now be canceled before they are printed. This introduces additional control over the check processing lifecycle and prevents unwanted check issuance.

Why It Matters

You can now stop checks before they are printed, reducing errors and avoiding the need for manual reversals or corrections after printing.

Omits Duplicate DBA Name On Printed Checks

What’s New

When the Merchant DBA (Doing Business As) name matches the Merchant name, the system no longer prints the DBA name on checks. This removes redundant information from printed output.

Why It Matters

You get cleaner, more readable checks without duplicate business names. This improves the presentation and avoids confusion for recipients.

Excludes Bundle Address For USPS First Class Shipping

What’s New

The system no longer includes the bundle address when USPS First Class is selected as the shipping method. This avoids requiring unnecessary fields such as phone numbers for this shipping type.

Why It Matters

You can process shipments with fewer required fields when using USPS First Class. This streamlines the workflow and reduces validation errors tied to unnecessary address data.

Suppresses Transit Status After Delivered Webhook

What’s New

If a “Delivered” webhook is received, the system stops sending or displaying subsequent “In Transit” status updates. This ensures that delivery status is not overwritten by outdated tracking events.

Why It Matters

You now see accurate and consistent delivery statuses. This prevents confusion caused by conflicting tracking updates after a package has already been marked as delivered.

Implements Secure Webhook Validation For Checkeeper

What’s New

Incoming webhooks from Checkeeper are now validated using a signature-based verification process. This ensures that only trusted webhook events are accepted by the system.

Why It Matters

You can trust that webhook events are authentic and have not been tampered with. This improves the security of your payment workflows and reduces the risk of processing malicious or invalid requests.

Release Date: Feb 26, 2026

Release Status: Deployed to PROD

This release bundle contains Outbound payments API’s

Features Deployed to UAT

Merchant Portal Enhancements

Vendor Management:

Phone number made optional in Add/Edit Vendor, implemented across UI and Backend (Secure & Open APIs)

Client Facing Impact: Yes

Check Printing and Formatting:

Allow Cancellation of Checks in Print Queued Status
Merchants can now cancel Checks that are still in Print Queued status

Do Not print Merchant DBA Name when same as Merchant Name
If Merchant DBA name matches Merchant Name, the DBA name is omittedon the printed check to avoid redundancy.

Client Facing Impact: Yes

Exclude Bundle Address for USPS First Class Shipping Methods

Bundle address is now excluded when USPS first class shipping method is selected [only shipping method for now], to avoid phone number being mandate

Client Facing Impact: Yes

Omit Transit Status if Delivered webhook is received prior

Transit status updates are now omitted when a delivered webhook is already received, preventing wrong display of status

Client Facing Impact: Yes

Secure Webhook Validation for Checkeeper

Added Signature-based webhook validation to securely verify incoming Checkeeper webhook requests

Client Facing Impact: Yes

The post PROD Release Notes – Outbound Payments (AN_OUTPAY_V8) 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.

• Release date: 2026-02-11
• Release status: Deployed to UAT
• Version: AN_OUTPAY_V8

Highlights

• Vendor Management – Phone number made optional in Add/Edit Vendor across UI and Backend (Secure & Open APIs).
• Check Printing and Formatting – Allow cancellation of checks in Print Queued status; omit Merchant DBA Name on printed check when same as Merchant Name.
• Exclude Bundle Address for USPS First Class Shipping Methods – Bundle address excluded to avoid mandatory phone number constraint.
• Omit Transit Status if Delivered webhook is received prior – Prevents incorrect status display sequence.
• Secure Webhook Validation for Checkeeper – Signature-based validation to securely verify incoming Checkeeper webhook requests.

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