Payout Cycle
A payout cycle is the schedule on which a payment provider transfers a merchant's settled funds to its bank account — daily on a delay (T+1, T+2), weekly, or on request — set by the provider's own settlement from the schemes, its view of the merchant's risk, and its appetite for the float between. For a merchant it is working capital; for the provider a risk buffer and a small income on the float.
- Also known as
- Settlement cycle, Payout schedule, Settlement terms
- Used at
- every merchant agreement and facilitator terms; a line in the pricing that merchants read after the rate and should read before
- Binding
- the merchant agreement or the platform's terms; the provider may extend the cycle on a change in risk, and reserves and holds sit on top of it
- Typical cycles
- T+1 or T+2 for low-risk card-present merchants with their own acquirer; T+2 to T+7 for e-commerce at facilitators (Stripe's default of two business days in most markets, longer for new accounts and some categories); weekly or longer for high-risk; same-day or instant as a paid option
- Typical arithmetic
- the funds in transit equal daily sales × the cycle length; a merchant moving from T+7 to T+2 on €200,000 of daily card sales releases €1m of working capital
- Parties
- the merchant, the PSP or acquirer, the scheme settlement beneath (which arrives at the provider on its own cycle), the sponsor bank if any, and the merchant's treasury, which plans around it
How a payout cycle works in practice
A merchant captures Monday's sales. The acquirer clears them Monday night and receives the scheme's settlement Tuesday or Wednesday; it pays the merchant on the cycle in its contract — Wednesday on T+2, less fees, refunds, chargebacks and any reserve. The merchant's Monday sales are in its account Wednesday morning; its treasury knows the money arrives two days late and plans supplier payments and payroll around it. A facilitator with 20,000 sub-merchants runs the same cycle by rule, with longer cycles for new or high-risk accounts and an instant option for a fee.
The cycle is the provider's risk tool. Funds not yet paid out cover the refunds and chargebacks that arrive after the sale — a merchant that fails on Tuesday still owes Monday's chargebacks, and the unpaid Monday settlement is the first thing the provider takes. Longer cycles for riskier merchants are a reserve by another name. The float also earns the provider interest at current rates, which is why providers were slower to shorten cycles when rates rose, and why merchants above a size negotiate T+1 as part of the price.
For a buyer of a payments company, the payout terms across the merchant book are a liability schedule (funds owed to merchants) and a risk buffer (funds held against their failures) — and, at scale, a float whose income is a revenue line that rates decide.
Example
An online retailer on a facilitator's T+4 cycle sells €300,000 a day: €1.2m in transit at all times, financed by a revolving credit line at 7% — €84,000 a year of interest. It negotiates, on the strength of two years' clean history, to T+2 at the same rate: €600,000 released, €42,000 of interest saved. The facilitator agrees because the retailer's chargeback rate is 0.3% and it would otherwise lose the account to an acquirer offering T+1. Two years later the retailer's supplier fails, refunds spike, and the facilitator extends the cycle back to T+5 under the "change in risk" clause for three months — the terms had said it could, and the retailer's treasury had not planned for it.
Common mistakes
- Comparing providers on rate and not on cycle; two days of float on a large volume is worth more than ten basis points. - Treasury plans built on "T+2" without the clause that lets the provider extend it. - Reading the payout cycle as settlement; the scheme settled the provider earlier, and the gap is the provider's. - Facilitators offering short cycles to win merchants and funding chargebacks from their own cash. - Buyers of a payments company ignoring the float's interest income when rates are about to fall.