Stripe Integration for Food Delivery Platforms

A single food delivery order routes money to at least three parties — the restaurant, the driver, and your platform's commission — often on three different payout schedules. Stripe Connect handles the splitting mechanics, but the order in which those splits are calculated and the account structure behind each party determines whether a partial refund or a driver reassignment mid-delivery breaks your reconciliation.

Split-Payment Edge Cases That Actually Happen at Volume

• A driver is reassigned mid-order — does the original driver keep a partial payout for distance already covered?
• An order is partially refunded (one item missing) — restaurant, driver, and platform shares all need re-splitting, not a flat refund
• Tips need to route entirely to the driver, bypassing the platform commission calculation
• Instant payouts to drivers vs. daily/weekly batched payouts to restaurants are usually different Connect configurations

We build the split logic as an explicit, testable calculation step — not something implicit in how transfers happen to fire — specifically so partial refunds and reassignments recalculate correctly instead of requiring manual reconciliation. At delivery-platform order volumes, a splitting bug that only shows up 1% of the time is still a daily support and finance headache.