• 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: November 25, 2025

Status: Deployed to UAT

Overview

This release expands outbound payment capabilities in AndDone with improvements across vendor management, payment remittance, and check controls. The updates focus on giving insurance teams more flexibility, clearer validation, and better visibility when sending outbound payments.

What’s New

1. Optional DBA Field in Vendor Profiles

What it does:

The DBA (Doing Business As) field is now optional when creating or editing a vendor profile.

How it works:

• Users can save vendor profiles without entering a DBA name.
  
• Vendor creation continues even when a business operates under a single legal name.
  

Why it matters:

Speeds up vendor setup and removes unnecessary blockers during outbound payment preparation.

Customer-facing: Yes

2. Multiple Amount Fields in Payment Remittance

What it does:

Merchants can add multiple amount fields within payment remittance and choose which amount is applied to the check total.

How it works:

• Multiple amount columns can be entered in the remittance table.
  
• Users select the desired amount using the “$” icon.
  
• Only the selected amount is summed and reflected in Check Details.
  

Why it matters:

Supports more complex remittance scenarios while keeping check totals accurate.

Customer-facing: Yes

3. Validation for Check Amounts Over $1,000,000

What it does:

The system now blocks remittance submissions when the total check amount exceeds $1,000,000.

How it works:

• During save or submit, the system evaluates the summed remittance total.
  
• If the amount exceeds $1,000,000, an error message appears and the action is blocked.
  

Why it matters:

Prevents oversized check payments and reduces downstream processing issues.

Customer-facing: Yes

4. Bank Account Selection on Check Details Page

What it does:

Merchants can select which bank account is used before creating a check.

How it works:

• A dropdown lists all merchant-linked bank accounts with check capability.
  
• The default account appears at the top with a star indicator.
  
• If no selection is made, the default account is used automatically.
  

Why it matters:

Gives teams more control over funding sources for outbound payments.

Customer-facing: Yes

5. Vendor Listing Pagination

What it does:

Vendor listings now support pagination instead of a fixed date filter.

How it works:

• Pagination options include 10, 25, or 50 records per page.
  
• The automatic “Last 7 Days” filter has been removed.
  
• All available vendor records are visible by default.
  

Why it matters:

Improves navigation and visibility for teams managing larger vendor lists.

Customer-facing: Yes

Admin Portal Updates

Admin Notifications for Vendor Edits

What it does:

Administrators receive notifications when merchants create or update vendor records.

Why it matters:

Improves oversight and awareness of vendor changes across the platform.

Customer-facing: No

Payment Reference Visibility in Admin Portal

What it does:

Admins can view payment reference details for each outbound payment to help trace check transactions.

Why it matters:

Supports investigation and tracking of outbound payment activity.

Customer-facing: No

Key Takeaway

This release strengthens outbound payment workflows by improving vendor setup, remittance accuracy, and check-level controls. With clearer validation and expanded visibility, insurance teams gain more confidence and flexibility when managing outbound funds.

The post Outbound Payments – Enhanced Vendor Management & Check Controls appeared first on AndDone.

Release Date: August 13, 2025

Status: Live

Overview

This release adds new ways to search, pay, and track AMS360 invoices directly through AndDone. Customers can now look up invoices by number, and merchants get better tools to filter and identify AMS360 transactions.

What’s New

1. Search Invoices by Invoice Number

What it does: Customers can now pay specific AMS360 invoices by entering the invoice number directly on the payment page.

How it works:

• Customers choose between standard Anytime Payments or the new Invoice Lookup option
• Enter a valid AMS360 invoice number to instantly pull up invoice details (customer info, amount due, dates)
• If the invoice number is invalid, a helpful error message appears

Why it matters: Faster payments with fewer errors. Customers get exactly what they need without extra steps.

Customer-facing: Yes

2. Automatic Invoice Payment Limit Checks

What it does: The system now prevents customers from paying invoices that exceed your account’s payment limits for ACH or card transactions.

How it works:

• AndDone automatically checks invoice totals against your configured limits
• If an invoice exceeds the limit, customers see a clear message explaining why the payment can’t be processed that way

Why it matters: Keeps all payments within compliance and prevents failed transactions.

Customer-facing: Yes

3. Complete AMS360 Invoice Payments

What it does: Customers can now complete payments for validated AMS360 invoices with an automatic receipt.

How it works:

• After invoice validation, customers only see payment methods that work for their invoice amount
• Once payment is successful, a receipt is automatically generated

Why it matters: Streamlined checkout with built-in safeguards and instant confirmation.

Customer-facing: Yes

4. View AMS360 Transactions in Payment Listings

What it does: AMS360 payments are now clearly marked in your payment dashboard for easier tracking.

How it works:

• AMS360 transactions show a Vertafore logo in the “Ref Value” column on the payment listing page
• Payment detail pages display “AMS360” under “Initiated From”
• Customer and merchant receipts still show “Anytime Payments” for consistency

Why it matters: Quickly identify where payments originated without changing the customer experience.

Customer-facing: Yes

5. Filter Payments by Source

What it does: Merchants can now filter payment listings by payment source: Anytime Payments, AndDone.js, or AMS360.

How it works:

• New filter options appear based on your active Feature Access settings
• Only see filters for features you’re currently using
• Historical AMS360 transactions remain visible even if the feature is later disabled, but the filter option will be hidden

Why it matters: Better control and visibility into payment data. Easier to analyze transactions by source.

Customer-facing: Yes

The post AMS360 Enhanced Invoice Payments & Transaction Management  appeared first on AndDone.

1. Define PCI Scope and Ownership Across Systems and Vendors

PCI compliance for your insurance agency starts with clearly defining scope and ownership. Finance teams must understand every system, workflow, and vendor involved in accepting, processing, refunding, or adjusting card payments, especially when payment activity extends beyond internal systems.

Finance leaders should inventory every touchpoint where card data could appear, including:

• Customer-facing payment portals and hosted checkout experiences.
• Embedded payment links used in emails, invoices, or AMS workflows.
• Internal systems that process, reconcile, refund, or adjust transactions.
• Reprocessed or corrected payments handled outside the original workflow.
• Third-party vendors involved in payment acceptance, processing, tokenization, refunds, chargebacks, or reporting.

Just as important as defining ownership, PCI compliance in insurance depends on documented internal accountability and clearly outlined third-party vendor compliance responsibilities. While technical controls may live with IT teams or vendors, finance remains responsible for oversight.

Finance leaders should document:

• Who owns PCI oversight internally, including validation of scope, controls, and ongoing compliance.
• Which vendors are responsible for PCI controls related to payment acceptance, processing, and tokenization.
• How PCI evidence is collected, reviewed, and stored for audits.
• Where escalation occurs when compliance questions or control gaps arise.

2. Verify How Card Data Is Handled and Stored

Understanding how card data is handled is essential for limiting compliance burden.

Key areas to review include:

• Where card data is captured.
• Whether tokenization occurs immediately.
• Whether any system stores raw card data.
• How long payment data is retained.
• How data is removed or invalidated.

Platforms that rely on tokenization and limit data exposure help finance teams reduce audit scope while maintaining reporting visibility. Less exposure means fewer controls to manage and fewer questions to answer later.

Finance teams should confirm these controls are applied consistently across collections, refunds, and payment adjustments, not only initial transactions.

Look for platforms such as AndDone that tokenize payment data at capture and avoid storing raw card information to reduce audit scope and limit risk.

3. Restrict and Review Access to Payment

Access control is both compliance and financial security.

Finance teams should regularly review:

• Who can view payment details.
• Who can initiate refunds or adjustments.
• Who can export transaction data.
• How role changes are logged and approved.

Role-based permissions and access logs protect against internal risk and support clean audit trails in platforms like the AndDone Portal.

4. Validate Daily Reconciliation and Audit Trails

Reconciliation is where compliance becomes operational.

Strong payment workflows support:

• Transaction-level detail.
• Time-stamped audit logs.
• Clear linkage between payments, refunds, and accounting entries.
• Visibility into paid, pending, failed, and reversed transactions.

Manual reconciliation increases compliance risk. Finance teams benefit from systems that support daily reconciliation.

When payment records are tied to policies and customers with time-stamped logs, reconciliation becomes faster and more accurate. 

5. Make Exceptions Easy to See and Prove

Refunds, chargebacks, and adjustments are part of every payment operation. But when they aren’t documented or visible, they become compliance risks.

Finance teams should ensure:

• All exceptions are tracked with complete transaction history.
• Refunds follow standardized and documented workflows.
• Chargebacks remain visible in reporting.
• Exceptions do not bypass approval or logging controls.

Auditors focus on the moments when processes break. That’s why visibility matters.

Exception workflows should stay connected to the original transaction and remain visible to the full team. This makes it easier to demonstrate control, even when workflows don’t follow the standard path.

6. Confirm Third-Party and Vendor PCI Compliance

Third-party vendors are part of your compliance footprint. As industry coverage regularly highlights, payment complexity in insurance often increases when responsibility for data handling and reporting is spread across multiple platforms and partners. Finance leaders should verify each vendor’s PCI status and document third-party service provider responsibilities across data handling, reporting, and audit support.

Key areas to confirm include:

• Each vendor’s current PCI certification and scope.
• Which party captures, processes, tokenizes, or stores card data.
• How vendors support audits, including access to evidence and documentation.
• Where responsibility shifts between internal teams and external partners.

When vendors manage payment data correctly, finance teams stay in control without taking on extra compliance work. The right platform provides visibility, reporting, and audit support without adding PCI scope to your internal systems. 

The right partner keeps finance in control without adding technical PCI risk. In this short video, Chase Courtney from AndDone shares how their team helps reduce audit complexity by managing tokenization, routing, and reconciliation in one system.

7. Maintain PCI Evidence and Audit Readiness

Audit readiness depends on evidence that reflects how your business actually operates.

Finance teams should centralize:

• PCI policies and procedures.
• Access logs and activity records.
• Transaction and reconciliation reports.
• Vendor compliance documentation.

Evidence should remain current and aligned with live workflows, because faulty or outdated records can directly lead to compliance problems and audit obstacles. When documentation matches real operating conditions, audits move faster. 

8. Schedule Ongoing PCI Reviews for the Year

PCI compliance in your insurance agency must remain current as systems, vendors, and workflows change.

Finance leaders should:

• Align PCI reviews with monthly close cycles.
• Reassess PCI scope whenever payment systems, vendors, or workflows change.
• Review vendor compliance on a regular cadence.
• Update documentation proactively as processes evolve.

Routine reviews prevent compliance drift and reduce last-minute remediation. Keeping PCI oversight tied to financial operations supports consistent audit readiness throughout the year.

The post The CFO’s Compliance Checklist: Key Insurance Requirements and Where PCI Fits appeared first on AndDone.

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.

What Is Insurance Payment Processing?

Insurance payment processing includes the systems used to collect, route, track, and reconcile premium payments. It goes beyond simply accepting a payment. It covers everything from how funds are submitted to how they’re matched and confirmed.

A complete payment process answers several essential questions:

• How does the customer submit payment?
• Where do funds go after submission?
• How is the payment matched to the correct policy?
• When do teams receive confirmation?

Insurance payment processing includes:

• Payment methods, such as ACH and credit cards.
• Fund movement through banking or card networks.
• Payment matching tied to the correct customer and policy.
• Payment status visibility, including paid, pending, or failed.
• Accurate records for service, finance, and reporting.

Because insurance payments often involve binding deadlines, installments, and premium financing, this process carries more complexity than standard ecommerce transactions.

Why Insurance Payment Processing Matters for Service Teams and Owners

Payment processing affects every team in an insurance operation. Friction usually appears first in service interactions, then creates cash flow gaps and operational strain across the business.

Impact on Service Teams

Clear payment processes shape the daily workload for service teams.

When payment handling works well:

• Fewer steps make it easier to send payment links quickly.
• Clear confirmation reduces customer back and forth.
• Visible payment status prevents unnecessary follow ups.
• Faster payments help policies move forward without last minute pressure.

When payment status remains unclear, service teams spend time tracking, checking, and explaining instead of supporting customers.

Impact on Owners and Leadership

For business owners, payment processing influences both stability and reputation.

Reliable payment operations support:

• Better visibility into cash flow.
• Lower operational strain on staff.
• Consistent customer experiences that reflect professionalism.
• Modern payment options that meet customer expectations without disrupting familiar processes.

Delayed payments reduce visibility into cash flow, manual steps increase strain on staff, and inconsistent experiences can erode trust over time. As insurance operations become more data-driven and interconnected, operational efficiency plays a growing role in sustaining performance across billing, servicing, and financial oversight.

How Insurance Payment Processing Works

While specific tools may vary, insurance payment processing follows a predictable flow. Understanding each step helps teams identify where delays and confusion often begin.

Payment processing often operates behind the scenes, but it serves as the connective layer between payment collection, premium finance, and accounting. This foundational layer helps manage fund availability and ensures money moves in a way that supports both current operations and future growth.

What Slows Insurance Payments Down

Even small gaps in the payment process can create friction. These issues often appear repeatedly across service and finance teams.

Why do payments get delayed or returned?

Payment delays often stem from incorrect customer information, bank verification holds, or manual review that slows settlement. ACH returns from incorrect account details are one of the most common issues across the industry and frequently require additional follow up before funds can be posted correctly.

What happens when systems do not connect?

When systems don’t connect, teams face duplicate work and inconsistent updates. Disconnected tools lead to duplicate data entry, missed updates between service and finance, and unclear ownership of follow ups. Approaches that balance automation with human oversight help reduce these gaps by keeping processes aligned and communication clear.

Why do customers struggle to complete payments?

Customer friction often comes from unclear or complex steps. Too many screens, confusing instructions, and the lack of immediate confirmation can cause customers to assume something went wrong. This uncertainty increases inbound calls and slows payment completion.

How Modern Payment Platforms Support Insurance Payment Processing

Modern payment platforms designed for insurance focus on supporting existing processes while reducing manual effort.

With the right platform in place, teams can:

• Centralize payment collection.
• View payment status without switching tools.
• Reduce manual follow-ups tied to unclear or delayed payments.
• Provide service teams with intuitive tools.
• Give owners clearer visibility into payment activity.

Coverage from Digital Insurance highlights how insurance specific technology supports modernization without disrupting established operations.

Why Insurance Payment Processing Is Worth Getting Right

Insurance payment processing shapes service speed, staff workload, and customer confidence, and broader industry shifts toward technology that streamlines core operations reinforce why clarity and efficiency in payment workflows matter.

When payments move clearly and predictably:

• Teams stay focused on customer needs.
• Leadership gains stronger insight into cash flow.
• Customers feel supported throughout the process.

The right setup supports familiar processes while reducing friction across the business.

The post What is Insurance Payment Processing and Why Does it Matter? appeared first on AndDone.

• Release date: March 27, 2026
• Release status: Deployed to UAT
• Source pages: ANDDONE-ALL RELEASE NOTES.pdf pp. 330–331

Highlights

• collection mode (AN-26017)
• settlement reports

References

• AN-26017
• AN_REPRED_V2

Original Release Notes Excerpt

UAT Release Notes – Reports Changes (AN_REPRED_V2)

UAT Release: Reports Changes (AN_REPRED.V2)

Release Date: UAT Mar 27, 2025

Release Status: Deployed to UAT

With this version of release, Sub-merchants will have an ability to include or exclude some transactions from the authorization report and settlement reports. Additionally swash buckle integration and few miscellaneous items are included. Features Deployed to Production Client Facing Impact Report settings (feature) & Reporting changes based on YES collection mode (AN-26017)

This feature enables sub-merchants to be able to include or exclude certain type of transactions from the following reports « settlement reports

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

The post UAT Release Notes – Reports Changes (AN_REPRED_V2) 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

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: 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.