Batch Processing
Daily settlement process where authorized transactions are grouped and sent to acquiring bank for fund transfer.
Overview
What is Batch Processing?
Batch processing is the daily settlement mechanism where authorized transactions are grouped together and submitted to the acquiring bank for fund transfer. Rather than settling each transaction individually in real-time, payment processors accumulate all day's authorizations into "batches" that are closed and submitted at end-of-day (typically midnight in processor's timezone). This batch submission triggers the multi-day settlement process where funds move from issuing banks through card networks to acquirers and finally to your merchant account.
Batch cutoff times are critical for settlement speed. Transactions authorized before the daily cutoff (often 5-8 PM in processor's timezone) are included in that day's batch and settle T+1 or T+2. Transactions after cutoff roll into next day's batch, adding 24 hours to settlement timeline. For high-risk merchants with T+3 to T+7 settlement delays, missing cutoff by one hour means receiving funds an entire day later - impacting cash flow when processing $50K-100K daily.
Failed batch submissions can hold funds for extended periods. If batches fail to submit due to technical issues, compliance problems, or account holds, transactions remain in "authorized but unsettled" status - you can't access funds and authorizations eventually expire (typically 7-30 days depending on card type). High-risk merchants should monitor batch settlement status daily and investigate immediately when batches don't close on schedule.
Modern payment orchestration platforms automate batch management across multiple PSPs, but merchants with direct processor relationships must manually ensure batches close daily. Forgotten batches cost real money - a $50K batch left open for 7 days costs $350 in lost interest (assuming 3.65% annual rate) plus the risk of expired authorizations that must be re-captured or lost entirely.
In depth
Everything you need to know.
Throughout the day, your payment gateway authorizes transactions in real-time - each successful authorization places a hold on customer funds and creates a pending transaction record. These authorized transactions accumulate in your processor's system awaiting batch submission. At the designated batch cutoff time (configured in your merchant account settings, typically 5-11 PM), the processor automatically closes the batch: collecting all authorized transactions since the last batch, calculating total batch value and transaction count, generating a settlement file containing all transaction details, and submitting this file to the card network. The network distributes transaction data to issuing banks, which transfer funds through the card network to acquiring banks within 24-48 hours. Your acquirer receives funds, deducts processing fees and reserves, then deposits net amount to your merchant account. After the settlement period specified in your agreement (T+1 to T+7), funds transfer from merchant account to your operating bank account.
Batch timing directly impacts cash flow and authorization expiration risk. Missing batch cutoff delays settlement by 24 hours - for $100K daily volume with T+5 settlement, this means $100K arrives a day later, impacting your ability to pay suppliers, fulfill orders, or cover operating expenses. The compounding effect is significant: if you consistently miss cutoff, you permanently operate 24 hours behind on cash flow. Authorization expiration creates revenue risk. Authorizations typically expire after 7-10 days if not captured in a batch. If technical issues prevent batch submission for multiple days, authorizations expire and you must re-request authorization or lose the sale entirely. For high-ticket items ($500+), expired authorizations can mean thousands in lost revenue from customers who decline when re-charged days later. Batch monitoring prevents processing disruptions. Failed batch submissions often indicate account issues: compliance holds, reserve threshold breaches, or technical failures. Catching failed batches within hours allows immediate remediation; discovering them days later means extended fund holds and potential lost transactions.
Illustrative example — not a specific client engagement.
- A supplement merchant with 5 PM batch cutoff processed 60% of daily volume between 6-11 PM (peak hours). These transactions settled 24 hours later than necessary. Changing cutoff to 11 PM accelerated settlement for 60% of volume, effectively reducing average settlement time from T+5 to T+4.4, improving cash flow by $80K for their $2M monthly volume.
- An online course platform experienced technical issues preventing batch submission for 3 days. By day 3, they had $180K in authorized but unsettled transactions. On day 4, authorizations began expiring - losing $40K in sales from customers who declined re-authorization. Daily batch monitoring would have caught the issue within hours, preventing authorization expirations.
- A dating platform operating with 3 PSPs had different batch cutoffs (5 PM, 8 PM, 11 PM). This created unpredictable cash flow - some days receiving $150K, others $80K despite similar sales volumes. Aligning all cutoffs to 11 PM standardized cash flow timing, making financial forecasting accurate within 5% vs. previous 20% variance.
- Configure batch cutoff for 11 PM or midnight to capture maximum daily transactions in same-day batch
- Implement automated batch monitoring: alerts when batches fail to close on schedule or contain unusual transaction counts
- For multi-PSP setups: align batch cutoffs across all processors to consistent time for predictable cash flow modeling
- Review batch reports daily: total volume, transaction count, any errors or rejected transactions requiring attention
- Process voids and refunds before batch cutoff - ensures same-day adjustment rather than creating next-day complications
- Maintain batch submission logs for 18+ months - critical for chargeback defense and accounting reconciliation
- For high-volume merchants: request multiple daily batch windows to accelerate settlement for peak-hour transactions
- Not monitoring batch closure daily - operating blind to failed batches that delay settlement or cause authorization expiration
- Using processor default cutoff times - accepting 5 PM cutoff when your peak sales are 6-10 PM, pushing most transactions to next day's batch
- Forgetting to close manual batches - some legacy systems require manual batch closure, forgotten batches hold funds indefinitely
- Not coordinating batch times across multiple PSPs - different cutoffs across 3 processors creates settlement chaos and cash flow unpredictability
- Ignoring authorization expiration timelines - assuming authorizations last indefinitely when they expire in 7-10 days
- Processing voids/refunds after batch closure - forcing these adjustments into next day's batch, delaying customer refunds by 24+ hours
Keep exploring
Related terms
Put this to work
for your business.
MIDs structures high-risk acquiring across 30+ banks — smart routing, fraud and chargeback control built in. Tell us your category and volume and we'll build the setup around it.