Understand that negative balances on connected accounts occur when refunds, disputes, or transfer reversals exceed the account's Stripe balance.
Check controller.losses.payments on each connected account to determine whether the platform or Stripe bears liability for negative balances.
Monitor account.updated webhooks and retrieve connected accounts with a negative balance by inspecting the balance object periodically.
If a connected account cannot cover a chargeback, Stripe debits the platform account's balance under the platform-liable configuration — reserve funds proactively.
Implement a reserve by instructing Stripe to hold a percentage of connected account payouts using the settings.payouts.debit_negative_balances flag or by manually delaying payouts.
Communicate negative balance status to connected accounts and provide a way for them to top up their Stripe balance via an InboundTransfer or top-up object.
Known gotchas
Once the platform's balance is debited for a connected account's negative balance, recovering those funds from the connected account is the platform's operational responsibility — Stripe will not pursue the merchant.
Enabling debit_negative_balances on a connected account allows Stripe to debit the connected account's external bank account to cover shortfalls — ensure connected accounts consent to this.
Platforms in high-dispute-rate verticals should model expected chargeback losses and size reserves accordingly before launching.
Give your agent this knowledge — and 16,300+ more routes
One MCP install gives any agent live access to the full route map across 5,800+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?