What’s New

The account listing view now surfaces the virtual account processor associated with each account. This gives administrators and internal users visibility into which payment processor backs a given virtual account directly from the listing, without needing to open individual account records.

Why It Matters

You can now identify the virtual account processor for any account at a glance from the listing page, reducing the need to drill into individual records during account review or support workflows.

Adds Multi-Status Filtering to the Applications Search API

What’s New

The Applications Search API now accepts multiple status values as filter parameters in a single request. Previously, queries could only filter by one status at a time, requiring multiple round trips to retrieve applications across different states.

Why It Matters

You can now retrieve applications in multiple statuses — such as pending and under review — in a single API call, simplifying dashboard queries, reporting logic, and any workflow that needs to operate across application lifecycle stages simultaneously.

Changes

Parameter: status filter on GET /applications

Change type: Modified — now accepts multiple values (previously limited to a single status value per request)

Handles Remediation Actions Triggered by Payment Processor Events

What’s New

The platform now listens for and processes remediation-related events from the payment processor and automatically triggers the corresponding remediation actions on the affected accounts or applications. This closes a gap where processor-side compliance or verification events had no automated handler on the platform side.

Why It Matters

Before this change, remediation actions flagged by the payment processor required manual intervention to apply on the platform. The platform now responds to these events automatically, reducing operational lag and the risk of accounts remaining in an unresolved remediation state.

Enforces a Single Individual Restriction for Sole Proprietorship and Individual Organization Subtypes

What’s New

When creating or updating an application for an organization with a subtype of Sole Proprietorship or Individual, the platform now enforces that only a single individual can be associated with that organization. Attempts to associate more than one individual with these subtypes are rejected with a validation error.

Why It Matters

Before this change, it was possible to associate multiple individuals with organization types that are legally defined as single-person entities, leading to data inconsistencies. You can now rely on the API to enforce this structural constraint automatically rather than managing it in application-layer validation.

Synchronizes Merchant Profile Data With Application Data

What’s New

Merchant profile records are now kept in sync with the data held in their associated application. When application data is updated — such as business details or contact information — those changes are reflected on the merchant record automatically, eliminating drift between the two data sources.

Why It Matters

Previously, merchant and application records could fall out of sync after an application update, requiring manual reconciliation. You can now treat the application as the authoritative source of merchant data and trust that the merchant record reflects the latest state automatically.

Fixes Balance Account Resolution Failures for Test Environments

What’s New

An issue that caused “balance account not found” errors in test Adyen environments has been resolved. The platform now correctly resolves balance accounts in test configurations, allowing end-to-end testing of balance account flows without encountering spurious lookup failures.

Why It Matters

Before this fix, balance account operations in test environments would intermittently fail with a not-found error even when the account existed, blocking integration testing and QA workflows. Test environment balance account flows now resolve reliably.

Adds Event Handling for Underwriting Evaluation Mappings

What’s New

The platform now includes an event handler that listens for underwriting evaluation events from the external underwriting service and maps them to the corresponding internal application states. This creates a real-time bridge between the underwriting service’s event stream and the platform’s application lifecycle.

Why It Matters

Before this change, underwriting evaluation outcomes were not automatically reflected in application state — status updates required polling or manual intervention. You can now rely on event-driven updates to keep application state current as underwriting evaluations complete.

Correlates Completed Evaluation Events With Application Artifacts

What’s New

When an underwriting evaluation completes, the platform now automatically correlates the resulting evaluation record with the relevant application artifacts — such as documents and submitted data — already on file. This linkage makes it possible to trace which application inputs contributed to a given underwriting outcome.

Why It Matters

You can now retrieve a completed evaluation alongside its associated application artifacts in a unified view, rather than manually cross-referencing separate records to reconstruct the full picture of an underwriting decision.

Adds Entity Filtering to the Underwriting Summary API

What’s New

The Underwriting Summary API now supports filtering by entity, allowing callers to retrieve underwriting summaries scoped to a specific legal entity within an application. Previously, the API returned underwriting data at the application level only, with no way to narrow results to a particular entity.

Why It Matters

You can now query underwriting summaries for a specific entity — such as a business owner or subsidiary — without retrieving and filtering the full application-level response in your own code.

Changes

Parameter: entity_id filter on the Underwriting Summary endpoint

Change type: Added — filters summary results to the specified entity

Adds Entity Filtering to the Underwriting Summary Events API

What’s New

The Underwriting Summary Events API now accepts an entity filter, enabling callers to retrieve the underwriting event history for a specific entity within an application. This mirrors the entity filtering capability added to the Underwriting Summary API in this release.

Why It Matters

You can now fetch the underwriting event timeline for a single entity directly from the API, making it easier to build audit views or investigate underwriting activity for a specific person or organization tied to an application.

Changes

Parameter: entity_id filter on the Underwriting Summary Events endpoint

Change type: Added — filters event results to the specified entity

Adds Owner, Grantor, and Role Assignment Management for Application Entities

What’s New

A new set of capabilities supports managing legal entity relationships within an application. Administrators can now assign an owner to a legal entity, retrieve all entity owners for a given application, assign grantors across all entities in an application, and manage role assignments for individual entities. Together, these operations cover the full lifecycle of entity relationship management needed to prepare an application for approval.

Why It Matters

Before this change, there was no supported way to programmatically assign or retrieve ownership and role structures for entities within an application, blocking the application acceptance workflow. You can now fully configure entity roles and ownership through the API as part of building an end-to-end application submission and approval flow.

Changes

The following endpoints are newly added to support entity relationship management on applications:

POST /applications/{id}/entities/{entityId}/owner — Added. Assigns an owner to a specific legal entity.

GET /applications/{id}/entity-owners — Added. Returns all entity owners associated with the application.

POST /applications/{id}/grantors — Added. Assigns grantors to all entities within the application.

PUT /applications/{id}/entities/{entityId}/roles — Added. Sets role assignments for a specific entity.

Release Date: Feb 26th, 2026

Release Status: Deployed to PROD

This release bundle primarily consists of Alloy underwriting Integration updates, Onboarding Enhancements and Enabling Application Acceptance on AndDone platform. This also includes some UX enhancements to admin portal and bug-fixes as identified during the development cycle.

Onboarding Enhancements

(AN-43267, AN-43031, AN-43285, AN-42551, AN-44569,AN-43228)

Virtual Account Processor on Account Listing
Search Applications API supporting multiple status filters
Handle Remediations actions from Adyen events
Restrict single Individual for Organization of subtypes “Sole Proprietorship” and “Individual”
Synchronize merchant data with Application data
Addressed Balance account not found issue for Test Adyen

Client Facing Impact: No

Alloy Underwriting Integration Updates

(AN-43709, AN-44223, AN-44298, AN-44299)

Event handler for Alloy evaluation event mappings
Correlate completed_evaluation events with application artifacts
Underwriting summary API enhancements with entity filters
Underwriting summary Events API enhancements withentity filters

Client Facing Impact: No

Enabling Application Acceptance

(AN-43138, AN-44007, AN-43139, AN-43135 )

Assign owner to a legal entity of an Application
Fetch all entity owners for an Application
Assign grantors to all entities of an AndDone application
Manage entity roles and role assignments for an AndDone Application

Client Facing Impact: No

The post PROD 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_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.