Batch processing collects transactions over a set period and submits them together as one file, instead of sending each one the instant it happens. The batch processing definition turns on timing rather than transaction type: card capture, automated clearing house origination and most payout runs all work this way, with entries accumulating until a cut-off arrives and the file goes.
What is batch processing in a card flow?
During trading, each approved sale is captured and added to an open batch. The approval itself is not batched — authorization happens in real time, in the second the customer pays, and only the capture waits.
At the cut-off, often late evening, the batch closes and is submitted for clearing. Overnight the acquirer sorts entries by scheme and passes them to the networks. One to three business days later the money lands as a single deposit at settlement covering many sales at once. That deposit is the unit balance reconciliation works against, and the gap between close and credit is what treasury management forecasts across.
The cut-off is a commercial term
For a merchant the practical batch processing meaning comes down to one setting. Merchants can rarely change how clearing works, but the cut-off is configurable and worth arguing about. Moving it from ten in the evening to two in the morning pulls an entire evening of sales one day forward in the funding cycle — every day, permanently, for the cost of one conversation at contract stage.
The same setting decides which accounting day a sale falls into, so a cut-off tuned for cash flow can quietly complicate month-end. Pick deliberately rather than accepting the default the acquirer ships.
Correcting a sale before the file goes
Between capture and cut-off there is a window in which a transaction can still be pulled. Cancelling it there is a void: no interchange, no refund fee, and nothing on the cardholder's statement to explain. After the batch closes the only remedy is a refund, which costs money and appears as two entries the customer can query.
Support teams that know where their cut-off sits cancel far more orders on the cheap side of it.
Batches that never close, and batches that close twice
A batch that fails to close is the classic silent incident: sales sit uncaptured, no deposit arrives, and nobody notices until someone reconciles. Retail terminals cause a specific version when a device loses connectivity and holds a batch it never transmits.
Duplicate submission is the mirror image and worse, charging customers twice and generating a wave of disputes. Both are cheap to monitor for: alert when no batch has closed by an expected time, and when a batch's count or value deviates sharply from the same weekday last week.