Merchant-of-record checkout for SaaS that handles global tax remittance and geo-localized pricing automatically.
Paddle is a merchant of record for software companies: it is legally the seller of your product, which means it runs the checkout, processes payments, calculates and remits sales tax and VAT in every jurisdiction, and handles invoices, refunds, and chargebacks under its own entity. Around that core it offers localized pricing by market, subscription management, and dunning. SaaS and digital-product companies — especially small teams selling globally — use it to outsource the entire compliance and payments burden rather than assembling a processor, tax engine, and invoicing stack themselves.
Which of the capability map's modules Paddle covers — each links to the module's own page, with every tool that supports it.
| Module | Phase | Depth | Note |
|---|---|---|---|
| Define What You Sell | |||
| Pricing Tables / Checkout | Design & Setup | Core | |
| Geo & Localized Price Books | Design & Setup | Supported | |
| Tax Setup & Rules | Design & Setup | Supported | Tax rules are largely absorbed by the MoR model rather than configured by you. |
| Win the Deal | |||
| Checkout Conversion Optimization | Digital Commerce | Supported | |
| Trial Provisioning & Management | Digital Commerce | Partial | |
| Fulfill & Bill | |||
| Payments & Refunds | Rate & Bill | Core | Paddle is the legal seller — payments, refunds, and chargebacks under its entity. |
| Tax Calculation | Rate & Bill | Core | Calculates and remits global sales tax and VAT as merchant of record. |
| Invoice Generation | Rate & Bill | Supported | |
| Multi-Currency & FX Rate Management | Rate & Bill | Supported | |
Scored against UsagePricing's Usage-based billing & metering rubric v1.0 (0 weak · 1 adequate · 2 strong), assessed July 2026. Requirements we couldn't verify from public material stay unscored — never guessed. Read the method.
| Requirement | Score | Why |
|---|---|---|
| Real-time balances & drawdown Can a customer (and your product) see an accurate credit or spend balance mid-period? | 1 · Adequate | Credit balances at the account level; no usage drawdown model. |
| Correction & re-rating When a meter was wrong, can you fix history without hand-editing invoices? | 0 · Weak | Corrections flow through refunds and credits — no event pipeline to replay. |
| Commits, credits & custom rate cards Can it express how enterprise AI deals are actually signed? | 0 · Weak | Self-serve subscription focus; negotiated commit contracts are out of scope. |
| Billable-metric flexibility Can finance define a new meter without re-instrumenting the product? | 1 · Adequate | Usage-based charges over reported quantities. |
| Invoice & proration correctness Do mid-cycle changes, consolidation, and multi-currency come out right? | 1 · Adequate | Solid subscription invoicing; the merchant-of-record model constrains bespoke formats. |
| Rev-rec & ERP handoff Can the numbers survive an audit once they leave the billing system? | 1 · Adequate | As merchant of record Paddle owns tax and liability; finance consumes its reporting. |
| Ingestion scale & integrity Does the meter stay correct at production event volumes? | 1 · Adequate | Scaled for checkout and subscription events. |
| Price-change velocity How fast can you ship a pricing change safely? | 1 · Adequate | Catalog updates are straightforward at self-serve scale. |
The merchant-of-record model is the differentiation: global tax liability becomes Paddle's problem, not yours, which no gateway-plus-tax-tool combination fully replicates. The trade-off is control — checkout, payout timing, and customer billing records run through Paddle's entity and rules, so companies that need bespoke payment flows or direct processor relationships eventually feel the boundaries.
Percentage per checkout, published. Merchant-of-record take rate covering payments, tax, and compliance.
1 of the companies the Blueprint tracks — from public job posts, engineering blogs, and filings. Every claim links to its evidence on the company page.
Paddle sells your product to the customer and you sell to Paddle. It owns tax registration and remittance worldwide, PCI compliance, and chargeback liability; you receive consolidated payouts. The cost is a take rate above raw processing fees and less direct control over the billing relationship.
Common triggers are complex negotiated B2B contracts, invoicing terms the MoR flow cannot express, a need for direct processor economics at volume, or wanting to own customer billing data end to end. Many keep Paddle for self-serve while running enterprise deals on separate rails.
By overlap on the capability map — computed, not curated.