Stripe's Billie Payment Method Guarantees Your First B2B Invoice. It Doesn't Renew Itself.
Stripe added Billie, a B2B BNPL method, on August 26. Its own docs call it single-use — here's what that means for your second invoice.
Stripe quietly added Billie as a supported payment method on August 26, 2026, pinned to API version 2026-08-26.dahlia, with support for both one-off invoices and subscriptions. If you sell B2B SaaS on net terms and have ever chased an unpaid invoice through someone else's accounts payable queue, this looks like exactly the fix you've been waiting for: a payment method that pays you in full on day one and hands the collections risk to somebody else. It mostly is that fix — for the invoice it's attached to. The part worth slowing down on is what "attached to" actually means here, because Stripe's own documentation puts a label on Billie that changes the whole calculation for a subscription business: single-use.
That's the demand side of why this matters. Trade credit isn't a nice-to-have anymore — TreviPay's 2026 buyer research found it jumped from the 17th most important factor in supplier selection to the first, among buyers who've considered switching suppliers over payment terms alone. A B2B SaaS company that can't offer flexible terms is increasingly competing with one hand tied behind its back. Billie is Stripe's answer to that demand, and it's a real one: Billie is already Germany's market leader for B2B BNPL, with more than 200,000 registered business buyers in that market alone, and per-transaction credit limits that partner integrations put anywhere from the tens of thousands of euros up past €100,000 depending on the buyer's credit profile. None of that is in question. What's in question is whether it does anything for your second invoice.
What Billie actually does at the moment of payment
Mechanically, Billie is a real-time underwriting decision wrapped around a checkout. The buyer selects Billie, Stripe redirects them to Billie's flow, Billie runs an instant credit and fraud check against that specific business buyer for that specific transaction, and — if approved — the buyer gets 7 to 120 days to pay while Stripe settles the full amount to the merchant right away. Stripe's integration guidance for merchants even recommends passing detailed line_items data on the transaction specifically because it improves Billie's approval rate, which only makes sense if you understand that every transaction gets its own decision. There's no persistent "Billie account" on the merchant's side that, once opened, silently approves everything that comes after it.
That single-transaction design is exactly what shows up in Stripe's payment method documentation: Billie is categorized alongside certain bank transfer methods as single-use, meaning it can't be attached to a Stripe customer object and reused. A saved card sits on file and gets charged again next month with zero customer involvement. A single-use method is consumed the moment it's used — there is nothing left to charge automatically when the next billing period rolls around.
Why this is a different problem than your net-terms invoice already has
We've written before about why an unpaid net-30 invoice fails differently than a declined card — no decline code, no webhook, just an invoice that quietly ages inside a customer's AP queue for weeks. Billie genuinely removes that specific failure mode for the invoice it approves: the merchant isn't waiting on the buyer's AP process at all, because Billie already paid. But swap "will my customer's finance team eventually pay this?" for "will Billie approve this specific renewal invoice?" and you've traded a slow, visible risk for a fast, invisible one.
| Billing method | Who bears default risk | When merchant gets paid | Recurring-capable on Stripe |
|---|---|---|---|
| Card (auto-charge) | Merchant, via chargeback exposure | On successful charge | Yes — stored token, default Billing rail |
| ACH direct debit | Merchant, until return window clears | After return window closes | Yes — stored mandate |
| Net-30 invoice (send invoice) | Merchant, for the full DSO period | Whenever customer's AP pays it | N/A — no charge to retry |
| Billie (B2B BNPL) | Billie, for the approved invoice | Within ~1 business day | No — single-use, re-approved each time |
Look at that last row carefully. Billie doesn't fail the way a card or an invoice fails — it doesn't decline with a code, and it doesn't age unpaid. It either approves the transaction or it doesn't, in real time, based on a credit decision Stripe and the merchant don't control. For a one-time purchase, that's a clean trade: you either get paid today or the buyer pays some other way. For a subscription, it means every renewal is a fresh credit application that the account passed once and now has to pass again — possibly a year later, possibly after the buyer's own financial position has changed in ways neither you nor Billie can see coming until the exact moment of the renewal charge.
The mechanism this shares with — and how it differs from — other "checkout only" payment methods
This isn't the first time a Stripe payment method expansion has looked like a renewal fix and turned out to be a checkout fix. We saw the same shape when Stripe added six Southeast Asian wallets in August that convert beautifully at signup and, for most of the batch, can't be stored and rebilled at all. The failure mode there is architectural — the payment rail was never built with a storable token. Billie's limitation is different in kind: it's not that Stripe hasn't wired up the plumbing yet, it's that reusability would defeat the point of what Billie is actually selling. A stored, always-approved BNPL credential would mean Billie underwrote a customer's creditworthiness once and then extended unlimited future credit on that single decision — no BNPL provider operates that way, because the entire business model depends on re-checking the buyer every time real money changes hands.
That distinction matters for how you plan around it. A missing recurring token for a wallet payment method is a Stripe roadmap gap that might close in a future release. A single-use design for a credit product is closer to a permanent feature of how buy-now-pay-later works — don't build a plan that assumes Stripe will eventually make Billie "sticky" the way a card is.
Source: TreviPay, "B2B Sales Strategy: Where Buyers Say Sellers Are Falling Short in 2026"
The jump from 28% to 49% in three years tells you demand for exactly this kind of flexibility is accelerating, not plateauing — which is the honest case for turning Billie on even knowing its limits. Offering it at signup or at contract renewal time can win or keep a deal that a card-only or invoice-only checkout would lose. The mistake is treating "we accept Billie" as equivalent to "we solved our net-terms collections problem," the way we've cautioned against treating a new checkout payment method as automatically renewal-safe.
What to actually do if you turn Billie on
1. Treat every renewal as a new approval event, not a formality
Build your renewal workflow assuming Billie might say no this time even though it said yes last time. That means having a fallback collection path ready — a card on file as backup, or a direct invoice with your own terms — before the renewal date, not after a decline you didn't expect.
2. Don't let a Billie decline look identical to a support problem
A declined Billie authorization at renewal isn't a technical failure and it isn't (necessarily) a sign the customer doesn't want to renew — it's a credit decision made by a third party about that specific transaction. Route it to whoever owns renewal collections, the same way you'd route a hard decline code differently than a soft one, rather than letting it sit in a generic "payment failed" queue with no context on why.
3. Keep a secondary payment method on file regardless
Because Billie can't be stored, you have no fallback unless you separately capture one. Ask for a card or bank account as a backup at signup, the same advice that applies to any single-use or non-recurring method — it's the difference between a renewal hiccup you can immediately route around and one that turns into a silent lapse.
4. Segment involuntary churn reporting by payment method, including Billie
A Billie-declined renewal, a card decline, and an unpaid net-30 invoice are three different failure mechanisms with three different fixes. Lumping them into one "involuntary churn" bucket, the mistake we've flagged before with involuntary churn generally, hides which lever actually needs pulling. If Billie renewals are declining at a meaningfully higher rate than your card renewals, that's a segment worth tracking on its own, not folding into an aggregate number.
Where this leaves the pricing and risk decision
Billie is a genuinely good option for the specific problem it solves: getting paid in full, immediately, on an invoice you'd otherwise have to chase through someone else's finance department. It is not a subscription payment method in the sense a card or a stored ACH mandate is, and Stripe's own single-use classification says so plainly. The businesses that will get the most out of it are the ones that use it for what it's built for — a strong first invoice, a strong annual renewal invoice handled as its own event — while keeping a real fallback collection method in place for the renewals it doesn't approve.
If you're weighing whether Billie changes your involuntary churn exposure, run your current invoice-billed segment through our churn calculator with and without a renewal-decline scenario modeled in — a payment method that removes DSO risk on the invoices it approves can still leave a gap on the ones it doesn't, and that gap behaves a lot more like a payment-rail-specific dunning problem than like ordinary AR collections. And whatever share of your renewals end up running through Billie, a cancellation flow that catches the accounts who do reach the point of leaving on purpose still matters just as much — a credit-risk transfer on the invoice side doesn't do anything for a subscriber who simply decides not to renew.
Frequently asked questions
What is Stripe's Billie payment method?+
Billie is a B2B buy-now-pay-later provider that Stripe added as a supported payment method on August 26, 2026 (Stripe API version 2026-08-26). It lets a business buyer pay an invoice on 7–120 day terms while the merchant gets paid in full upfront. Billie runs a real-time credit check at the moment of purchase and assumes the default and fraud risk itself — if the buyer never pays, that loss is Billie's, not the merchant's.
Does Billie support recurring or subscription billing on Stripe?+
No. Stripe's own documentation classifies Billie as a single-use payment method, the same category as certain bank transfers — it can't be attached to a customer object and reused, because it's consumed after one payment attempt. Every invoice, including a subscription renewal, needs its own Billie checkout and its own real-time credit decision. There is no stored Billie credential Stripe can charge automatically the way it charges a card.
Who bears the risk if a customer doesn't pay a Billie-financed invoice?+
Billie does, for the invoice it approved. That is the entire commercial pitch: the merchant is paid in full, usually within a day of the transaction, and Billie collects from the buyer on its own schedule, taking on both the credit risk and the fraud risk. It's a meaningfully different risk position than a standard net-30 invoice, where the merchant carries the receivable until the customer's accounts payable process actually pays it.
Should a B2B SaaS company use Billie instead of standard net terms?+
For a one-time purchase or an annual contract's first invoice, it can be a strong trade — you get paid immediately and someone else owns the collections risk. For an ongoing subscription, it only solves the problem for the invoice it actually approved. Treat each renewal as a fresh underwriting event rather than a fix for the collections workload described in our net-terms churn guide — you need a plan for what happens if a renewal-time credit check comes back different than the signup-time one did.
Stop losing subscribers today
One script tag. One function call. A live cancellation flow in under 10 minutes.
Start free trial →