PROD Release Notes – Event Based Settlement Processing Upgrade (AN_EVTSPU_V2)

Redesigns the Settlement Pipeline to Support Bulk Event Processing

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