Image
Build
Connect & operate
Design & teams
Start hereScope a build in one callBring a spec, a wireframe, or a paragraph. You leave with an architecture, a timeline, and a number.Request a scoping call
AI software
LLM & data systems
Vibe coding
Ready to ship?Put AI where the work isAgents, RAG, and private LLMs wired into the systems your team already uses — not a chatbot bolted to a homepage.Discuss an AI project
Domain firstWe learn your workflow before we model itRegulated, operational, or high-volume — the constraints belong in the schema, not in a training doc.Talk about your domain
Timothy Carter
Author
Building a Stripe Connect Marketplace That Reconciles Cleanly — featured image
11/18/2026

Building a Stripe Connect Marketplace That Reconciles Cleanly

A Stripe payout is not a day's sales. It is a net figure: card charges minus Stripe fees, minus refunds, minus application fees, minus disputed amounts and reserves, settled on a schedule that lands in your bank a day or two later.

Treating that deposit as revenue is how marketplace books drift. The fix is a double-entry ledger that records every money movement the moment a charge is created, not when cash arrives.

Three architectural decisions govern whether the ledger reconciles cleanly: the Connect account type, the charge model, and how application fees and refunds are booked against the connected account's balance.

Three Numbers That Set the Context for Connect
1.4
2024 Stripe TPV
38
TPV growth YoY
1.3
Share of global GDP
Stripe's 2024 total payment volume, its year-over-year growth, and its approximate share of global GDP. Source: Stripe, 2025

Pick the Account Type That Fits Your Compliance Appetite

Connect offers three onboarding shapes: Standard, Express, and Custom. Standard hands the connected account a full Stripe Dashboard and most of the KYC and tax-form burden; the platform has the lightest build and the least control over the seller experience. Express splits the difference. Stripe handles identity verification and payouts UI, and the platform owns the surrounding product through embedded components. Custom gives the platform full API control and full responsibility for KYC refreshes, dispute handling, 1099-K data, and negative-balance recovery.

The choice looks like a product decision. It is really a compliance one. If sellers are US sole proprietors on Custom accounts, the platform is responsible for the 1099-K filing. Stripe generates the form from the payment objects, but the reconciliation has to prove the number. Firms building this for the first time usually underestimate how much the Custom path resembles a custom banking software stack: identity, ledger, reporting, dispute workflows, and audit trails.

Charge Flows Shape the Ledger You Will Have to Build

Connect exposes three charge patterns and the ledger shape follows the pattern, not the other way round. Direct charges put the connected account's statement descriptor on the cardholder's bill and leave the Stripe fee on the seller; the platform takes an application_fee_amount. Destination charges put the platform on the hook as merchant of record and move funds to the connected account on the same transaction, net of the application fee. Separate charges and transfers decouple collection from payout, which you need the moment one customer order fans out to multiple sellers.

Each flow produces different objects in the Stripe API: charge, application_fee, transfer, payout, balance_transaction. The ledger has to subscribe to that vocabulary rather than invent its own. The balance_transaction id is the atomic unit of reconciliation; treat it the way an accounting system treats a GL line.

The Double-Entry Model That Survives Reconciliation

A marketplace without a double-entry ledger will reconcile for a while, then stop. Every movement touches two accounts: a customer payment creates a liability to the seller and a receivable from Stripe; a payout clears the Stripe receivable and credits a bank clearing account; a chargeback reverses the first entry and creates a dispute reserve. Model charges, refunds, transfers, application fees, and disputed amounts as journal entries keyed by balance_transaction.id, with the connected account id as a dimension on every row.

Isolating seller balances is the point. The same reasoning that drives tenant isolation in SaaS applies here: a single query should rebuild any seller's balance history without reading another seller's rows. Pick Postgres with partitioned ledger tables or a purpose-built double-entry library; do not try to recover this from an orders table and a webhook log.

Open green ledger book with fountain pen, magnifying glass, and two columns of coin stacks

Where the Drift Hides in a Single Payout

The worked example Stripe publishes in its marketplace guide is the cleanest way to see how a charge actually resolves. A $100 customer payment yields a $97.50 transfer to the seller after the platform's Stripe fees and application fee are deducted. Refunds, disputed charges, and cross-currency conversions are what pull the real number away from that tidy sum, and they are what turn a weekly reconciliation into a monthly fire drill.

Three traps show up in practice. Refunds reverse the charge but do not refund the Stripe processing fee, so an explicit fee-retained account is required or the seller balance drifts by a few cents per transaction. Disputes debit the connected account's balance by the dispute amount plus a $15 network fee, held until the case closes, and when the seller's balance cannot cover it, Stripe debits the platform. Instant Payouts and cross-border transfers charge a volume fee that must land on its own ledger line, not be smeared into the processing fee.

Reserves, Disputes, and 1099-K Reporting

Dispute volume is the single variable most likely to blow up the reconciliation model. Chargebacks911's 2024 field report found that 83.4% of merchants reported increases in friendly-fraud chargebacks last year, with friendly fraud now representing roughly 43.8% of their disputes. Platforms need Radar rules, a reserve policy, and the ability to garnish a seller's upcoming payouts against unresolved disputes. Stripe Radar is trained on more than 70 trillion data points across the network, which is useful for triage but does not remove the platform's obligation to reconcile the money.

Tax reporting is the quieter risk. The IRS set a Form 1099-K threshold of $5,000 for tax year 2024 payments through third-party platforms, phasing down toward the American Rescue Plan's original $600 line. On Custom accounts, the platform owns the filing, which means the ledger must be able to produce seller-level gross volume by calendar year, excluding refunds that landed in the same year, and reconcile the result to Stripe's generated form before it goes out.

Where the Take Rate Lives in the Books

The application fee is not platform revenue when the charge posts. It is a receivable from Stripe that converts to revenue only when the payout settles. Marketplaces that book it as revenue on the charge end up restating when refunds and disputes arrive, which they always do. The size of that receivable is a function of the platform's take rate, and take rates vary enormously by category.

Marketplace Take Rates, FY2025
Marketplace Take Rates, FY2025Fiverr: 40.2%; Lyft: 31.9%; Uber: 26.9%; Etsy: 24.2%; Upwork: 19.6%; Airbnb: 13.4%; DoorDash: 13.4%1Fiverr40.2%2Lyft31.9%3Uber26.9%4Etsy24.2%5Upwork19.6%6Airbnb13.4%7DoorDash13.4%
Revenue divided by gross volume, FY2025. Source: Platform Take Rates analysis, 2026

Rates in that range are also why platforms grow interested in embedded financial products once volume climbs. The B2B shift is real: McKinsey's B2B Pulse research reports 65% of B2B companies now offer e-commerce, up from 53% in 2021, with online channels generating 34% of revenue for those that do. Connect's monetization shelf (Instant Payouts, Issuing, Capital) is designed to be sold into that volume, and each product adds its own ledger surface.

What to Watch After You Ship

The number worth watching is the unexplained variance between the sum of Stripe balance_transaction rows for a payout window and the amount of the actual payout. If that variance is zero to the penny, the ledger is doing its job. If it is anything else, the reconciliation is broken and you have hours, not weeks, to find the missing journal entry before the next payout masks the first. Teams that cannot answer this on demand, for any seller and any week, are the ones that discover a six-figure drift during an audit. Dev.co's engineering practice treats this variance as the health metric for every marketplace build, and it is the first thing to instrument before the first live charge, not after. The API integration surface and the first 90 days with a new vendor are both won or lost on that one number.

Author
Timothy Carter
Timothy Carter is the Chief Revenue Officer. Tim leads all revenue-generation activities for marketing and software development activities. He has helped to scale sales teams with the right mix of hustle and finesse. Based in Seattle, Washington, Tim enjoys spending time in Hawaii with family and playing disc golf.