stripedunninginvoluntary churncustomer balanceinvoicing

Stripe Can Now Aim a Customer Credit at the One Invoice That's About to Trigger a Cancellation

Before Nov 18, a Stripe credit always waited for the next invoice. Now you can point it at the open one keeping a subscription on life support.

XY
20 November 2026 · 8 min read

Our Stripe dunning guide covers the mechanics of retrying a failed payment. What it doesn't cover — because the API didn't support it until last week — is what happens when you want to rescue a specific invoice with a credit instead of a card charge. Say a subscriber's renewal invoice is three retries deep and about to trigger a cancellation, and your support team wants to apply a $40 goodwill credit to get it paid before that happens. Before November 18, you couldn't do that. The credit would go onto the customer's balance and wait for the next invoice. The one actually at risk kept retrying, untouched, on its own clock.

Key stat
9%
Of MRR the average subscription business loses to involuntary churn from failed payments
Source: Baremetrics

That 9% is the budget this feature is quietly fighting for. Not all of it — most involuntary churn resolves through retries alone, or never resolves at all because the card is genuinely dead. But a meaningful slice sits in a specific gap: invoices that could be collected right now, with money the business has already decided to credit the customer, if only that credit could land on the right invoice at the right time.

What actually shipped on November 18

Stripe added a new type to the Customer Balance Transaction object: applied_to_invoice. Create a balance transaction with that type and pass the invoice's ID in applied_to_invoice.invoice, and the amount reduces that invoice's outstanding balance directly. It doesn't touch the customer's general balance at all — it's scoped to one invoice, applied once, and reflected immediately on that invoice's amount_remaining.

Alongside it, Stripe added a customer_balance property to the Invoice object (and to QuotePreviewInvoice), which breaks the applied amount into three numbers: how much balance got applied automatically at finalization, how much got applied manually afterward, and the total of both. Before this, if you wanted to know whether a paid invoice had been settled by a card charge or partly by credit, you had to reconstruct it from the customer's balance transaction history. Now it's a field on the invoice itself.

The gap this closes

Every Stripe integration that issues credits — refund-to-credit conversions, loyalty credits, downgrade prorations, support-issued goodwill — has always had exactly one native destination for that money: whatever invoice Stripe finalizes next for that customer. If the customer's account is healthy, that's a minor inconvenience; the credit shows up on next month's bill instead of this one, nobody notices. If the customer has an invoice open right now that's failing, mid-retry, and heading toward a pause or cancellation, that same behavior means the credit arrives too late to help the thing it was meant to fix.

ApproachWhat happens to the at-risk invoiceTradeoff
Issue a credit, let it auto-applyNothing — the open invoice keeps retrying on its own scheduleSimplest API call, but the credit does zero work until a future invoice exists
Void the open invoice and reissue with credit includedResolved, but as a new invoice objectBreaks invoice numbering continuity and complicates revenue recognition, since the original invoice never gets marked paid
Apply balance directly with applied_to_invoiceResolved on the original invoice, same invoice IDOne extra API call, but the invoice record stays intact and dunning stops the moment amount_remaining hits zero

That middle row is the workaround most teams actually used, because it was the only one that reliably worked. Voiding and reissuing is a blunt instrument — you lose the paper trail of the original failed attempts, your accounting team has to reconcile an invoice number that effectively vanished, and if anything downstream keys off invoice IDs (a CRM sync, a dunning-metrics dashboard, an audit log), that integration now has a gap to explain. Teams that didn't want that mess mostly just let the credit sit and hoped the retry succeeded on its own before the subscription got canceled. Sometimes it did. The cases where it didn't are exactly the ones this feature was built for.

What automated dunning recovers — and what's left over
MRR lost annually to failed payments9%
Typical automated retry recovery rate50%
Churn reduction from optimized retry timing17%

Sources: Baremetrics (MRR lost to failed payments); Paddle payment recovery research (retry recovery rate, churn reduction from optimized retries)

A 50% automated recovery rate still leaves half of failed invoices unresolved by retries alone. Some of that half is genuinely dead — a canceled card, a closed account, a dispute that's never getting paid. But some of it is a customer your retention team has already decided is worth keeping, sitting on an invoice that a $20 or $40 credit would clear outright, if the credit could reach it. Until now, it couldn't.

Where this actually earns its keep: mid-dunning retention offers

This connects directly to automatic pause-on-payment-failure, which Stripe shipped in September. That feature lets a subscription pause instead of cancel when a renewal invoice fails, and resumes automatically once the triggering invoice is paid. The two features compound: a subscription sitting paused because of a failed invoice is exactly the scenario where applying a credit directly to that invoice matters most, because clearing it doesn't just stop dunning — it's the specific trigger that resumes the subscription. Before applied_to_invoice existed, a support agent offering a goodwill credit to a paused customer had no way to make that credit do the one thing the customer actually needed: pay off the invoice holding their subscription hostage.

The same logic applies to retention offers that were never about payment failure in the first place. A customer threatening to cancel over a billing dispute, a downgrade credit issued mid-cycle while a prior invoice is still open, a "we'll cover this month" save offer from your cancellation flow — all of these generate a credit that, until now, had no reliable way to land on the invoice the conversation was actually about. Our piece on Stripe's invoice item credit hold covers a related but opposite problem: making sure a credit doesn't post before the invoice it offsets is paid. This is the other side of that coin — making sure a credit can post exactly where you want it, the moment you decide it should.

What to check in your integration

  • Find every place you create a credit balance transaction and ask what it's actually for. If the credit is meant to resolve a specific open invoice — a retention save, a dispute resolution, a goodwill gesture tied to a failed payment — switch that call to type: 'applied_to_invoice' with the invoice ID, instead of a generic credit that floats to whatever invoice comes next.
  • Apply the full amount owed, not just a token credit, if stopping dunning is the goal. A partial application reduces amount_remaining but leaves the invoice open and still retrying on the balance. If the point is to resume a paused subscription or stop a cancellation countdown, the credit needs to cover what's left, not just soften it.
  • Retire your void-and-reissue workaround for this specific case. If you built a process around voiding an open invoice to apply a credit, that process now creates more reconciliation work than it saves. Keep it for cases that genuinely need a different invoice (a pricing error, a wrong line item) and route straightforward "apply this credit to this invoice" cases through the new type instead.
  • Add the customer_balance breakdown to your dunning dashboard. Knowing how many of your "recovered" invoices were actually paid by credit versus by a successful charge tells you something your recovery-rate metric alone doesn't — whether your retry schedule is working, or whether your support team is quietly doing the recovering.

None of this changes whether a given credit was the right call — that's still a retention-strategy decision, not an API one. What it changes is whether the decision, once made, actually reaches the invoice it was meant for. A cancellation flow that offers a discount or a credit to a subscriber on their way out is only as good as Stripe's ability to apply that offer to the bill currently causing the problem, and until last week, it often couldn't. If you want to put a number on what even a modest improvement in invoice-level recovery is worth against your current involuntary churn, our churn calculator is a quick way to size it before you go rewiring your credit-issuance code.

Frequently asked questions

What is Stripe's applied_to_invoice type for customer balance transactions?+

It's a new type value you can pass when creating a Customer Balance Transaction. Set type to applied_to_invoice and pass the target invoice's ID in applied_to_invoice.invoice, and the credit reduces that specific invoice's outstanding amount immediately instead of sitting in the customer's balance until their next invoice is finalized. Stripe shipped it in the 2026-11-18 API version.

Could you apply a customer's account balance to an invoice before this update?+

Only automatically, and only to a future invoice. A credit balance transaction would sit on the customer object and get netted against the next invoice Stripe finalized for them — you had no way to direct it at an invoice that was already open. The only workaround for an invoice already in flight was to void it and reissue it with the credit baked in, which breaks invoice numbering continuity and complicates revenue recognition.

Does applying a balance to an open invoice stop Stripe's dunning retries?+

If the applied amount brings the invoice's amount_remaining to zero, yes — Stripe marks it paid, which ends the retry schedule for that invoice the same way a successful card charge would. A partial application reduces what's owed but leaves the invoice open and still subject to retries on the remainder, so you have to apply enough to actually clear it if your goal is to stop a payment-failure pause or cancellation.

How do I see how much of an invoice was paid by credit versus by card charge?+

Check the new customer_balance property on the Invoice object. It breaks out the amount applied automatically at finalization, the amount applied manually afterward, and the total applied — so your reconciliation doesn't have to infer credit usage from the gap between the invoice total and the charge amount.

Try CancelFlow

Stop losing subscribers today

One script tag. One function call. A live cancellation flow in under 10 minutes.

Start free trial →
← All postsHome