• 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 phone number field is now optional when creating or updating a vendor. This change applies consistently across both the user interface and backend APIs. Existing validation rules have been updated to allow vendor records without a phone number.

Why It Matters

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

Changes

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

Allows Cancellation Of Checks In Print Queued Status

What’s New

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

Why It Matters

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

Omits Duplicate DBA Name On Printed Checks

What’s New

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

Why It Matters

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

Excludes Bundle Address For USPS First Class Shipping

What’s New

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

Why It Matters

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

Suppresses Transit Status After Delivered Webhook

What’s New

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

Why It Matters

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

Implements Secure Webhook Validation For Checkeeper

What’s New

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

Why It Matters

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

Release Date: Feb 26, 2026

Release Status: Deployed to PROD

This release bundle contains Outbound payments API’s

Features Deployed to UAT

Merchant Portal Enhancements

Vendor Management:

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

Client Facing Impact: Yes

Check Printing and Formatting:

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

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

Client Facing Impact: Yes

Exclude Bundle Address for USPS First Class Shipping Methods

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

Client Facing Impact: Yes

Omit Transit Status if Delivered webhook is received prior

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

Client Facing Impact: Yes

Secure Webhook Validation for Checkeeper

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

Client Facing Impact: Yes

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

• Release date: 2026-02-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.

What’s new

A new System Notification management interface is now available in the admin portal. Admins can create, schedule, preview, edit, and cancel maintenance notifications through a guided wizard. Each notification supports a rich-text body, a defined maintenance window with start and end times, and two configurable lead-time alerts that trigger automated emails ahead of the maintenance event. Notifications have a lifecycle status (Pending or Active) that controls which actions are available.

Why it matters

You can now communicate planned downtime to merchants at scale without manual intervention. Scheduling is handled by an automated job that fires emails at the configured lead times, reducing the risk of missed or delayed notifications during maintenance windows.

Adds dedicated System Maintenance notification tab to the merchant portal

What’s new

The merchant portal’s notification section now includes a new “System” tab. This tab surfaces all maintenance notifications sent by the platform in a single, dedicated view. Each notification arrives as a formatted email containing the subject, body, maintenance timing, and all relevant details.

Why it matters

Merchants now have a consistent, predictable place to review maintenance communications. Previously, platform-wide maintenance alerts had no dedicated display location in the portal — they now appear in a structured view alongside the formatted email delivered to their inbox.

Fixes saved-login autofill appearing on the wrong field in the merchant portal

What’s new

The browser’s saved-login suggestion popup was incorrectly appearing on the Password field rather than the Username field on the merchant portal login screen. This has been corrected so that the popup triggers on the Username field as expected. Selecting a saved username now also auto-fills the corresponding password.

Why it matters

Before this fix, the autofill prompt appeared in the wrong place, causing confusion and potentially interrupting the login flow. Users relying on saved credentials can now select their username and have both fields populated automatically without extra steps.

Fixes card payment UI overflow on Android devices

What’s new

On certain Android devices, the card payment section within the embedded payment widget was rendering outside the widget’s boundaries on the Contact Information page. The layout has been corrected so the card payment UI is fully contained within the widget frame across all screen sizes.

Why it matters

Merchants and their customers using Android devices will no longer encounter a broken or clipped payment UI. The widget now renders correctly regardless of screen size or device, ensuring a consistent checkout experience.

Enforces ACH banking and account type classification UI when feature flag is enabled

What’s new

When the ACH classification enforcement feature flag is turned on for a merchant, the UI for selecting banking type (e.g., Business) and account type (e.g., Checking) was not rendering correctly. This has been resolved so the classification fields display and function as intended whenever the flag is active.

Why it matters

Integrations that rely on ACH classification — particularly those requiring merchants to specify their banking and account type — can now correctly present the required fields to end users. This unblocks compliant ACH collection flows that depend on this classification step being visible and interactive.

Production Release Notes – Support New Notification Type (AN_NOTTYP_V1)

Release Date: Feb 9, 2026

Release Status: Deployed to Prod

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

New Platform Notification Type: Maintenance on admin portal [AN-34779]

A comprehensive system maintenance notification platform enabling admins to schedule and manage downtime communications to merchants at scale.

• New “System notification” submenu with listing table featuring pagination, search, and bulk actions (create, edit, cancel, preview)
• “New notification” wizard for maintenance events with title, rich-text body, maintenance window (start/end), and dual lead-time scheduling
• Real-time email preview with populated date placeholders
• Automated scheduler job orchestration with status tracking
• Cancel capability for Pending schedules (disabled for Active)
• Inline preview from listing view

Client Facing: Yes

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

New Platform Notification Type: Maintenance on merchant portal [AN-34780]

• Adds a new “System” tab in the merchant portal’s notification section
• Displays all System Maintenance notifications in one dedicated location
• Sends formatted email notifications to merchants about platform maintenance
• Includes proper email template with subject, body, timing, and necessary fields
• Provides maintenance details directly to merchant inboxes

Client Facing: Yes

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

[Merchant portal] Saved merchant login option getting displayed on password field [AN-43347]

Issue Description:The “saved username and password” suggestion popup was appearing on the Password field instead of the Username field.

Expected behavior/fix:The saved-login popup should appear when the user clicks on the Username field. When a saved username is selected, both username and password should be auto-filled.

Client Facing: Yes

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

Card payment method UI overflows outside payment widget frame on Android [AN-39045]

Issue Description:When using the payment widget on certain Android devices, the Card Payment section on the Contact Information page is not fully contained within the widget frame. The card payment UI overflows beyond the widget boundary, causing layout breakage.

Expected behavior/fix:Card payment method UI remains fully within the widget frame, responsive across all screen sizes.

Client Facing: Yes

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

ACH – classification: 2 new type → banking and account type: Expected UI is not getting displayed [AN-44026]

Issue Description:When the ach-classification-enforcement feature flag is turned ON for a merchant, the expected UI for selecting “banking” and account types (e.g., Business & Checking) does not display correctly.

Expected behavior/fix:The new classification UI should be visible and fully functional, allowing selection of the appropriate banking and account type values.

Client Facing: Yes

The post Production Release Notes – Support New Notification Type (AN_NOTTYP_V1) appeared first on AndDone.

What’s new

A new Merchant module webhook is now available for Allies. When an AndDone Admin makes changes to a merchant — such as activating, deactivating, or updating configuration — the Ally receives a webhook notification in real time. This brings merchant activity visibility directly into Ally systems without requiring polling.

Why it matters

You can now build event-driven workflows that react to merchant state changes as they happen. Allies no longer need to manually check for updates or poll the API to detect when a merchant has been activated, deactivated, or reconfigured by an admin.

Synchronizes Ally account details across Admin and Ally portals

What’s new

A synchronization mechanism has been added to ensure that Ally account details stay consistent regardless of where an update originates. Changes made from either the Ally Portal or the Admin Portal are now automatically reflected in both systems.

Why it matters

Before this change, updates made in one portal were not guaranteed to propagate to the other, which could result in stale or inconsistent Ally account data depending on where it was viewed. Account details are now always in sync across both portals.

Updates feature lists for Allies and Ally merchants

What’s new

The feature lists available to Allies and Ally merchants have been updated to reflect the current set of supported capabilities. This ensures that feature access configuration in the Admin Portal accurately represents what is available to each party.

Why it matters

Admins configuring feature access for Allies and Ally merchants can now work from an accurate and up-to-date feature list, reducing the risk of enabling or expecting features that are no longer applicable.

Revokes merchant portal access for Ally merchants via migration

What’s new

A migration script has been run to revoke merchant portal access for Ally merchants across existing accounts. This is a one-time data migration to enforce the correct access boundaries for this merchant type going forward.

Why it matters

Ally merchants should not have direct merchant portal access — that access is managed through the Ally. This migration brings existing accounts into compliance with that access model without requiring manual intervention per merchant.

Discontinues generation and display of Private API keys for submerchants

What’s new

The platform no longer generates Private API keys for submerchants, and existing Private API keys are no longer displayed in the UI. This change removes a potential security exposure by limiting Private API key visibility and issuance to the appropriate account level.

Why it matters

Before this change, Private API keys were being generated and shown for submerchants, which represented an unnecessary security surface. Any workflows that relied on submerchant Private API keys will need to be updated to use the appropriate key type at the correct account level.

Activates webhook notifications for the Ally report module

What’s new

Webhook notifications for the report module are now active for Allies. When a new report is generated, Allies receive a webhook notification automatically, keeping them informed of new report availability without requiring manual checks.

Why it matters

You can now trigger downstream workflows — such as automated report retrieval or processing — as soon as a new report is generated, rather than polling for availability.

Removes redundant report subscriptions for Ally merchants via migration

What’s new

A data cleanup migration has been run to identify and remove redundant report subscriptions for Ally merchants. This is a one-time migration to clean up stale subscription data that was no longer valid.

Why it matters

Redundant report subscriptions could result in unnecessary notifications or processing overhead. This migration ensures that only valid, active subscriptions remain for Ally merchants.

Adds Payments section to the Ally Portal with transaction history, refunds, and search

What’s new

A new Payments section is now available in the Ally Portal, featuring a full payment table with comprehensive transaction history and refund transactions. The table includes robust filtering and search tools, giving Allies a single place to look up and analyze payment activity across their merchants.

Why it matters

Before this change, Allies had no dedicated view of payment activity within the Ally Portal. You can now browse, search, and filter the complete transaction and refund history for your merchants directly from the portal without needing separate reporting tools or API calls.

Production Release Notes – Ally Management V12 (AN_ALMGMT_V12)PROD Release: Ally Management V12 (AN_ALMGMT_V12)

Release Date: Jan 8, 2026

Release Status: Post Deployment Monitoring

Summary

This release delivers a new webhook module for allies to get notifications on their merchant related activity by AndDone Admin. Additionally, this release includes updates to Ally Management and Ally Merchant management including enhancements to feature list, API key display, portal access revocation, report subscription revocations for Ally merchants and ally reporting module webhook updates. Payments section will be available on the Ally Portal to conveniently look up Allies payments.

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

Ally Webhooks | Merchant Module (AN-38060)

The Merchant module webhooks allows allies to receive updates regarding their merchant activity by AndDone Admins like activation, deactivation or any configuration change.

Client Facing: Yes

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

Ally User Management | Update Ally Details When Admin User is Updated (AN-39309)

Added synchronization logic to ensure Ally account details are automatically updated whether its updated from Ally portal or Admin portal.

Client Facing: Yes

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

Ally Management | Ally Feature List, Ally Merchant Feature List (AN-33935)

Updated feature list for Allies and Ally merchants according to the current supported capabilities.

Client Facing: Yes

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

[CR] Ally Merchant Management | Merchant Portal Access to be Removed (Migration) (AN-34999)

Merchant portal access to be revoked for any ally merchants through migration script.

Client Facing: Yes

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

Ally Merchant | Submerchant Private API Keys (Stop Generation and Display) (AN-32568)

Enhanced security by discontinuing the generation and UI display of Private API keys for submerchants.

Client Facing: Yes

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

Ally Webhooks | Webhook Notifications for Report Module (AN-37817)

Webhook notifications for report module are active for allies and will receive notifications for any new report generations.

Client Facing: Yes

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

Ally Report Management | Check if Report Subscription Exists for Ally Merchants and Remove (Migration) (AN-37818)

Data cleanup migration to identify and remove redundant report subscriptions for Ally merchants.

Client Facing: Yes

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

Ally Portal Payments | Payment Table Listing, Refund Transactions & Filter and Search (AN-38252, AN-38253, AN-38258)

New Payment Table within the Ally Portal to provide a comprehensive view of transaction history, refunds along with robust search and filtering tools.

Client Facing: Yes

The post Production Release Notes – Ally Management V12 (AN_ALMGMT_V12) appeared first on AndDone.

What’s new

Merchants can now link their AMS360 bank accounts to the platform and designate a default bank under Business Settings. The available bank options are pulled directly from the accounts already configured in AMS360. When posting receipts, the system automatically suggests the default bank but allows merchants to override it on a per-transaction basis. Once posted, receipts appear in AMS360 under the bank name selected during the posting process.

Why it matters

Before this change, there was no way to associate payments made through the platform with specific AMS360 bank accounts. Merchants can now post receipts directly to the correct bank in AMS360, keeping their records organized and reconciliation straightforward.

Introduces individual and bulk receipt posting to AMS360

What’s new

A new “Post Receipts” tab is now available on the Payment Listing page, displaying AMS360-eligible transactions based on the merchant’s selected filters. Merchants can select one or multiple transactions and submit them for posting in a single action. Only transactions in an Authorized or Settled status are eligible — Failed, Refunded, and Chargeback transactions are excluded. The system requires full posting only; partial posting is not supported. Eligible transactions can also be re-posted individually from their Transaction Details page if needed.

Why it matters

You can now post receipts to AMS360 in bulk directly from the payment listing, eliminating the need to handle transactions one by one. The eligibility rules are enforced automatically, reducing the risk of posting transactions in invalid states.

Adds Invoice Count column to Authorization and Settlement reports

What’s new

The Authorization and Settlement reports now include a new “Invoice Count” column that displays the number of AMS360 invoices associated with each transaction.

Why it matters

You can now see at a glance how many AMS360 invoices are tied to a given transaction without needing to navigate to individual transaction records, making it faster to audit and reconcile payment data.

Updates CSV filename convention for AMS360 compatibility

What’s new

The naming convention for exported CSV files has been shortened to comply with AMS360’s 35-character filename limit, which was causing filenames to be truncated. Authorization reports are now named AMS360_auth_yyyy_mm_dd_D and Settlement reports are named AMS360_settled_yyyy_mm_dd_D, where D is a sequence counter (e.g. _01) to differentiate multiple files exported on the same day. Previously generated files retain their original names and must be manually re-exported if the new naming convention is required.

Why it matters

Before this change, long filenames were being cut off by AMS360’s character limit, which could cause files to be unreadable or misidentified on import. Exported files now import cleanly into AMS360 without truncation issues.

Production Release Notes – AMS360 (AN_AMS360_V7)

Release Date: Jan 8, 2026

Release Status: Deployed to Production

This release bundle includes functionality related to AMS360 receipt posting through APIs.

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

AMS360 Bank Configuration for Receipt Posting

This update allows merchants to integrate AMS360 bank accounts with the AndDone platform for accurate recording of payments and receipts.

• Set a Default Bank: Merchants can choose a preferred bank name under Business Settings. The available options are based on the bank accounts already set up in AMS360. This will act as the “Default Bank,” and the system will automatically suggest it for all receipt postings.
• Flexible Posting Options: While a default bank is set, the merchant is not locked into it. When posting receipts to AMS360, the merchant can manually override the default and select a different bank for specific transactions if needed.
• Seamless Integration: Once posted, all receipts will appear in the AMS360 system under the specific bank name selected during the process, ensuring the merchant’s records remain organized and easy to reconcile.

Client Facing: Yes

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

Individual and Bulk Posting of Receipts to AMS360

A new “Post Receipts” tab is now available on the Payment Listing page, displaying AMS360 transactions based on the merchant’s selected filters. The merchant can select one or multiple transactions and submit them by clicking the “Post Receipts” button.

Important Rules for Posting:

• Eligible Statuses: Only transactions marked as Authorized or Settled can be selected for bulk posting.
• Exclusions: Transactions that are Failed, Refunded, or Chargeback cannot be posted.
• Full Posting Only: The system does not allow partial posting of transactions.
• Re-posting: If necessary, eligible transactions can be re-posted through their individual Transaction Details page.

Client Facing: Yes

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

New “Invoice Count” Column in Reports

The Authorization and Settlement reports now include an “Invoice Count” column, which displays how many AMS360 invoices are associated with each transaction.

Client Facing: Yes

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

Updated CSV Filename Convention for AMS360 Compatibility

To prevent filenames from being truncated (cut off) due to AMS360’s 35-character limit, the naming convention for CSV files has been shortened. Merchants will now see files named in the following formats:

• Authorization Reports: AMS360_auth_yyyy_mm_dd_D
• Settlement Reports: AMS360_settled_yyyy_mm_dd_D

(Note: “D” represents a sequence counter, such as _01, to distinguish between multiple files on the same day.)

Important: Previously generated files will retain their original names. The merchant must re-generate any older files if the new naming convention is required for those records.

Client Facing: Yes

The post Production Release Notes – AMS360 (AN_AMS360_V7) appeared first on AndDone.

• Release date: December 23, 2025
• Release status: Deployed to Production
• Source pages: ANDDONE-ALL RELEASE NOTES.pdf pp. 215–219

References

• AN_OUTPAY_V7

Original release notes excerpt

Production Release Notes – Outbound Payments (AN_OUTPAY_V7)
Release Date: Dec 23, 2025,
Release Status: Deployed to Production
This release bundle contains Outbound payments API's for Merchant portal, Vendor
Notifications to Admin and couple of enhancements for payment creation. Dynatrace has been
implemented to enhance application logging and Monitoring for Outbound Payments.
Features Deployed to PROD Client
Facing
Impact
Merchant Portal Enhancements
DBA (Doing Business As) Field Optional in Vendor Profile Yes
The DBA Name field is now optional when creating or editing vendor profiles. This,
change allows users to proceed with vendor creation even when the business does
not operate under a separate trade name.

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

The post Production Release Notes – Outbound Payments (AN_OUTPAY_V7) appeared first on AndDone.

• Release date: November 25, 2025
• Release status: Deployed to UAT
• Source pages: ANDDONE-ALL RELEASE NOTES.pdf pp. 325–329

References

• AN_OUTPAY_V7

Original release notes excerpt

UAT Release Notes – Outbound Payments (AN_OUTPAY_V7)
Release Date: Nov 25 2025
Release Status: Deployed to UAT
This release bundle contains Outbound payments API's for Admin portals and couple of
enhancements.
Features Deployed to UAT Client
Facing
Impac
t
Merchant Portal Enhancements
DBA (Doing Business As) Field Optional in Vendor Profile Yes
The DBA Name field is now optional when creating or editing vendor profiles. This
change allows users to proceed with vendor creation even when the business does
not operate under a separate trade name.

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

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

• Release date: November 24, 2025
• Release status: Deployed to Production
• Source pages: ANDDONE-ALL RELEASE NOTES.pdf pp. 185–186

Highlights

• AN-37318, AN-37820, AN-38565)

References

• AN-37318
• AN-37820
• AN-38565
• AN_BALPH2_V1

Original release notes excerpt

Production Release Notes – Balance Platform Phase II (AN_BALPH2_V1)
Release Date: Nov 24th, 2025
Release Status: Deployed to Production
This release bundle primarily consists of prerequisites for Phase 2 initiatives, Instructional
Payout Foundational items, KYC Updates and Miscellaneous Tech Backlog and hotfix items, This
includes updates to Admin Portal, Merchant Portal and some backend processing upgraded.
This also includes bug-fixes as identified during the development cycle.
Features Deployed to Production Client
Facing
Impact
Merchant Associations with Existing Application Admin No
Portal Changes
AN-37318, AN-37820, AN-38565)
Association of an existing merchant to an approved or
Ariemanart @ mares Armiieatian.

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

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

• Release date: November 07, 2025
• Release status: Deployed to UAT
• Source pages: ANDDONE-ALL RELEASE NOTES.pdf pp. 307–308

Highlights

• AN-37318, AN-37820, AN-38565)

References

• AN-37318
• AN-37820
• AN-38565
• AN_BALPH2_V1

Original release notes excerpt

UAT Release Notes – Balance Platform Phase II (AN_BALPH2_V1)
Release Date: Nov 7th, 2025
Release Status: Deployed to UAT
This release bundle primarily consists of prerequisites for Phase 2 initiatives, Instructional
Payout Foundational items, KYC Updates and Miscellaneous Tech Backlog and hotfix items, This
includes updates to Admin Portal, Merchant Portal and some backend processing upgraded.
This also includes bug-fixes as identified during the development cycle.
Features Deployed to UAT Client
Facing
Impact
Merchant Associations with Existing Application Admin No
Portal Changes
AN-37318, AN-37820, AN-38565)
Association of an existing merchant to an approved or
Ariemanart @ mares Armiieatian.

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

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