← Files GitBookARCHIVED FILE

references/example-site/connections/blog/same-day-payouts-tradeoffs.html

1.64 KB · Oct 4, 2026 · 12:04 UTC

↓ Download file

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<title>Same-day payouts: when 0.4% is worth it (and when it isn't) — Evolve Blog</title>
<meta name="description" content="A practical guide to evaluating whether same-day payouts make sense for your business — with the math behind the decision.">
<meta name="author" content="Priya Shah, Product Manager, Payments">
<meta property="article:published_time" content="2026-01-22">
<meta name="keywords" content="payouts, same-day, cash flow, enterprise">
</head>
<body>
<article>
<header>
<h1>Same-day payouts: when 0.4% is worth it (and when it isn't)</h1>
<p>By Priya Shah, Product Manager, Payments — January 22, 2026</p>
</header>
<p>Same-day payouts went GA on Enterprise plans this month: hit a button, your settled balance lands in your bank within hours instead of next business day, for a 0.4% premium per transfer. The customers who pre-ordered the feature broke down into two clear groups. One group was platforms with seller-facing payout SLAs — they'd been paying for early-payout APIs from third-party providers and saving money switching to native. The other was finance teams running tight on working capital who could put 24 hours of float to better use than the fee cost.</p>
<p>For most teams, the standard next-day payout is still the right default. The math only flips in your favor when working-capital cost exceeds 0.4% on the relevant horizon — high-velocity businesses, platforms passing payouts to sellers, or teams in a brief cash crunch. Configure under <strong>Settings → Payouts</strong> if you want to experiment per-transfer rather than always-on.</p>
</article>
</body>
</html>

SHA-256: e4695d4bfb05ac1f72c22ecbd5bd474e888c1f2195b777ae9d8dc7669a8a4765