Payouts are the half of marketplace payments nobody writes about: collecting money is a solved problem, but getting it to thousands of sellers — legally, reconciled, with the right tax forms — is where marketplace architectures earn or lose their keep. I built this for a creator marketplace paying sellers worldwide across card and ACH rails; here is how the pieces actually fit.
The three-layer payout architecture
- Your ledger decides. Who is owed what, when it became payable, what is held in escrow, what is reserved against disputes. No payout executes except from a ledger balance — the ledger guide covers keeping that truthful.
- A disbursement provider executes. A MassPay-style provider takes payout instructions and moves money across rails — ACH, push-to-card, and international options — handling bank failures, retries, and recipient onboarding so you are not building bank integrations per country.
- An FBO structure holds. Between collection and disbursement, seller funds sit in an account a licensed partner holds for the benefit of your sellers. Your platform directs movements; it does not own the funds. That separation — platform as bookkeeper and instructor, partner as holder — is what keeps the money-transmission question answered correctly.
The design intent throughout: the platform touches instructions and records, the regulated entities touch money. Get that division right, with counsel reviewing the actual fund flows, and the structure scales; blur it, and growth converts directly into regulatory exposure.
The tax-form layer
Every payout program has three tax questions with exactly one correct time to answer them — before the first payout:
- Who is the settlement entity for 1099-K purposes? Processor-settled flows usually carry processor reporting; restructure the flow and the obligation can move with it.
- Who generates payout tax forms? Disbursement providers often offer 1099 generation and e-filing for recipients they pay. If it is you, W-9/W-8 collection belongs in seller onboarding, not in a December scramble.
- What thresholds apply this year? Reporting thresholds have moved repeatedly. Encode them as configuration, expect them to change, and let your ledger produce the numbers — if tax season requires spreadsheet archaeology, the ledger was not doing its one job.
Field notes
- Payout failures are a state machine, not an error. Wrong account numbers, closed accounts, name mismatches — a few percent of every payout run. Model instructed → sent → settled → failed → returned explicitly, with ledger reversals for the returns path. The marketplaces that suffer are the ones treating returns as exceptions.
- Instant payouts are a pricing feature. Push-to-card costs more per transaction; sellers happily pay a fee for speed. Standard-free, instant-paid is the pattern that funds the whole payout program.
- Reserve before you regret. Dispute windows outlive payouts. A reserve policy (rolling percentage or days-held) encoded in the ledger from day one beats clawing back money from sellers who already spent it.
None of this needs to become your specialty. Payout architecture is a solved problem when someone who has operated one designs yours. That is a platform engagement, or a 90-minute clarity call if you want your current design pressure-tested first. For the legal structure itself, bring counsel — I design the flows; lawyers bless them.
Frequently asked questions
What is an FBO account and why do marketplaces use one?
An FBO (For Benefit Of) account is a bank account a licensed partner holds for the benefit of your sellers: funds sit legally with the regulated entity, not on your balance sheet, while your ledger tracks whose money is whose. Structured properly with the right partner, it keeps the platform from holding customer funds directly — which is the line where money-transmission licensing questions begin. The structure only works as well as the ledger behind it, and it needs real legal review, not a blog post's assurance.
Who sends the 1099s for marketplace seller payouts?
It depends on who is the settlement entity. Payment processors handle 1099-K reporting for transactions they settle; disbursement providers often take on 1099 generation for payouts they execute; and platforms that structure flows outside those paths can inherit the obligation themselves. The reporting thresholds have also changed repeatedly in recent years. Decide who owns each form before your first payout — retrofitting tax reporting in January is a miserable project.
What payout rails should a marketplace support?
Match rails to your sellers, not to a feature list: US-heavy bases run on ACH with debit-card push for the impatient; international bases need local rails or a provider that abstracts them. Every added rail adds failure modes and reconciliation surface, so start with the two rails covering 90% of sellers and expand only when sellers actually ask.
Written by Andrej Dragojevic, Stripe Certified Professional Billing Architect.