At a glance
Average days from successful capture to acquirer-funded bank deposit. Measures the cash-flow lag between customer-paid and merchant-cash-in-bank. Acquirer-driven, not Authorize.Net-driven (Authorize.Net hands the batch off; the acquirer funds).
Calculation
Calculated automatically from your Authorize.net data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
“Heartland Hardware Co.”, Elavon-acquired, 30 days ending 02 May 26.
Notes:
- 1.9 days for cards is normal. Elavon funds Mon-Fri at T+1 with same-day cut-off at 16:00 PT.
- A capture on Friday 14:00 PT settles Monday morning. That’s 3 days clock time, T+1 in business days. The card averages T+1 to T+2 over the month due to weekends.
- eCheck.Net at 4.1 days reflects NACHA standard. No way to speed this up without paying for “Same Day ACH” service.
- Holiday impact: 28 May 26 (Memorial Day). A Friday-before-Memorial-Day capture funds on Tuesday, an extra day delay.
- Reserve-held funds excluded. Heartland is on a no-reserve account (10+ years processing history); newer merchants may see headline number lower because reserved funds aren’t counted in deposits.
Sibling cards merchants should reference together
Reconciling against the vendor’s own dashboard
Where to look: Authorize.Net Dashboard does not show settlement-lag directly; refer to the acquirer (Elavon / Vantiv / Fiserv) statement and the merchant business-bank account deposit dates. Why our number may differ:
Cross-connector reconciliation: