The transaction lifecycle is the full path a single payment travels, from the issuer's approval to the point where the record can no longer be reversed. Its practical lesson is that a payment is not one event with one amount and one date: it is a chain of records, each carrying a different reference and a different value.
One sale, day by day
Tuesday 14:02 — authorization: the issuer approves, the amount is held, the customer sees a pending line. Tuesday 23:00 — the merchant's capture drops into the acquirer's cut-off file. Wednesday — the schemes clear the batch, calculate interchange and produce net positions between the banks. Thursday or Friday — the acquirer credits the merchant, less fees. Day 40 — the cardholder disputes the purchase and the transaction is live again.
The record changes name at every hand-off
Reconciliation fails because teams try to match an order ID from checkout against a credit on a bank statement. In between, the same payment has been an approval code, a batch reference, an acquirer reference number carried through clearing, and finally one line inside an aggregated payout. Matching works only when each stage's identifier is stored against the order as it is issued. Reconstructing it afterwards from amounts and dates is guesswork the moment two customers pay the same price on the same day.
The amount changes too
The figure collected and the figure received are never equal. Fees, scheme charges, currency conversion, adjustments and any reserve are netted before the credit lands, so a day of sales arrives as a single number that matches nothing in the order table. That is why finance reconciles at settlement rather than at approval, and why the payout line, not the sales report, is the source of truth for cash.
When a transaction is finally closed
Settlement is not the end. Refunds, chargebacks, representments and scheme arbitration all arrive afterwards, and the windows are long — commonly around 120 days from the transaction or the expected delivery date, and longer in some travel and services categories. A transaction is closed only when the last window under the dispute flow has expired, which is why evidence is kept well past the point the money looks final.
What changes at volume
At a few hundred payments a day the gaps can be eyeballed. At tens of thousands they cannot, and the lifecycle becomes a data problem: automated matching on stored references, an exception queue for unmatched items, and an alert on approvals that never became collections.