What’s new

A new API service is available in Premium Finance Lite that allows a manual sync to be triggered for updating IPFS GA (General Agent) data in the system for a specific merchant. This gives operators an on-demand alternative to waiting for the regularly scheduled cron job to run.

Why it matters

You can now trigger a GA sync programmatically at any time, making it easier to recover from data discrepancies or push updates immediately after a GA change in IPFS without waiting for the next scheduled run.

Adds manual GA sync button to the Admin Portal

What’s new

A new button has been added to the PF Lite feature page in the Admin Portal, allowing admins to trigger a manual GA sync directly from the UI at any time without waiting for the regular cron job.

Why it matters

Before this change, initiating a sync required either waiting for the scheduled job or triggering the API directly. Admins can now initiate a sync on demand from the portal without any technical intervention.

Introduces automated GA sync for Premium Finance Lite

What’s new

A new scheduled API service has been introduced that runs automatically at a configured time, retrieves all GAs from IPFS, and syncs them into the system for each relevant merchant. This replaces the need for manual intervention to keep GA data current on a routine basis.

Why it matters

GA data in the system now stays automatically up to date with IPFS on a scheduled basis, reducing the risk of stale GA records being used in quote creation and other downstream flows.

Adds GA search API by name

What’s new

A new API service allows callers to search for a General Agent by their unique name. This provides a targeted lookup mechanism for GA records without needing to retrieve the full list.

Why it matters

You can now look up a specific GA by name in a single API call, making it straightforward to integrate GA selection into quote creation flows or other workflows that require identifying a GA by name.

Integrates GA search into the quote creation UI

What’s new

A dropdown search field has been added to the quote creation flow in the UI, allowing users to find and select a General Agent to associate with a new quote. The field is powered by the GA search API and supports searching by GA name.

Why it matters

Before this change, there was no UI mechanism to associate a GA with a quote at creation time. Users can now search for and add a GA directly within the quote creation workflow without leaving the page.

Adds GA support to the Draft Quote JWT API

What’s new

The existing Draft Quote API has been updated to accept a GA object in the policy request body, enabling GA details to be included when creating a draft quote. The API for fetching quote details has also been updated to return the GA in the policy object.

Why it matters

Integrations that create draft quotes via the JWT API can now include GA information as part of the initial quote creation request, and retrieve it back when fetching quote details, without requiring a separate update step.

Changes

Maps GA object to quote creation UI fields

What’s new

The GA object returned from the API is now mapped to the corresponding UI text fields in the quote creation flow, enabling both adding and displaying a GA when creating or viewing a quote.

Why it matters

GA data entered or retrieved via the API is now consistently reflected in the quote creation UI, ensuring that what is stored in the system matches what the user sees and interacts with on screen.

Includes GA details in quote generation

What’s new

The existing quote creation flow has been updated to include GA details in the generated quote. When a GA is associated with a quote, that information is now carried through to the final quote output.

Why it matters

Before this change, GA information entered during quote creation was not reflected in the generated quote. GA details are now included end-to-end, from selection through to the final quote document.

Displays GA on saved policies in search results

What’s new

When a GA is added during quote creation, it is now mapped to the resulting policy and displayed when that policy is retrieved via the saved policy search. This ensures GA association is visible throughout the policy lifecycle, not just at quote time.

Why it matters

Before this change, a GA associated with a quote was not surfaced when searching saved policies, making it difficult to identify which GA was linked to a given policy. GA information is now consistently visible at both the quote and policy level.

UAT Release – GA Support to Premium Finance Lite (AN_GASPFL_V1)

Release Date: Mar 31, 2026

Release Status: Deployed to UAT

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

Create GA Manual Sync in Existing Premium Finance Lite [AN-46447]

An API service in premium finance lite to perform manual sync for updating IPFS GA in our system for a merchant.

Client Facing: No

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

Integrate Manual Sync API in Admin Portal [AN-46462]

UI to display a button on PF lite feature page to perform a manual sync at any time without waiting for regular Cron job.

Client Facing: Yes

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

Create Auto Sync for GA in Premium Finance Lite [AN-45696]

An API service which will execute on a given time and retrieve all GAs from IPFS and sync in our system for a specific merchant.

Client Facing: No

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

Create Get API for GA with Search by Name [AN-45749]

An API service which will be able to search a GA with its unique name.

Client Facing: No

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

Integrate Get GA Details to Fetch and Search GA [AN-46419]

UI to display a dropdown search option to find GA and add it in quote creation.

Client Facing: Yes

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

Add GA for Draft Quote in JWT API [AN-45768]

Update existing draft quote to support GA in the policy request for quote creation.

Client Facing: No

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

Return GA in the Draft JWT API [AN-46116]

Update existing API to fetch quote details for GA in policy object.

Client Facing: No

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

Integrate GA Object in Policy Details [AN-46394]

UI to map GA Object with UI text field for Add and get GA in quote creation.

Client Facing: Yes

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

Generate a Quote with GA Object [AN-46888]

Update existing quote creation to support GA details in the generated quote.

Client Facing: Yes

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

Search Saved Policies Should Show GA When Added [AN-47244]

The GA added while quote creation should be mapped to Policy and should be displayed when policy is searched.

Client Facing: Yes

The post UAT Release – GA Support to Premium Finance Lite (AN_GASPFL_V1) 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-03-09
• Release status: Deployed to UAT
• Version: AN_BALPH2_V5

Highlights

• Admin Portal Integration of Underwriting Evaluations (AN-32769) – Underwriting as a step in quick onboarding/edit workflows; display summary, timeline events, application versions.
• Account holder and Balance account Updates (AN-44059) – Account summary page updated with Application data.
• Enabling Application Acceptance (AN-44008 et al.) – Emulate Apply portal; create application from Sub-merchant; perform underwriting evaluations; approve with justifications.
• Technology Backlog items (AN-45215, AN-45211) – Dynatrace logs enabled in Balance Account Transaction and Payment Batching modules.

References

• AN-32769
• AN-44059
• AN-44008
• AN-44933
• AN-44934
• AN-45195
• AN-45211

The post UAT Release Notes – Balance Platform Phase II (AN_BALPH2_V5) appeared first on AndDone.

• Release date: 2026-03-04
• Release status: Deployed to UAT
• Version: AN_PFTADN_V4

Highlights

• PFTAD | Coverage Management (Entity API) [AN-28221] – Full CRUD support for Coverage entities; manual and scheduled cron sync with Datalink Coverages.
• PFTAD | Policy Management (Entity API) [AN-28221] – Full CRUD support for policy entities; manual and scheduled sync with Datalink policy.
• PFTAD | Admin Portal – Data Sync [AN-38556] – Front-end data sync framework; UI integration with entity-based APIs (Program, Carrier, Coverage, GA, Broker Management).
• Required PFTAD swagger update for all modules – Updated OpenAPI/Swagger specs; PF4 → PFTAD renaming; standardized x-version metadata.
• [CR] Quote Config – make alias unique and required – alias in quoteConfig is now mandatory; case-insensitive uniqueness validation; MISSING_REQUIRED_FIELD and DUPLICATE_ALIAS error codes.
• [CR] CommsConfig – Make alias field required and unique – alias in communicationConfig is now mandatory; DUPLICATE_ALIAS returned on conflict.

References

• AN-28221
• AN-38556

The post UAT Release Notes – PFTAD (AN_PFTADN_V4) appeared first on AndDone.

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

Highlights

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

References

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

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

• 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_BALPH2_V4

Highlights

• Onboarding Enhancements (AN-43267, AN-43031, AN-43285, AN-42551, AN-44569, AN-43228) – Virtual Account Processor on Account Listing; multi-status application search; Adyen remediation handling; sole proprietorship restriction; merchant-application data sync.
• Alloy Underwriting Integration Updates (AN-43709, AN-44223, AN-44298, AN-44299) – Event handler for Alloy evaluation mappings; correlate completed_evaluation events; underwriting summary and events API enhancements with entity filters.
• Enabling Application Acceptance (AN-43138, AN-44007, AN-43139, AN-43135) – Assign owner, fetch entity owners, assign grantors, manage entity roles for AndDone applications.

References

• AN-43267
• AN-43031
• AN-43285
• AN-42551
• AN-44569
• AN-43228
• AN-43709
• AN-44223
• AN-44298
• AN-44299
• AN-43138
• AN-44007
• AN-43139
• AN-43135

The post UAT Release Notes – Balance Platform Phase II (AN_BALPH2_V4) 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.

• Release date: 2026-02-10
• Release status: Deployed to UAT
• Version: AN_EVTSPU_V2

Highlights

• Design changes to support bulk processing of events (AN-42017, AN-42018, AN-42019) – Data source changes; bulk settlement event publishing via event-bridge scheduler; schedule creation on incoming events.
• Processing Enhancements for downstream processing (AN-42020 et al.) – Transaction entity, event log, and status handler enhancements for Bulk OnSuccess events; Payment Link status handler updates.
• Dead Letter Queue implementation (AN-44108) – Retry mechanism for failed settlement event processing.

References

• AN-42017
• AN-42018
• AN-42019
• AN-42020
• AN-42545
• AN-42546
• AN-42547
• AN-44108

The post UAT Release Notes – Event Based Settlement Processing Upgrade (AN_EVTSPU_V2) appeared first on AndDone.