Skip to main content

Trends, tech news, and tool comparisons.

10 posts tagged with "billing"

View All Tags

How to handle failed payments in a SaaS (Stripe setup)

· 7 min read
Dealpuffin
Proof points and live coupons for early adopters

To handle failed payments in a SaaS, let your billing provider retry the charge on a schedule, email the customer a link to update their card, and decide in advance when access ends if the invoice stays unpaid. With Stripe Billing, the first two are dashboard settings and the third is one dropdown plus a webhook handler in your app.

This guide covers that setup for Stripe, based on Stripe's documentation read on 13 November 2026. The same three decisions apply to Paddle, Polar and others, though the settings are named differently.

How to offer an annual discount in Stripe

· 6 min read
Dealpuffin
Proof points and live coupons for early adopters

The cleanest way to offer an annual discount in Stripe is to give the product a second Price with a yearly interval, set below twelve times the monthly price. A coupon can do the same job, but it is built for discounts that start and end, not for a permanent plan. This guide shows the setup, a worked example, and what happens when a monthly customer switches.

Everything about Stripe's behavior below comes from its documentation, read on 12 November 2026.

Paddle vs Lemon Squeezy for indie SaaS: fees and future

· 5 min read
Dealpuffin
Proof points and live coupons for early adopters

Paddle and Lemon Squeezy publish the same headline fee for a merchant of record: 5% + 50¢ per transaction, with no monthly fee. They differ in the surcharges around it and in where each product is heading. Lemon Squeezy adds fees for international cards, PayPal, and subscription payments, while Paddle's pricing page lists one rate. Lemon Squeezy is also owned by Stripe, and its own pricing page now points to Stripe Managed Payments.

All figures below come from each vendor's own pages, read on 12 November 2026. Check them again before you commit, since both can change.

Usage-based vs seat-based pricing for AI products

· 6 min read
Dealpuffin
Proof points and live coupons for early adopters

Use seat-based pricing when each person gets their own value and your cost per user is stable. Use usage-based pricing when your cost rises with every request, which is usually true of AI features. Many AI products land on a hybrid: a seat price that includes a pool of usage, with paid overage after that. Intercom and GitHub both do versions of this, and their pricing pages show how.

Facts below come from vendor pages read on 10 November 2026. Prices change, so confirm before copying a number.

How to price a SaaS product at the early stage: a decision rule

· 6 min read
Dealpuffin
Proof points and live coupons for early adopters

To price an early-stage SaaS product, choose one value metric that grows with the benefit a customer gets, anchor the price to the cost of the problem it replaces, offer two or three simple tiers, and test the number in conversations with real buyers before you build the billing. Expect to change the price in the first year, and keep the first customers' price fixed for a stated period so changing it stays fair.

This guide is a method, not a benchmark. Pricing data differs a lot between markets, and I cite only vendor documentation for the facts below, read on 9 November 2026.

How to test Stripe webhooks locally with the Stripe CLI

· 6 min read
Dealpuffin
Proof points and live coupons for early adopters

To test Stripe webhooks locally, install the Stripe CLI, run stripe login, then run stripe listen --forward-to localhost:4242/webhook. The CLI prints a whsec_ signing secret; put it in your server's environment and fire test events with stripe trigger. You do not need a public URL or a tunnel for this.

This guide walks through the full loop: forwarding, triggering, verifying the signature, and the mistakes that make verification fail. The commands and behavior come from Stripe's documentation, read on 7 November 2026.

Merchant of record explained for indie founders

· 5 min read
Dealpuffin
Proof points and live coupons for early adopters

A merchant of record (MoR) is the company that legally sells your product to the customer. It charges the buyer, collects and remits sales tax or VAT, handles fraud and chargebacks, and appears on the card statement. You are paid by the MoR rather than by the customer. You still pay income tax in your own country.

For a solo founder selling software worldwide, that trade is simple to state: you pay a higher fee per payment, and someone else carries the cross-border tax work. This post explains what changes in practice. Facts come from the providers' own documentation, read on 7 November 2026.

Stripe vs Paddle vs Polar: what an indie SaaS pays in fees

· 6 min read
Dealpuffin
Proof points and live coupons for early adopters

On a $20 subscription payment from a US card, Stripe's standard fee is $0.88. Paddle and Polar's free plan each take $1.50. The difference is mostly who sells to your customer. Paddle and Polar are the merchant of record and handle sales tax and VAT for you. With standard Stripe payments you are the seller and the tax work is yours.

This post puts the three fee schedules side by side and runs the same $20 payment through each. All figures come from the providers' own pricing pages, read on 5 November 2026. Fees change, so check the linked pages before you commit.

Stripe coupons vs promotion codes (what founders mix up)

· 5 min read
Dealpuffin
Proof points and live coupons for early adopters

In Stripe, the thing people type at checkout is a promotion code. The thing that actually defines the discount is a coupon. Founders launching on Product Hunt mix these up constantly: they invent a string like LAUNCH50, paste it in a thread, and never create the objects in Stripe. Checkout then does exactly what you told it to do. Nothing.

Picking usage-based billing now that Stripe owns Metronome and Adyen owns Orb

· 5 min read
Dealpuffin
Proof points and live coupons for early adopters

Stripe closed its acquisition of Metronome on 14 January 2026. Adyen closed its acquisition of Orb on 1 July. So the two metering engines most AI and API companies shortlisted are now owned by companies whose main business is processing your payments. If you're pre-revenue and about to put a usage meter on your product, that's worth ten minutes of thought before you write the integration.