Re-run payout unit economics before your next payroll

The reprice rewards boring rails

Before the next payroll or vendor run, re-cost each payout flow that leaves through Stripe Global Payouts. Between Oct 26, 2026 and Nov 2, 2026, Stripe replaced a $1.50 flat fee for local bank, debit, and international payouts with 50 free monthly domestic payouts and rail fees of $0.50 or $1.00 for ACH, $2.50 for RTP, and $25 for Fedwire.

Global Payouts lets businesses pay recipients in over 160 countries through a single API, with bank transfers, international wires, and stablecoins available, and recipients do not need Stripe accounts.

Debit-card payouts are 0.75% plus $1.50, stablecoin payouts are $0.50 plus 0.5%, and a 0.05% platform fee applies to Global Payouts volume above $1M per month.

Stripe also removed the $2.00 per-wire funding option from Treasury's Receive funds, leaving only free ACH funding shown.

By October 2026, Stripe had paid more than $1 billion to over 3,400 vendors in the US and UK using Global Payouts.

At that scale, the reprice is a unit-economics problem. The same product can be cheaper for one payroll batch and more expensive for another contractor corridor.

The expensive flows hide in speed, volume, and disputes

Low-volume domestic ACH is the likely winner. If a flow stays inside the free domestic allowance, the payout fee can be close to zero. If it crosses the allowance, the per-rail ACH fee can still sit below the old flat charge.

Instant speed is the likely loser when same-day money is expected. RTP is now a priced option, not a default. Compare it against a standard rail that arrives later but costs less, and decide whether the speed is worth the extra cost per payout. If not, move the run to the slower rail or adjust timing.

High volume changes the math even when the per-payout fee looks fine. If a flow is near the platform-fee line, model the excess separately. A small percentage on the overage can erase a per-rail saving that looked clean at lower volume.

Corridor matters because the same rail can behave differently across countries. A local bank transfer in one corridor may be cheap, while an international wire in another can carry a different fee. That keeps the re-cost honest when a single product hides several cost structures.

Disputes are the hidden line item. Each appealed dispute carries a $15.00 fee, and Stripe does not refund it even when you win; network fees can also apply. If a corridor has a high appeal rate, add that cost to the payout cost, not to support overhead. A payout that looks cheap can become expensive when the recipient contests it.

Funding path is the quiet multiplier. If your money enters through Treasury, check whether the funding route changed your total cost. The payout fee starts after the money is in, so a changed entry path can move the whole unit cost.

The re-cost sheet belongs before the run

Use the flow, not the average payout, as the unit. A payroll batch, a vendor corridor, a contractor group, or a partner settlement each has a rail, a speed, a monthly volume, a dispute pattern, and a funding path. The new pricing touches all of them.

Keep the checklist below. The first three items are the core re-cost. They force you to compare the same payout under the old and new structure, not the dashboard average. The sheet is built to take a few minutes per flow, not an afternoon, and the items are ordered so you can stop early when a flow is clearly safe.

• Name the rail, speed, corridor, monthly volume, dispute-appeal rate, and funding path for each payout flow.
• Record the old per-payout fee and the new per-rail fee for the same flow.
• Multiply by monthly volume to get old and new monthly cost.
• Add funding-path costs where the money enters Stripe Treasury before payout.
• Add dispute-appeal costs where appeals are common.
• Mark flows where instant speed, high volume, or appeals erase the savings.