Timing, end to end
Payment timing operates across two distinct regimes: synchronous electronic messaging executing in milliseconds, and asynchronous interbank settlement operating across days.
While card scheme regulations publish rigid statutory deadlines for clearing and dispute presentment, merchant funding timelines are commercial parameters negotiated in private merchant agreements.
End-to-end transaction lifecycle timeline
Milestone elapsed durations and operational controllers
| Lifecycle phase | Typical elapsed duration | Operational controlling entity |
|---|---|---|
| Authorization request and decisioning | Under 1,000 milliseconds | Card network switches and issuing bank |
| Authorization hold posted to account | Immediate to several minutes | Issuing bank mobile and core banking systems |
| Transaction capture submission | Immediate (card-present) to multiple days (fulfillment) | Merchant order management system |
| Daily batch closure | Scheduled daily cut-off window | Payment processor |
| Interbank clearing file processing | Overnight following batch close | Acquiring bank and card networks |
| Multilateral interbank settlement | Typically next banking day following clearing | Card schemes and central bank settlement systems |
| Merchant funding disbursement | Commonly 1 to 3 banking days following batch close | Acquiring bank or payment processor agreement |
| Customer refund credit posted | 2 to 5 business days following refund issuance | Issuing bank core banking systems |
| Chargeback dispute presentment | 30 to 120 days following transaction date | Cardholder and issuing bank |
Mandatory scheme deadlines
Unlike commercial funding schedules, scheme deadlines are rigid statutory requirements established by Visa, Mastercard, and Nacha. Violating these timeframes carries financial penalties or immediate forfeiture of dispute rights:
| Procedural requirement | Enforced scheme limit | Regulatory reference |
|---|---|---|
| Authorization-to-clearing window (all transaction types) | 5 to 30 calendar days (scheme, channel, and MCC dependent) | Authorization |
| Automated fuel dispenser preauthorization completion | 2 hours from initial approval | Authorization |
| Card-present cancellation authorization reversal | 24 hours from cancellation event | Voids, reversals, and refunds |
| Card-not-present authorization reversal | 72 hours from cancellation event | Voids, reversals, and refunds |
| Cardholder dispute filing window | Typically 120 calendar days from transaction date | Disputes |
| Merchant representment response window | Typically 30 days (Visa) or 45 days (Mastercard) | Disputes |
| Standard technical ACH return window | 2 banking days following settlement | ACH |
| Unauthorized consumer ACH debit return window | 60 calendar days following statement date | ACH |
Understanding funding lags: T+n and banking calendars
A common source of confusion in financial operations is the interpretation of settlement schedules:
- T represents batch close, not order placement: Funding schedules are defined as T+n, where T represents the exact calendar day the batch closed, and n represents the number of intervening banking days. If an order is captured after the processor's evening cut-off window, its T-date rolls over to the following day.
- Banking days exclude weekends and federal holidays: Interbank clearinghouses and central bank wire networks operate strictly on commercial banking days.
Consider a T+2 funding schedule with a 6:00 PM daily cut-off:
| Transaction event | Batch close timestamp | Scheduled funds arrival |
|---|---|---|
| Tuesday, 10:00 AM | Tuesday evening (T) | Thursday |
| Friday, 2:00 PM | Friday evening (T) | Tuesday (Monday + Tuesday banking days) |
| Friday, 7:00 PM (post cut-off) | Monday evening (T) | Wednesday |
Orders placed only a few hours apart on a Friday can fund five calendar days apart without any operational malfunction.
Root causes of missing disbursements
When scheduled deposits fail to arrive in a merchant's bank account, investigate in the following order:
- Unclosed batches: The point-of-sale terminal or automated gateway script failed to close the batch.
- Missing capture commands: Orders were marked as fulfilled in e-commerce systems, but API capture requests failed to trigger.
- Federal banking holidays: Interbank wire switches were halted for a public holiday.
- Compliance or risk funding holds: The payment provider suspended payouts pending verification of high dispute velocity or volume spikes.
- Rejected disbursement account details: Updated routing or account numbers failed ACH validation.
- Negative net position: High refund or chargeback volumes exceeded gross daily sales, resulting in a negative net position where zero capital was available for payout.
Architectural contrast: Cards versus ACH
Cards and ACH operate on fundamentally inverted operational paradigms:
- Card networks provide immediate synchronous feedback at authorization. If an authorization succeeds, the merchant can be confident that credentials are valid and funds are reserved.
- ACH direct debits operate on negative confirmation: the network provides zero real-time confirmation of balance sufficiency. A transaction is presumed successful only when no ACH return arrives within the mandatory two-day return window.
Attempting to apply card-based fulfillment architectures directly to ACH networks without accounting for delayed return windows leads to substantial bad-debt losses.
Provide precise operational guidance aligned with transaction state transitions.
- Inquiries regarding disappearing pending transactions: explain that the entry was an authorization hold that expired without being captured, confirming that no funds were deducted.
- Inquiries regarding delayed refund deposits: explain that the refund was processed on the date shown, and that remaining processing delays are governed by the cardholder's issuing bank.
- Inquiries regarding duplicate statement entries: differentiate between an active settled charge and an un-cleared pending authorization hold, providing the expected date when the hold will drop.
Terms introduced
- T+n: funding counted in banking days from batch close, not from purchase.
- Banking day: a day the settlement system runs. Not weekends or holidays.
- Negative net position: a period where refunds and chargebacks exceed sales.