The Platform Refund Ledger

The complete mechanics of Stripe Connect refunds, reverse transfers, and application fees

FeeGuard · First edition · August 2026

---

Who this book is for

If you run payments on a Stripe Connect platform — a marketplace, an on-demand service, a SaaS product paying out to sellers or providers — this book is the reference your finance team and your engineering team can both keep open in a tab. It answers one question exhaustively: when money moves backward on Connect, where does it come from, who ends up paying, and how do you prove it from the records Stripe gives you?

Nothing here is about getting refunds approved or writing dispute narratives. It is about the plumbing: which objects exist, which parameters decide who absorbs a refund, what each balance transaction line means, and how to reconcile all of it by hand before you trust any tool — including ours — to do it for you.

How to read it

Chapters 1 through 6 are mechanics. They build in order: the object model, refund paths per charge type, transfer reversals, application fees, disputes, and then chapter 6, the flags-and-defaults matrix that compresses all of it into one truth table. Chapters 7 through 10 are practice: reading balance transactions as ground truth, running a 90-day self-audit, closing a month, and designing a refund policy deliberately instead of inheriting one from missing flags.

Every chapter opens with the question it answers, works its numbers in front of you, and closes with a short list of what to check on your own platform. Those lists accumulate into Appendix A. Every object name, parameter name, and event name in this book matches Stripe's official documentation, cited inline; Appendix B is the glossary of everything used.

Where the numbers come from

This book contains no survey statistics, no industry benchmarks, and no customer anecdotes. Every figure is either derived arithmetically from a stated starting point, or quoted from Stripe's documentation with a citation. The worked examples use constructed round amounts on a fabricated platform so the arithmetic is easy to follow; they are illustrations of mechanics, not reports of anyone's actual results. Where a claim depends on your account configuration rather than on Stripe's defaults, the text says so.

A note on scope

Stripe's documentation is the authority on its own behavior, and it changes. Citations in this edition point to the live pages as of August 2026. If Stripe's docs and this book ever disagree, check the date on both, then trust Stripe's current page and re-derive the arithmetic — the method survives every API revision even when details move.

Independence

FeeGuard is an independent product and is not affiliated with, endorsed by, or sponsored by Stripe, Inc. "Stripe" and "Stripe Connect" are trademarks of Stripe, Inc., referenced descriptively.

Contents