Settlement Lifecycle — From Payment Capture to Fund Transfer
Introduction
In the previous article, we established the terminology used throughout settlement systems.
In this article, we will follow the journey of a transaction from payment capture until funds reach the beneficiary's bank account.
Payment Capture
Every settlement journey starts with a successful payment.
When a customer initiates a payment, the request passes through multiple systems before eventually being accepted or rejected. Once the payment is successfully processed, the payment system marks it as captured.
From a customer's perspective, this is usually the end of the journey. The payment has succeeded and the order can proceed further.
However, for the merchant, the captured payment does not immediately translate into funds arriving in the bank account. Multiple financial and operational checks still need to happen before those funds become eligible for settlement. This captured payment acts as the starting point for all downstream settlement-related workflows.
Transaction Creation
Settlement systems generally do not work directly on payment records. Instead, a separate financial record called a transaction is created from the captured payment. This transaction becomes the primary unit used by downstream financial systems.
A transaction carries information such as:
Payment reference
Associated merchant
Credit or debit impact
Financial metadata required for settlement
Additional transactions may also be created for refunds, adjustments, chargebacks, and other fund movements.
By operating on transactions instead of raw payment records, settlement systems can maintain a consistent financial view across different types of money movement.
In a nutshell, changes to a merchant's financial position are typically represented through transactions. Every transaction is associated with an originating entity such as a payment, refund, adjustment, chargeback, or another financial event.
Transaction Readiness Evaluation
Not every transaction becomes immediately eligible for settlement. Before funds can be transferred, settlement systems evaluate whether a transaction satisfies all required business conditions.
Depending on the organization, these checks may include:
Payment capture status
Configured settlement delay
Risk or compliance validations
Merchant-specific settlement permissions
Payment method dependent schedules (E.g. Card, UPI, Net-banking)
Internal business rules
Transactions that pass these checks are considered ready for settlement. Transactions that fail one or more conditions continue to remain pending until the required conditions are met. This readiness evaluation acts as a safety layer before funds are moved.
Transaction Selection for Settlement
As transactions become ready, the settlement system periodically identifies the set of transactions that can participate in the settlement cycle.
For large platforms, thousands or even millions of transactions may become ready throughout the day.
Settlement systems typically select a group of eligible transactions belonging to a beneficiary and prepare them for settlement processing. However, depending on business requirements, some organizations may choose to process individual transactions as separate settlements.
This grouping process allows the system to efficiently manage fund movement while adhering to configured settlement schedules. At the end of this stage, the system knows which transactions are expected to contribute towards a settlement. This process also helps in estimating the outgoing fund requirement for that cycle.
Settlement Creation
Once eligible transactions have been selected, the settlement system creates a settlement record. This record acts as a financial representation of the funds that need to be transferred.
A settlement typically contains associated information such as:
Beneficiary details
Settlement value
Associated transactions
Destination bank account
Processing metadata
From this point onwards, the settlement becomes the primary entity that the system tracks until funds are successfully transferred or corrective action is required.
Fund Transfer
After a settlement is created, the settlement system initiates a fund transfer request through the appropriate banking partner.
The exact integration mechanism may vary depending on the banking infrastructure involved. Some integrations may rely on APIs, while others may use files or a combination of multiple integration mechanisms.
The objective remains the same: communicate the settlement details to the banking network and request movement of funds to the beneficiary's bank account. At this stage, the settlement request has left the internal platform and entered the banking ecosystem.
Fund Transfer Status Tracking
Submitting a settlement request to a bank does not immediately guarantee that funds have been credited to the beneficiary.
The settlement system must continuously track the status of the transfer request until a final outcome is received. Depending on the banking integration, status information may be received through:
Status APIs
Webhooks
Reconciliation files
Periodic polling mechanisms
The settlement remains under observation until the banking partner confirms whether the fund transfer was successful or unsuccessful. This tracking process helps maintain visibility into every settlement being processed.
Reconciliation
Fund movement is one of the most critical operations performed by a financial system. For this reason, settlement systems (OR an independent service) will periodically reconcile the internal records with information received from banking partners.
The purpose of reconciliation is to verify that:
Requested transfers were processed correctly
Settlement values match expected values
No settlement has been accidentally missed or duplicated
Internal records remain financially accurate
Reconciliation acts as an additional layer of validation and helps identify financial discrepancies that may require operational intervention. This process does not necessarily happen at the same time. It may happen passively and results are kept ready for internal audit purposes.
Merchant Notification
Once a settlement is successfully processed, the beneficiary is informed about the completion of the fund transfer.
Notifications may be delivered through:
Dashboard updates
Email notifications
Push notifications
Messaging systems (SMS, WhatsApp)
Settlement reports
In parallel, beneficiaries may also receive confirmation from their banking institution when funds are credited. At this point, the settlement lifecycle for that transaction group is considered complete.
Summary
| Stage | Objective |
|---|---|
| Payment Capture | Confirm payment collection |
| Transaction Creation | Create financial representation |
| Readiness Evaluation | Determine eligibility |
| Transaction Selection | Pick transactions for settlement |
| Settlement Creation | Create settlement record |
| Fund Transfer | Initiate movement of funds |
| Status Tracking | Track processing outcome |
| Reconciliation | Validate financial accuracy |
| Merchant Notification | Inform beneficiary |
In this article, we explored the journey of a transaction after a payment is captured and how it eventually reaches the beneficiary.
In the next article, we will move one level deeper and understand the various services that participate in this lifecycle and how they interact with each other.
