Independent software guidance for creators and small teams.

How we reviewAffiliate disclosure
ToolMerit
⌕ SearchStart here →

CHARGE, RENEW, AND KEEP ACCESS IN SYNC

Payment and subscription tools: choose who runs the billing

For a custom checkout and recurring billing you operate, start with Stripe Payments plus Billing. For eligible software sold through a merchant of record, consider Paddle. For digital downloads, licenses and subscriptions with a built-in selling layer, consider Lemon Squeezy. First check the product and seller eligibility—not just the transaction fee.

An editorial shortlist for creators and small teams, based on official documentation checked September 9, 2026. These are fit judgments, not hands-on ratings or a complete market ranking. ToolMerit does not collect payments or manage subscriptions on this page.

Compare the payment role, not three interchangeable checkout buttons

A processor collects a payment. A billing layer schedules and tracks recurring charges. A merchant of record is the transaction seller to the buyer and takes on specified payment and transaction-tax work. Those roles can be packaged together, but the contract and enabled product determine the boundary.

CUSTOM CHECKOUT + BILLING

Stripe Payments + Billing

Shortlist this standard setup when you want to control the integration and have an owner for billing operations. Billing supports recurring charges, Payment Links and a hosted customer portal; Payments is a separate fee layer.

Price structure
Billing pay-as-you-go: 0.7% of Billing volume, excluding one-off invoices. The US page separately lists card processing at 2.9% + $0.30. Other methods, markets and negotiated plans differ.
Rule it out when
You expect this standard combination alone to transfer the transaction seller role or operate your product-access system for you.
Stripe Billing scope and prices →

SOFTWARE MERCHANT OF RECORD

Paddle

Consider Paddle for eligible software and apps when you want payment collection, subscriptions and transaction-tax administration in one merchant-of-record arrangement.

Price structure
Standard checkout pricing is 5% + $0.50 per transaction. Products under $10 or an invoicing requirement need a custom pricing discussion.
Rule it out when
The main offering is physical goods or human services such as consulting. Check the exact product before integrating; a recurring charge does not make every business eligible.
Paddle pricing and inclusions →Paddle product eligibility →

DIGITAL PRODUCT SELLING LAYER

Lemon Squeezy

Consider Lemon Squeezy for digital files, software licenses and subscriptions. Its merchant-of-record selling layer can reduce the work of assembling checkout and digital delivery.

Price structure
Base pricing is 5% + $0.50. Subscriptions add 0.5%; international transactions outside the US and PayPal each add 1.5%. Read the fee breakdown before comparing totals.
Rule it out when
You need physical fulfillment or human services that do not meet store approval rules. Confirm approval, seller country and payout method before moving customers.
Lemon Squeezy product scope →Store approval requirements →

A $20 renewal: which fees are actually in the quote?

The examples below assume one eligible $20 subscription payment by a US domestic card, with no tax, discount, currency conversion or international surcharge. They illustrate fee arithmetic—not total operating cost, a quote for your account, or a cheapest-provider verdict.

Scroll the comparison sideways to see every fee and limitation. Keyboard users: focus the table, then use the arrow keys.

Same $20 input, different service bundles
SetupIncluded calculationIllustrated feeNot established by this example
Stripe standard US card + Billing$20 × 2.9% + $0.30 processing
+ $20 × 0.7% Billing
$1.02Tax tooling, other products, dispute/refund effects, FX, custom pricing and your operating work.
Paddle checkout$20 × 5% + $0.50$1.50Eligibility, custom invoicing or low-ticket terms, optional services and actual settlement conditions.
Lemon Squeezy US card subscription$20 × (5% + 0.5%) + $0.50$1.60International or PayPal additions, payout charges, marketing extras and your negotiated plan.

Rate bases: Stripe Billing and Payments, Paddle checkout, and Lemon Squeezy fees. Lemon Squeezy calculates its fee on total order value, so a taxed checkout is not the same $20 example. Payout and marketing fees can be separate.

Ask for a transaction-level breakdown

Use your expected ticket size, customer locations, currencies, payment methods and renewal volume. Ask which amounts attract each fee, what happens after a refund, when payouts become available and how reserves or disputes affect settlement. Compare a realistic month, not just the lowest displayed percentage.

Keep product and business duties assigned

A merchant-of-record arrangement does not create your content, maintain your app or settle every obligation of your business. Confirm the division of product support, refunds, buyer communication and transaction-tax work in the provider agreement. This is software selection guidance, not tax or legal advice.

Cancellation, payment failure and access are different states

A successful checkout screen is only one event. The billing system and the product need an agreed response to renewals, failed charges and the end of paid access. Do not copy one provider's status names or cancellation timing into another integration.

LEMON SQUEEZY CANCELLATION EXAMPLEStop the next charge without ending paid access early
  1. 1 · ACTIVECurrent paid period

    The subscription remains valid.

  2. 2 · CANCELLEDFuture collection stops

    Access continues until the current billing period ends.

  3. 3 · EXPIREDThe subscription has ended

    Update access to reflect the end of the subscription.

A documentation-based state illustration, not a software screenshot or a test run. Lemon Squeezy's subscription lifecycle distinguishes Cancelled from Expired.

A failed renewal is not a cancellation request

In Lemon Squeezy, a failed renewal becomes Past due; exhausted retries can become Unpaid, with further handling depending on settings. Its documentation says to retain product access in non-Expired states. Check the configured recovery process rather than revoking access on the first decline.

Other providers can end a plan immediately

Stripe supports immediate, period-end and custom-date cancellation; refund handling is a separate choice. Pausing collection does not itself change subscription status. Match your product behavior to the selected option and the terms shown to the buyer. Stripe cancellation behavior →

For a custom integration, use verified server-side events rather than the buyer's return URL as your payment evidence. Stripe's subscription-event guide covers successful invoices, payment failures and action-required states. Its webhook guidance also requires authenticity checks and handling duplicate or out-of-order deliveries. A duplicate notification must not grant a second entitlement or trigger another fulfillment.

Before migration, prove six billing outcomes

Run these checks in the provider's supported sandbox with test identities and test payment methods. Record the input, provider record, customer-visible result and product-access result. ToolMerit has not run these tests inside the vendors' products.

  1. First payment and renewal

    Test the initial charge and a later billing cycle. Match the plan, currency, invoice amount, receipt, next billing date and enabled access. An initial success does not prove the renewal path.

  2. Decline and recovery

    Use a supported failure case. Confirm the customer can update their payment method, retries follow the configured schedule and recovery restores the correct state without a duplicate subscription.

  3. Cancel now versus period end

    Test the cancellation choices your product exposes. Verify the stop date, access end, confirmation and any refund separately; do not promise an option your integration cannot support.

  4. Plan change and trial ending

    Check an upgrade, downgrade and trial expiry. Inspect proration, billing date and feature access before and after the change. Editing a Lemon Squeezy product price does not automatically reprice existing subscriptions.

  5. Duplicate and delayed events

    Replay supported test events. Confirm one business action per event/object, signature rejection for an invalid event and correct state when an older notification arrives late.

  6. Export and reconcile

    Export customer, plan, subscription, invoice and payout records with stable IDs. Confirm the destination can preserve renewal dates, currency and terms. A customer CSV does not prove payment credentials can migrate; agree a supported transfer process before switching.

Sandbox results do not establish production approval, bank settlement, fraud outcomes or tax compliance. Keep test and live environments separate; do not use real customer cards to fill gaps in this checklist.

Connect billing to the work around it

Need the product catalog and delivery layer first? Use the online store comparison. To measure visits becoming signups, use the conversion calculator; a signup conversion rate is not payment recovery or retained revenue.

Assign one owner to review billing exceptions and another clear route for product support. The automation comparison can help choose supporting workflows, but moving an event between apps does not validate its financial meaning. See how ToolMerit separates source research from testing.

ADJACENT OPERATIONS

Related settlement, inventory and order tools

These existing resources support business operations around payments. They are not substitutes for a payment processor or a subscription billing provider.