Recovery playbook
When a connected account goes negative
A negative connected-account balance is not an error state. It is a debt the account owes Stripe — and because platforms guarantee the banking relationship, Stripe’s first creditor is effectively you. Most platforms carry these debts without accounting for them, discovering them only as unexplained debits. This playbook names the four ways accounts go negative, what Stripe does about each, and the three absorption paths that follow.
Four ways accounts go negative
A reversal created after the seller paid out. A lost dispute debited after payout. A refund larger than the account’s remaining balance. An application-fee refund against an empty balance. The first two are recovery attempts gone stale; the last two are ordinary operations meeting empty accounts. All four look identical in the ledger: a negative number where zero was expected.
What Stripe does
Stripe recovers from future volume: incoming charges diverted, future transfers reduced, payouts withheld until the debt clears. Accounts can be flagged restricted while indebted, which limits their ability to trade their way out. At no point does Stripe invoice the seller’s bank — the debt exists only inside Stripe and resolves only inside Stripe.
Three absorption paths
Future volume exists. The account trades its way back to zero and self-heals; nobody notices except the seller, whose payouts ran light for a few cycles. The seller churns. The debt sits until someone writes it off; the platform ate it without ever deciding to. Explicit top-up. The platform transfers fresh funds to zero the account — occasionally correct for strategic sellers, and fine when recorded as the deliberate subsidy it is.
The accounting treatment
Carrying negative receivables at face value overstates assets. Modelled example: a $90 negative with roughly 60% probability of future volume is about $54 of expected recovery — book the write-down honestly rather than carrying $90 forever. The discipline costs one journal entry and buys a balance sheet finance can defend.
Prevention, and what FeeGuard does
Payout schedule versus detection latency is the lever most platforms never examine: slower payouts widen the window in which reversals reach live balances. FeeGuard findings raised while balances are positive are the whole point of real-time monitoring; when they land late anyway, the queue separates recoverable from nettable from write-off so the negative-balance path stays a deliberate decision rather than a slow surprise.
Common questions
Will payouts pause while the account is negative?
Payouts can be withheld against the debt until it clears, which is exactly why active sellers self-heal and dormant ones never do. Plan cash-flow conversations accordingly.
Can we see negative balances in the API?
Yes — an account balance reads negative. Monitoring it per-account is cheap; being surprised by it at close is expensive.
Should we top up strategic sellers?
Sometimes — keeping a high-performing seller trading beats letting them drown in a debt partly caused by your refund bug. Record it as the deliberate subsidy it is.