Stripe's New 'Pay with Balance' Fee Collection, Explained

What 'Pay with Stripe Balance' Actually Covers

Stripe has shipped a preview payment method, documented as "Pay with Stripe balance," that lets a Connect platform collect its own recurring software subscription fee directly from a connected account's available Stripe balance instead of running a card charge against it. It is scoped narrowly: Stripe's documentation states platforms can only use it to debit subscription payments for use of the platform's software, not for any other goods or services, and only funds the connected account actually earned through payment processing are eligible — balance from a top-up doesn't count. The integration currently requires the Accounts V2 preview API, and Stripe is explicit that this is a preview release, not a generally available feature.

Eligibility is tight on the account side too. The connected account must be active, controlled by the platform, and must have accepted a "full" service agreement type. It also needs both merchant and customer configurations with an active card_payments capability, and its available balance has to cover the full subscription charge or the payment fails outright.

Settlement Is Fixed, Confirmation Is the Platform's Call

Unlike a lot of Stripe's other Connect mechanics, the timing here isn't something you configure. Settlement is same-day (T+0) when the connected account is in the platform's own country, and next-day (T+1) for cross-border accounts. Confirmation is business-initiated: the platform triggers the debit on its own schedule, rather than waiting on the connected account to approve each charge the way a cardholder would. The tradeoff is on the dispute side — there's no dispute mechanism for these charges, though full and partial refunds work exactly like they do for card payments.

Consent Isn't Optional

Stripe requires platforms to collect an explicit, logged authorization from each connected account before turning this on, and it supplies suggested consent language for exactly that purpose — wording that authorizes the platform to debit the account's Stripe balance for recurring charges tied to using the platform's services. Build that consent step into onboarding or account settings before flipping the payment method on. It's a requirement, not a suggestion.

Don't Confuse It With Account Debits

Stripe already has a separate way to pull money out of a connected account's balance: Account Debits. It's easy to conflate the two. Account Debits is a Transfer+Payment construct capped at $100,000 per debit, and it's only available when the platform is responsible for the connected account's negative balances. Pay with Stripe balance carries no such cap in Stripe's documentation and runs through ordinary Stripe Billing subscriptions instead. For platforms already running Connect and billing sellers a software fee, that's the real decision point: Account Debits assumes you're underwriting the account's balance risk, while Pay with Stripe balance assumes you're simply charging a subscription against whatever balance is already there.

Sources

• Pay with Stripe balance
• Charge SaaS fees to your connected accounts
• Debit connected accounts