How to Use Paddle as Your SaaS Merchant of Record

Direct answer: To use Paddle, create a seller account, add your products and prices, drop a checkout link or overlay into your app, and let Paddle handle VAT, sales tax, invoicing, and chargebacks as the merchant of record.

The merchant-of-record model is the whole pitch. Paddle is the legal seller; you’re the supplier. That means tax registration in dozens of jurisdictions stops being your problem. It also means Paddle’s approval process decides whether you can sell at all.

What does merchant of record actually change for you?

A lot, in both directions. Paddle collects payment, so the customer’s card statement says Paddle, not your company name. Refund requests go to Paddle’s support first. If a buyer disputes a charge, Paddle handles the chargeback and it counts against Paddle’s processor record, not yours.

On the tax side, this is real relief. Selling to a buyer in Germany means 19% VAT, an invoice with required fields, and OSS reporting if you cross thresholds. With Stripe you own all of that. With Paddle you don’t.

How do you get set up?

Approval takes 1-5 business days and can stall on documentation, so start it before you build.

1. Apply for a seller account at paddle.com. You’ll submit company registration, a bank account, and a description of what you sell.
2. Complete KYC. Individual sellers need ID and proof of address; companies need incorporation documents and a UBO declaration.
3. Create a product. Products are containers; prices live under them. One product can have monthly, annual, and lifetime prices.
4. Set tax category. SaaS is usually “standard digital service”. Getting this wrong produces wrong invoices later and is painful to correct retroactively.
5. Configure checkout. Paddle Checkout is hosted — you pass a price_id and it renders the payment page. There’s also an overlay version you can trigger from a button without leaving your app.
6. Wire webhooks. Subscription created, payment succeeded, subscription canceled. Without webhooks your app never learns someone paid.

Test in sandbox first. Paddle’s sandbox is a separate environment with separate credentials, and the price IDs do not carry over to production. Repoint every ID when you go live, or you’ll launch with checkout errors.

What does Paddle cost?

Paddle’s standard rate is 5% plus $0.50 per transaction. There’s no monthly fee and no separate gateway charge — the card processing is inside that percentage.

Run the math on a $20/month plan. Paddle takes $1.50, which is 7.5% effective. Stripe takes 2.9% plus 30¢, or $0.88, plus you’d still owe VAT registration and filing work that costs roughly $30-80 per country per year if you outsource it. At that volume Paddle is more expensive in pure percentage and cheaper in labor.

At $200/month per customer, Paddle takes $10.50 versus Stripe’s $6.10. The gap widens with price. Above roughly $500/month per seat, a DIY tax stack starts to win financially — if you have someone to run it.

Which parts of Paddle actually work well?

• Subscription management. Proration, trial-to-paid conversion, dunning for failed payments, and pause-at-period-end all work without custom code.
• Tax handling. Invoices are generated per jurisdiction with the right fields. This is the part customers notice and it’s genuinely done well.
• Churn recovery. Retry logic on failed cards is configurable and Paddle’s default retry schedule is more patient than most teams build themselves.

Where does Paddle hurt?

The approval bar. Paddle rejects a meaningful share of applicants — crypto, gambling, adult, and anything ambiguous gets declined. If your product is close to the edge of SaaS, apply early and have a fallback.

Payouts are slower than Stripe. Expect a rolling payout schedule with a delay measured in days to weeks depending on your risk tier and volume. For a bootstrapped team, cash-flow timing matters more than the fee.

Support is thin on the seller side. Paddle’s customer-facing support is fine; the seller support responses are often templated and can take a couple of days. A dispute about a refund can stretch past a week.

And the customer experience: buyers see “Paddle” on the statement, which produces “who charged me?” tickets to your support inbox. Put a line on your pricing page that says payments appear as PADDLE.NET. Save yourself a dozen tickets a month.

Should you use Paddle or should you not?

Good fit: B2B SaaS in the $10-$200 per seat range sold internationally, small team, nobody who wants to do tax filings, growth primarily through self-serve checkout.

Poor fit: enterprise deals with negotiated contract terms (Paddle supports tail receipts but it’s clunky for large multi-year contracts), products above roughly $500 per seat, or marketplaces where you resell someone else’s product. Also poor for teams already running a mature Stripe stack with a tax subcontractor — the migration cost won’t pay back.

Quick Summary

• Paddle is the merchant of record: it collects payment, handles tax, and takes chargebacks.
• Standard pricing is 5% plus $0.50 per transaction, no monthly fee.
• Approval takes 1-5 business days; sandbox and production use different price IDs.
• Customers see “Paddle” on their statement — warn them on your pricing page.
• Sweet spot is self-serve SaaS between $10 and $200 per seat; above $500, do the math again.