Separate charges and transfers

Separate charges and transfers is a Stripe Connect flow-of-funds model: the platform charges the buyer into its own balance first, then makes one or more separate transfers to move each seller’s share out afterwards. It is the Connect charge type built for a payment that belongs to several sellers at once, such as a basket with items from three shops.

How separate charges and transfers work

1. Charge. The buyer pays the platform. The whole amount lands in the platform’s Stripe balance.
2. Transfer. The platform creates a transfer to each connected account for that seller’s share, keeping its own fee.
3. Payout. Each connected account is paid out from its balance on its payout schedule.

Because the charge and the transfers are decoupled, the platform can transfer later, split one payment between several sellers, or charge before it knows which seller will fulfil the order. Stripe’s charge-type guide lists exactly those cases: transactions that “involve multiple connected accounts”, charges created “before knowing the connected account”, and funds transferred before or after the payment settles.

Separate charges and transfers vs destination charges vs direct charges

	Separate charges and transfers	Fynex split rule	Destination charge	Direct charge
Charge created on	The platform	Your existing PSP; Fynex applies the split	The platform	The connected account
Sellers per payment	Several	Several, plus partners and fees	One	One
Who writes the split	Your code computes each transfer	A per-seller rule, edited from the dashboard	Your code sets the fee	An application fee
Refunds and chargebacks hit	The platform’s balance	Traced back to the original order	The platform’s balance	The connected account
Typical fit	Multi-seller baskets, delivery apps	Multi-party marketplaces, any rail	Rideshare, rentals, single-seller marketplaces	SaaS platforms, store builders

Stripe gives DoorDash as its example of a business that needs to split payments between several parties, and it warns that separate charges and transfers “require a more complex Connect integration”, to be used “only if your business use case requires them” (Stripe).

Why it matters

The model is flexible, but the flexibility is yours to build and to carry:

• You write the split. Every transfer amount is computed in your code. Changing a seller’s terms is a release.
• You carry the liability in between. Stripe debits the platform’s balance for refunds and disputes on these charges, and the platform then reverses transfers to recover the money.
• You watch your balance. A transfer can be made before the charge’s funds are available, so the platform has to keep enough balance to cover it.
• You reconcile the legs. One charge becomes several transfers and several payouts. Matching each back to the original order is where the manual work, and the leaks, appear.

On cost, Connect’s platform-priced plan charges $2 per monthly active account and 0.25% + 25¢ per payout in the US, on top of card processing (Stripe Connect pricing).

How Fynex does it

Fynex handles the multi-seller case natively instead of stitching a charge to a chain of follow-up transfers. One incoming payment is split across many parties at once, by a standing rule per seller or per transaction. Each payout goes over the cheapest compliant rail for that recipient, and every leg posts back to the original order in Xero or QuickBooks. Stripe can stay your card processor underneath. See multi-party payments, Fynex vs Stripe Connect and split payments for platforms.