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

What’s New

The settlement processing pipeline has been rearchitected to handle large volumes of authorization events simultaneously rather than sequentially. The underlying data layer has been updated to support bulk settlement operations, and a scheduler now publishes groups of settlement events in bulk through the event routing infrastructure. Incoming settlement events are processed and evaluated to determine whether a processing schedule needs to be created.

Why It Matters

Before this change, high-volume settlement scenarios — such as end-of-day batches or simultaneous authorization bursts — could create processing bottlenecks because events were handled one at a time. The pipeline can now ingest and route large numbers of settlement events concurrently, reducing settlement latency during peak periods.

Extends Downstream Handlers to Process Bulk Settlement Events

What’s New

The transaction, transaction event log, transaction status, and payment link status handlers have each been updated to correctly process bulk settlement success events. Previously, these handlers were designed around single-event processing and could not interpret or act on the batch-formatted events introduced by the new bulk pipeline.

Why It Matters

Before this change, downstream systems that update transaction records, status fields, and payment link states would not respond correctly when bulk settlement events arrived. All downstream handlers now process bulk success events accurately, ensuring that transaction and payment link states reflect settlement outcomes without manual intervention or reprocessing.

Adds a Dead Letter Queue for Automatic Retry of Failed Settlement Events

What’s New

A dead letter queue has been introduced into the settlement processing pipeline. When a settlement event fails to process — for example, due to a transient error during a high-volume period — it is routed to the dead letter queue and automatically retried rather than being dropped or requiring manual recovery.

Why It Matters

Before this change, settlement events that failed during processing had no automatic recovery path, meaning failed events could result in unresolved transaction states that required manual investigation and reprocessing. You can now rely on the pipeline to automatically retry and resume processing of failed settlement events, maintaining settlement integrity even when simultaneous high-volume events cause transient failures.

Release Date: Feb 26th, 2026

Release Status: Deployed to PROD

This release bundle primarily consists of modules required to support settlement processing based on the authorization events which contain information about the value date or settlement date-time. This version has the implementation to support change in approach for handling bulk events simultaneously. Also includes an ability to retry and resume of settlement processing incase of voluminous settlement occurrences happening at the same time.

Design changes to support bulk processing of events

(AN-42017, AN-42018, AN-42019)

Data source changes to support bulk settlement processing
Publishing of Bulk settlement events through event-bridgescheduler
Processing of incoming settlement event and createschedule if required

Client Facing Impact: No

Processing Enhancements for downstream processing

(AN-42020, AN-42545, AN-42546, AN-42547, AN-44108)

Transaction entity handler enhancements to support Bulk OnSuccess events
Transaction event log handler enhancements to support Bulk OnSuccess events
Transaction status handler enhancements to support Bulk OnSuccess events
Payment Link status handler enhancements to support Bulk OnSuccess events
Implement Dead letter queue for Retry of settlement event processing

Client Facing Impact: No

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

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

Highlights

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

References

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

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

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: November 10, 2025
• Release status: Deployed to UAT
• Source pages: ANDDONE-ALL RELEASE NOTES.pdf pp. 321–322

Highlights

• Paymet link portal – New Design [ AN- 38215] Yes

References

• AN_MISCPI_V5

Original release notes excerpt

UAT Release Notes – Miscellaneous Priority Items (AN_MISCPI_V5)
Release Date: UAT Nov 10, 2025
Release Status: Deployed to UAT
This release bundle primarily consists of UI updates on the Payment links and Adyen
Transaction events items. This also includes bug-fixes as identified during the development
cycle.
Features Deployed Client
Facing
Impact
Paymet link portal – New Design [ AN- 38215] Yes
Implements new Design for the payment link. So that the
new payment link ULis as per the latest brand guideline.
View & send reseinten the navmantlink Gummarsnane Yes.

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

The post UAT Release Notes – Miscellaneous Priority Items (AN_MISCPI_V5) appeared first on AndDone.

• Release date: December 29, 2024
• Release status: Deployed to Production
• Source pages: ANDDONE-ALL RELEASE NOTES.pdf pp. 225–226

Highlights

• Upgradation of Transactions Microservice .NET 6.0 to 8.0 (AN-19993) No

References

• AN-19993
• AN_TRNUGD_V1

Original release notes excerpt

Production Release Notes – Transaction Microservices Upgrade
AN_TRNUGD_V1)
Release Date: December Sth, 2024
Release Status: Deployed to Production
Highlights of Work for Release: In this release, the primary item which was rolled out was the
NET Framework upgrade of Transaction Microservices, from 6.0 to 8.0, due to an end-of-
support as notified by Microsoft. Transaction Microservices, caters to all of the payment
transaction processing. and is thus a critical component of the platform.
Along with this, there were some bug fixes including hot-fixes that were also deployed together
with the bundle.
Features Deployed to PROD Client Facing
Transaction Microservices .NET version 6.0 to 8.0 upgrade GEL
AN_TRNUGD_V1)
Upgradation of Transactions Microservice .NET 6.0 to 8.0 (AN-19993) No
Technology Upgrades necessary to be compliant with latest updates

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

The post Production Release Notes – Transaction Microservices Upgrade appeared first on AndDone.

• Release date: December 24, 2024
• Release status: Deployed to Production
• Source pages: ANDDONE-ALL RELEASE NOTES.pdf pp. 199–201

Highlights

• Secure APIs-Integration to ORUM-V1(AN-24087) Yes
• Validation enabled for a bank account with ORUM.

References

• AN-24087
• AN_MISCPI_V1

Original release notes excerpt

Production Release Notes – Miscellaneous Priority Items (AN_MISCPI_V1)
payment remRelease Date: December 24, 2024 & December 30, 2024
Release Status: Deployed to Production
This release bundle contains multiple miscellaneous items including few CRs and Hotfix items.
This included few CRs needed for Refund settlement events
Features Deployed to Production Client
Facing
Impact
Secure APIs-Integration to ORUM-V1(AN-24087) Yes
Develop a Secure Open API for POST verity bank accounts and GET verity @
bank account
« Validation enabled for a bank account with ORUM.
Confirmation and validation ofthe status of a bank account with ORUM.
by passing the account number, Routing number and account holder
name to the ANDDONE secure APT

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

The post Production Release Notes – Miscellaneous Priority Items (AN_MISCPI_V1) appeared first on AndDone.

• Release date: August 13, 2024
• Release status: Deployed to PROD.
• Version: 2.09.6
• Source pages: ANDDONE-ALL RELEASE NOTES.pdf pp. 139–144

Highlights

• Admin Portal Revamp General Update 2 (AN-16453) Yes

References

• AN-16453

Original release notes excerpt

Production Release 2.09.6 Notes
Release Date: August 13rh, 2024
Release Status: Deployed to PROD.
Features Deployed to UAT Client
Facing
Impact
Admin Portal Revamp General Update 2 (AN-16453) Yes
Front End Implementation of Transactions Details with
Refund and Chargebacks
Refund and Chargeback details can be seen separately
Sub Merchant Updates
Deactivate
Emulate

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

The post Production Release 2.09.6 Notes appeared first on AndDone.

• Release date: December 14, 2023
• Release status: Deployed to Production
• Version: 2.08.6
• Source pages: ANDDONE-ALL RELEASE NOTES.pdf pp. 61–64

Highlights

• Support and Handlina of Charaebacks (AN-5786) Yes

References

• AN-5786

Original release notes excerpt

AndDone Release 2.08.6 Notes
Release Date: December 14th, 2023
Release Status: Deployed to Production
Highlights of Work for Release: In this release, the major functionalities that were deployed to
production were processing of chargebacks with the initial implementation of chargeback in the
AndDone Platform. The Payments Multi-Select Enablement of Reference Type has been added
to the Payment Links functionality where now there can be more than one reference type
selected. This functionality has also been added to the reporting infrastructure for Settlement
and Authorization Reports,
More 0, for Commerce Bank enhancements we support the voiding of transactions now which
enables the system to void authorized transactions.
Features Deployed to PRODUCTION Client
Facing
Impact
Support and Handlina of Charaebacks (AN-5786) Yes

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

The post AndDone Release 2.08.6 Notes appeared first on AndDone.

• Release date: October 18, 2023
• Release status: Released to Production
• Version: 2.08.3
• Source pages: ANDDONE-ALL RELEASE NOTES.pdf pp. 51–54

Highlights

• General UI Updates/Support/Enhancements (AN-88/AN-227) Yes

References

• AN-227
• AN-88

Original release notes excerpt

AndDone Release 2.08.3 Notes
Release Date: October 18th, 2023
Release Status: Released to Production
Highlights of Work for Release: The main scope of this release was that there were key fast
follow items that were deployed to Production on a high priority for Notifications and CSS/HTML.
Updates. Token Link Re-direction was implemented and deployed to Production to enhance the
overall experience of the user. There was also functionality added around editing Payment Links.
NACHA Report UI Implementation and Back-End Development was completed for consolidated
reports for merchants,
Features Deployed to PRODUCTION Client
Facing
Impact
General UI Updates/Support/Enhancements (AN-88/AN-227) Yes
Updated Templates for the following pages:
Payments Pace

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

The post AndDone Release 2.08.3 Notes appeared first on AndDone.