Stripe integration
Use Stripe as the payment processor behind Bunny's invoices and customer portal. Cards are stored, charged and reconciled automatically — while quoting, subscriptions and revenue stay in Bunny.
What the integration does
Cards charged against invoices
Bunny raises the invoice from the subscription and Stripe collects it — including recurring charges, upgrades and usage overages.
Self-service payment methods
Customers add and update their own card in the Bunny portal. The card is held by Stripe; Bunny never stores the number.
Webhooks close the loop
Stripe payment events flow back into Bunny via a signed webhook, so payment status, failures and retries are reflected on the invoice.
Your statement descriptor
Set a statement descriptor suffix so charges appear on customer statements under a name they recognise.
Stripe is excellent at moving money and deliberately thin on the things B2B SaaS billing actually turns on — negotiated pricing, ramps, co-terming, approval workflows, contract-level revenue schedules. Most companies that try to run the whole revenue stack on Stripe end up with a layer of custom code and a spreadsheet doing the parts Stripe does not model.
Using Stripe underneath Bunny avoids that. Bunny owns the commercial model — the quote, the subscription, the usage rating, the invoice, the revenue schedule. Stripe does what it is genuinely best at: taking the payment.
What the customer experiences
An invoice with a pay link, a portal where they can add or update a card themselves, and automatic collection on renewal. Failed payments and retries flow back into Bunny through the webhook, so dunning and AR reporting reflect reality rather than what was expected to happen.
Frequently asked questions
Is this the same as Stripe Billing?
Do we keep our existing Stripe account?
Where are card details stored?
What do I need to configure?
Is it available outside the US?
Keep the stack you have
Bunny sits between your CRM, your tax engine, your payment processor and your ledger — so quoting, subscriptions, usage and invoicing share one system of record without anyone migrating off the tools they already use.