What’s New

The Admin Portal now supports underwriting as a step within merchant onboarding and merchant edit workflows. Administrators can view a full underwriting summary, a timeline of underwriting events, and all versions of a given application. It is also now possible to associate an existing application with a merchant and view underwriting results for any entity tied to that application.

Why It Matters

Before this change, underwriting data lived outside the Admin Portal, requiring context-switching between systems to assess a merchant’s status. You can now complete underwriting review entirely within the Admin Portal, with full visibility into history, decisions, and application versions in one place.

Updates Account Summary Pages With Application Data

What’s New

The account summary page for account holders and balance accounts now pulls in and displays relevant information sourced from the associated application. This keeps merchant profile data and application data aligned in a single view.

Why It Matters

Previously, account summary pages reflected only the core account data, leaving out context from the application record. You can now see a more complete picture of an account holder’s details without navigating away from the summary page.

Enables End-to-End Application Approval From the Admin Portal

What’s New

Administrators can now manage the full application approval lifecycle directly from the Admin Portal. This includes creating an application from the merchant underwriting view, running underwriting evaluations inline, reviewing an approval panel, approving applications with written justifications, and editing applications in ways that respect their current status.

Administrators can also emulate the applicant-facing portal from within the Admin Portal, making it easier to review and validate the applicant experience without switching interfaces.

Why It Matters

Before this change, approving an application required coordinating across multiple tools or views with no unified workflow. You can now take a merchant from application creation through underwriting evaluation to final approval — with justification on record — entirely within a single interface.

Release Date: Mar 26th, 2026

Release Status: Deployed to Production

This release bundle primarily consists of Alloy underwriting Integration on Admin Portal Onboarding Enhancements supporting Account holder and balance account updates and Enabling Application Approval on AndDone platform. This also includes some UX enhancements to admin portal and bug-fixes as identified during the development cycle.

Admin Portal Integration of Underwriting Evaluations

(AN-32769)

• Underwriting as a step in quick onboarding or edit merchant workflows
• Ability to display Underwriting summary information
• Ability to display Underwriting timeline events
• Ability to associate an application to an existing merchant
• Display underwriting results for an entity associated with an application

Client facing impact: No

Account holder and Balance account Updates

(AN-44059)

• Update account summary page with information from Application

Client facing impact: No

Enabling Application Acceptance

(AN-44008, AN-44933, AN-44934, AN-45444, AN-45445, AN-45195, AN-45196, AN-45739)

• Ability to emulate Apply portal from Admin Portal 
• Ability to create application from Sub-merchant Underwriting view 
• Perform underwriting evaluations from Underwriting view 
• Application approval panel and ability to approve 
  applications 
• Approve application with Justifications 
• Edit application with status based behavior
  

Technology Backlog items

(AN-45215, AN-45211)

• Enablement of dynatrace logs in Balance Account Transaction module
• Enablement of dynatrace logs onto Transaction Payment Batching module

Client facing impact: No

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

What’s new

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

Why it matters

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

Converts Ally Monthly Profitability Report to merchant-level summary

What’s new

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

Why it matters

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

Exposes secure Payment Intent Timeline API to Ally users

What’s new

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

Why it matters

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

Introduces Ally Portal notification APIs for listing and retrieving notifications

What’s new

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

Why it matters

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

Adds notification status management APIs for Ally Portal

What’s new

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

Why it matters

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

Adds API to list all template variables for Ally notification templates

What’s new

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

Why it matters

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

Introduces distribution list management APIs for Ally Portal notifications

What’s new

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

Why it matters

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

Adds template update and creation APIs for Ally Portal notifications

What’s new

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

Why it matters

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

Extends secure merchant onboarding API with optional shopper statement field

What’s new

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

Changes

Why it matters

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

Aligns Ally sub-merchant feature inheritance with Ally feature configuration

What’s new

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

Why it matters

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

Migrates Domain project monitoring from Lumigo to Dynatrace

What’s new

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

Why it matters

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

Migrates Infrastructure project monitoring from Lumigo to Dynatrace

What’s new

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

Why it matters

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

Continues Transaction project monitoring migration to Dynatrace (Part 3)

What’s new

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

Why it matters

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

Completes Transaction project monitoring migration to Dynatrace (Part 5)

What’s new

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

Why it matters

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

Migrates Invoice project Lambdas to ARM64 (Graviton) processor

What’s new

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

Why it matters

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

Fixes repeated NACHA notification emails after scheduler run

What’s new

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

Why it matters

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

Fixes notifications not triggering for transaction events on QAT

What’s new

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

Why it matters

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

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

What’s new

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

Why it matters

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

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

Summary

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

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

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

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

Ally Portal | Payments Section (AN-37771)

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

Client Facing: Yes

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

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

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

Client Facing: Yes

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

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

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

Client Facing: No

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

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

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

Client Facing: No

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

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

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

Client Facing: No

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

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

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

Client Facing: No

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

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

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

Client Facing: No

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

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

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

Client Facing: No

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

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

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

Client Facing: Yes

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

Ally Submerchant Feature Inheritance (AN-42726)

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

Client Facing: Yes

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

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

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

Client Facing: No

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

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

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

Client Facing: No

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

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

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

Client Facing: No

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

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

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

Client Facing: No

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

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

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

Client Facing: No

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

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

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

Client Facing: No

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

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

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

Client Facing: No

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

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

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

Client Facing: Yes

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

What’s New

A new set of API services is now available for managing broker records within the system. Developers can sync, create, update, delete, and retrieve broker details through these endpoints. This forms the foundational data layer for broker management within the platform.

Why it Matters

You can now programmatically manage the full lifecycle of a broker record without manual intervention or workarounds. Teams building broker onboarding or management flows have a complete, consistent API surface to integrate against.

Introduces Admin UI Controls for Merchant IPFS Configuration and Permissions

What’s New

Admins can now configure merchant feature access and permissions directly from the onboarding page in the admin portal. This includes the ability to set up IPFS (Insurance Premium Finance Settings) configuration for a merchant through the UI, without requiring a backend intervention.

Why it Matters

Before this change, configuring merchant-level IPFS settings required non-UI intervention. Admins can now complete this configuration entirely from the onboarding flow, reducing setup time and dependency on engineering teams.

Adds Full CRUD Support for Communication Config Entities via API

What’s New

A new set of API services is now available for managing communication configuration records. Developers can create, update, delete, and retrieve communication details through these endpoints, enabling programmatic control over how communication settings are defined within the system.

Why it Matters

You can now manage communication configurations as first-class entities via API, making it straightforward to automate setup or integrate communication management into existing workflows.

Adds Full CRUD Support for GA Entities via API

What’s New

A new set of API services is now available for managing General Agent (GA) records. Developers can create, update, delete, and retrieve GA details through these endpoints, completing the core entity API layer for GA management.

Why it Matters

You can now manage GA records programmatically with the same API patterns used across other entities in the system, enabling consistent integration and automation across the platform.

Extends GET Carriers Endpoint With Additional Filter Parameters

What’s New

The GET multiple Carriers API now accepts additional filter parameters, allowing callers to narrow results by columns that were not previously searchable. This expands the query flexibility of the endpoint without breaking existing integrations.

Why it Matters

You can now search and filter carrier records more precisely in a single API call, reducing the need for client-side filtering of large result sets.

Standardizes Error Response Format Across Agent, Insured, Program, and Quote Config APIs

What’s New

Validation and exception handling across the Agent, Insured, Program, and QuoteConfig APIs have been updated to produce a consistent, standardized error response structure. Previously, error formats varied across these services, making it difficult to handle errors uniformly on the client side.

Why it Matters

Before this change, integrations had to account for inconsistent error shapes depending on which API returned the error. Error handling logic can now be written once and applied consistently across all four API surfaces, improving reliability and reducing integration complexity.

Verifies System Performance for Create and Get Insured on New Infrastructure

What’s New

Performance testing has been completed for the Create Insured and Get Insured endpoints running on the new PFTAD infrastructure. This validates that the system meets performance expectations under load before broader rollout.

Why it Matters

Teams integrating with these endpoints can proceed with confidence that the underlying infrastructure has been verified for performance, reducing the risk of unexpected latency or degradation in production.

Consolidates Default Program Handling into Program Sync and Removes Dedicated Endpoint

What’s New

The default program is now returned directly in the response to manual and cron job sync requests from IPFS, eliminating the need for a separate dedicated endpoint. The standalone default program API endpoint has been decommissioned as part of this change.

Why it Matters

Before this change, retrieving the default program required a separate API call to a dedicated endpoint. The default program is now included inline with sync responses, simplifying integration flows. Any existing calls to the standalone default program endpoint will need to be removed.

Upgrade

1. Remove any calls in your integration to the dedicated default program endpoint.
2. Update your sync response handler to read the default program from the IPFS sync response payload instead.

Migrates Monitoring From Lumigo to Dynatrace for the Premium Finance ECS Project

What’s New

The Transaction project within the Premium Finance ECS infrastructure has been migrated from Lumigo to Dynatrace for observability and monitoring. This is an internal infrastructure change with no impact on API behavior or response contracts.

Why it Matters

Operational monitoring and alerting for the Transaction project now runs through Dynatrace. Teams relying on Lumigo dashboards or alerts for this project should update their observability workflows accordingly.

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

Production Release Notes — PFTAD (AN_PFTADN_V3)Release Date: UAT Feb 9, 2026Release Status: Deployed to Prod

This release bundle primarily consists of premium finance development for the broker communication and GA along with merchant features and permissions.

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

PFTAD | Broker Management (Entity API) [AN-26446]

All API service to sync, create, update, delete, and retrieve details of the broker within the system.

Client Facing: No

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

PFTAD | Admin Portal – Merchant Features and Permissions [AN-30054]

Admin feature access and permission setting from UI for setting up merchant IPFS configuration from onboarding page.

Client Facing: Yes

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

PFTAD | Communication Config Management (Entity API) [AN-29019]

All API service to create, update, delete, and retrieve details of the Communication within the system.

Client Facing: Yes

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

PFTAD | GA Management (Entity API) [AN-28206]

All API service to create, update, delete, and retrieve details of the GA within the system.

Client Facing: Yes

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

[CR] Additional filter params to GET multiple [AN-40597]

Additional filter parameters added to the GET multiple Carriers API, so users can search on additional columns.

Client Facing: No

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

Standardize Error Code Format for Agent, Insured, Program, and QuoteConfig APIs [AN-39853]

Update all validation and exception handling layers to produce standardized error responses to improve debugging, integration consistency, and client-side error handling.

Client Facing: No

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

Performance Testing for Create and Get Insured [AN-38225]

Verify system performance on new infrastructure of PFTAD for create and get details of insured.

Client Facing: No

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

[CR] – Incorporate isDefault into Program sync and remove dedicated endpoint [AN-42014]

IPFS will send the default program in response to requests. Manual and cron job request.Decommission of default program API.

Client Facing: No

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

Migrate Monitoring from Lumigo to Dynatrace – PremiumFinance ECS Project [AN-38797]

Migrate the Transaction project from Lumigo to Dynatrace.

Client Facing: No

The post Production Release Notes — PFTAD (AN_PFTADN_V3) appeared first on AndDone.

What’s new

The Admin Portal now surfaces underwriting data pulled from Alloy. Admins can retrieve all applications associated with a merchant, view underwriting results summaries, browse underwriting summary events filtered by year or across all entities, and access the full set of underwriting results for any given entity. These capabilities are backed by four new API integrations that fetch and display this data within the portal.

Why it matters

Before this change, underwriting evaluation data was not accessible through the Admin Portal. Admins can now review the complete underwriting picture for a merchant — including results, summaries, and event history — without requiring direct database access or separate tooling.

Adds foundational email templates for the merchant-facing Apply Portal

What’s new

Two new email templates have been created to support the merchant-facing Apply Portal: one for the Initial Application notification and one for OTP (one-time password) authentication. These templates form the communication foundation for the merchant application journey.

Why it matters

These templates are a prerequisite for delivering a complete, communicative application experience to merchants. With them in place, applicants will receive properly formatted notifications at key steps in the onboarding and authentication flow.

Integrates Alloy underwriting services into the platform

What’s new

The platform now integrates with Alloy’s underwriting services across the full evaluation lifecycle. This includes an inbound webhook handler for Alloy events, support for triggering Alloy journeys for Sole Proprietors and Individuals, processing of journey application update events, financial information mapping for underwriting scans, and persistence of underwritten applications based on event data. The integration also fetches and persists underwriting results on completed_evaluation events, and stores or updates underwriting summary and summary events per entity.

Why it matters

You can now automate the underwriting evaluation pipeline end-to-end via Alloy. Application data flows from trigger through evaluation to persisted results without manual steps, and the platform maintains a durable record of all underwriting states and outcomes for each entity.

Miscellaneous tech backlog and infrastructure improvements

What’s new

This release includes several internal improvements across the platform. Account holder created and updated events are now persisted before processing to improve reliability. The payout schedule card layout has been updated. Logging has been migrated from Lumigo to Dynatrace across the Onboarding, Transactions, and Logs modules. Edge Functions have been implemented on the ALB-based ECS architecture.

Why it matters

These changes improve the resilience, observability, and performance of core platform infrastructure. Teams relying on Lumigo for logging visibility on the Onboarding, Transactions, or Logs modules should transition their monitoring to Dynatrace. No changes to external API contracts are introduced.

Production Release Notes – Balance Platform Phase II (AN_BALPH2_V3)

Release Date: Feb 9, 2026

Release Status: Deployed to Prod

This release bundle primarily consists of Alloy underwriting Integration for Journey, evaluations and results. This also includes enhancements to fetch, persist and display application versions, underwriting summary, underwriting summary events and underwriting results, and Miscellaneous Tech Backlog and hotfix items. This also includes bug-fixes as identified during the development cycle.

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

Admin Portal Integration of Underwriting Evaluations (AN-41299, AN-41470, AN-42113, AN-42114)

• Ability to fetch all applications associated with a merchant
• Ability to fetch underwriting results summary events for all entities by year
• Ability to fetch underwriting summary events for all entities
• Ability to fetch all underwriting results for an entity

Client Facing: No

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

Merchant Facing Apply Portal Foundational Items (AN-41506, AN-41507)

• Email template creation for Initial Application notification
• Email template creation for OTP authentication

Client Facing: No

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

Integration with Alloy Underwriting Services (AN-38810, AN-39427, AN-40057, AN-41930, AN-42841, AN-42844, AN-42845, AN-42847)

• Alloy Handler for processing inbound webhooks
• Support Alloy journey trigger for Sole Prop and Individuals
• Process Journey application updated events
• Add Financial information mapping for underwriting scans
• Persist Underwritten Applications Based on Event Data
• Fetch & Persist Underwriting Results on completed_evaluation Events
• Persist Underwriting Summary Events for an entity
• Persist or update Underwriting Summary for an entity

Client Facing: No

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

Tech Backlog & Miscellaneous (AN-41077, AN-42447, AN-41770, AN-38791, AN-38787, AN-38441)

• Account holder created updated events to be persisted before processing
• Updated payout schedule card layout
• Updated logging from Lumigo to Dynatrace on Onboarding, Transactions and Logs modules
• Implementation of Edge Functions on ALB based ECS Architecture

Client Facing: No

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

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

Highlights

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

References

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

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