MERCHANT OF RECORD
Best Merchant of Record for SaaS: 8 Providers Compared
Anyway Team
· 11 min read ·

The best Merchant of Record for SaaS depends on what you sell, where you can receive payouts, and which billing and tax tasks you need the provider to handle. For a small SaaS with low monthly sales, fixed transaction fees and withdrawal minimums can matter as much as the headline percentage.
This guide compares eight providers on those decisions. Start with Paddle or Lemon Squeezy if automated transaction-tax handling is a requirement; compare Anyway if hosted payment links, individual applications and an approved local payout route fit your app. Anyway's automated per-order tax calculation, collection and remittance has not launched, according to its current MoR documentation.
The shortlist is wider than one provider. Paddle is built around SaaS billing at scale, FastSpring offers a sales-assisted route for software companies, and products such as Lemon Squeezy, Dodo Payments, Creem, Polar, and PayPro Global each serve a distinct founder profile.

Best Merchant of Record for SaaS: quick comparison
Public prices checked October 26, 2026. These are starting rates, not total-cost quotes. Account approval, tax scope, payment method, add-ons and payout costs still need checking. This comparison is published by the Anyway team; the shortlist reflects documented capabilities, not a hands-on ranking or a complete market survey.
Provider | Starting rate | Put it on your shortlist for | Check before choosing |
|---|---|---|---|
Anyway | 3.9% + $0.50; no monthly/setup fee | Hosted links, recurring Card/USD plans and eligible individual/local payout routes | Per-order tax automation has not launched; standard payout fee is 1%, minimum $10 |
Dodo Payments | 4% + $0.40 | Developer-oriented SaaS and digital-product checkout | International, subscription and optional billing charges |
Creem | 3.9% + $0.40 | Software checkout and developer integrations | Approved product, seller country and payout terms |
Polar | Starter: 5% + $0.50; no monthly fee | Developer products and optional paid billing plans | Paid-plan monthly cost and international-card fees; legacy pricing differs |
Paddle | 5% + $0.50 per Checkout transaction | SaaS subscriptions and transaction-tax operations | Monthly payout cycle and minimum threshold |
Lemon Squeezy | 5% + $0.50 base | Subscriptions, downloads and license keys | Conditional transaction charges and supported payout country |
FastSpring | Custom quote | Software businesses needing tailored commercial terms | Full proposal, implementation and payout terms |
PayPro Global | Request a quote | Software vendors comparing localized checkout coverage | Seller eligibility, billing needs and the actual offer |
For a two-provider decision, read Anyway vs Paddle or Anyway vs Lemon Squeezy. Both include payout details that a starting-rate table cannot capture.
What a SaaS Merchant of Record actually changes
A payment processor moves money. A Merchant of Record, or MoR, becomes the seller named on the customer transaction for the sales it covers. Depending on the service agreement, an MoR provider can take on these operational jobs:
calculating, collecting, and remitting indirect tax such as VAT, GST, or sales tax;
issuing transaction documents to buyers;
working with payment partners and local methods;
administering refunds and payment disputes within the provider's process;
paying the SaaS merchant the net proceeds.
The MoR role does not prove that every listed workflow is automated or included. Check the provider's actual tax coverage and product scope. This is why comparing only the headline percentage produces a weak decision. A lower processing rate may still leave the founder responsible for registrations, filings, billing tools, and payment operations. Read the fuller explanation in Merchant of Record vs payment processor.
How to choose the best Merchant of Record for SaaS
1. Start with the billing model
Write down what customers can buy today and what will launch over the next year:
one-time licenses;
monthly or annual subscriptions;
fixed plan tiers;
credit packs;
usage-based charges;
upgrades, downgrades, and renewals.
A basic checkout can sell a fixed subscription. A more involved SaaS product may need plan changes, metering, proration, dunning, or a customer billing portal. Ask each provider which parts it owns and which parts your application must implement.
If your product uses credits or metered access, this AI credits vs usage-based billing guide explains the operational differences.
2. Check seller eligibility and payout routes
Payment acceptance and merchant payouts are separate questions. A provider may let customers pay from many countries while offering merchant payouts through a smaller set of routes.
Anyway supports Business and Individual account types during verification. Its public documentation lists US ACH, UK bank, Hong Kong bank, Alipay, and China bank payout account types. That makes it worth reviewing for founders whose preferred route appears on that list. Eligibility still depends on verification and product review.
Do not infer merchant eligibility from a generic "global payments" claim. Ask for written confirmation of the account type, country, settlement currency, minimum payout, and expected schedule that apply to you.
3. Model the whole fee schedule
Use real order data rather than one average order value. At minimum, model:
percentage and fixed transaction fees;
international card or payment-method charges;
currency conversion;
subscription or billing surcharges;
payout fees;
refund and dispute treatment;
minimum commitments under a custom contract.
For a worked example, see the Merchant of Record pricing comparison.
4. Review the launch workflow
The fastest route for a small SaaS is often a hosted checkout or payment link. A founder creates a product, publishes a checkout URL, listens for a paid-order webhook, and grants access after server-side verification.
Anyway exposes a paymentLinkUrl and supports merchant references and metadata. Those fields can connect a checkout session to the correct user, plan, or internal order. Sensitive information should stay out of URL parameters; the application should rely on verified webhook data before provisioning access.
The same architecture works well for a landing page, a settings screen, or an in-product upgrade prompt. See payment links for SaaS for the implementation pattern.
5. Match the provider to the team's operating style
Some teams want published terms and a direct product workflow. Others want a negotiated agreement, implementation guidance, and an account team. Neither model is universally better.
Choose a self-serve route when a small team needs to test demand quickly and the documented capabilities already match the product. Choose a sales-assisted route when the deal requires negotiated pricing, complex migration planning, or procurement support.
Which Merchant of Record fits a small SaaS with low sales volume?
Start with three requirements: your seller account can be approved, the subscription behavior works, and the payout route reaches your bank. Then compare a small month rather than a provider's largest discount tier.
Here is a hypothetical month of 20 card payments at $10 each, or $200 in sales. It excludes tax, international and subscription surcharges, refunds, currency conversion, payout costs and negotiated terms. It is a base-fee illustration, not an equal-service cost comparison.
Provider / plan | Calculation | Base transaction fees |
|---|---|---|
Anyway | $200 × 3.9% + 20 × $0.50 | $17.80 |
Dodo Payments | $200 × 4% + 20 × $0.40 | $16.00 |
Creem | $200 × 3.9% + 20 × $0.40 | $15.80 |
Polar Starter | $200 × 5% + 20 × $0.50 | $20.00 |
Paddle | $200 × 5% + 20 × $0.50 | $20.00 |
Lemon Squeezy | $200 × 5% + 20 × $0.50 | $20.00 |
With a $0.50 fixed fee, that component alone is 5% of a $10 order. Anyway's standard $10 minimum payout fee can also outweigh a small transaction-fee saving when withdrawing low balances. Batch timing and payout eligibility matter; a lower checkout rate does not automatically produce a lower total cost.
For an early-stage SaaS, shortlist by the work you need done:
A fixed subscription and your own access-control backend: compare supported renewals, webhooks, account eligibility and payout costs.
A download or licensed application: check native delivery and license management, including Lemon Squeezy's tools.
Automated indirect-tax handling from launch: require explicit coverage for your sales; Anyway's current automation gap is material.
Metered or changing plans: test usage reporting, proration and failed renewals instead of assuming any subscription checkout covers them.
Eight SaaS Merchant of Record platforms to consider
Anyway: hosted links and approved local payouts
Anyway combines the legal-seller role for eligible transactions with hosted payment links, one-time purchases, recurring Card/USD subscriptions, webhooks and payouts. Its published card and digital-wallet rate is 3.9% + $0.50, with no monthly or setup fee. Automated per-order tax calculation, collection and remittance has not launched; confirm the tax treatment of your sales before choosing it.
The Individual account path is relevant to founders who are selling before forming a company. Product and identity verification still establish who is selling and what buyers will receive. For SaaS teams, the clearest starting flow is product creation, payment-link placement, webhook verification, and entitlement activation.
Paddle: SaaS billing and transaction-tax operations
Paddle focuses on SaaS and operates as Merchant of Record for covered checkout sales. Its public checkout price is 5% + $0.50 per transaction. The product covers subscriptions, tax, payments, and revenue operations, and it has a mature ecosystem for SaaS teams.
Paddle is a natural candidate when billing operations are already a major function and the team wants a provider centered on that domain.
Lemon Squeezy: SaaS, downloads and license keys
Lemon Squeezy sells subscriptions and digital goods through an MoR model. Its public price is 5% + $0.50, with some services or transaction types subject to their own terms.
It fits founders who value a creator-friendly product experience and may sell downloads, memberships, or software from the same storefront.
Dodo Payments: developer-oriented checkout
Dodo Payments publishes a standard rate of 4% + $0.40 and promotes checkout coverage across many customer markets and payment methods. Its API-led positioning makes it relevant to SaaS and digital-product teams that want a modern integration path.
Review its supported merchant countries, payout terms, and billing requirements against your own launch plan.
Creem: software checkout and integrations
Creem is positioned for software and SaaS companies and states that it acts as Merchant of Record. Its current public site lists 3.9% + $0.40 per successful transaction for one-time purchases and subscriptions. Review the full account and payout terms as well as the transaction rate.
It belongs on a developer-focused shortlist where APIs, checkout setup, and software delivery matter more than enterprise procurement.
Polar: developer products and tiered platform plans
Polar combines MoR payments with developer-oriented billing tools. New organizations start on the free Starter plan at 5% + $0.50. Optional monthly plans lower the variable rate; international cards add 1.5%. The older 4% + $0.40 rate applies to qualifying Early Member organizations, with a separate subscription surcharge, and should not be used as the default quote for a new account.
Projects with an open-source audience may find its product framing especially familiar.
FastSpring: tailored software commerce
FastSpring has a long operating history with software, SaaS, and digital products. It uses custom revenue-share pricing rather than one public standard transaction rate. Its product covers subscriptions, local payment experiences, tax administration, and reporting.
It is well suited to teams that prefer to discuss volume, product needs, and commercial terms with a sales team.
PayPro Global: localized software checkout
PayPro Global markets MoR services to software businesses and publishes support for more than 70 payment methods and over 140 currencies. Pricing is provided through a quote.
It is relevant for vendors evaluating a sales-assisted provider with broad checkout localization and established software-company workflows.
A practical selection process
Run the same test with every finalist:
Confirm that your product category and merchant location are eligible.
Confirm the exact payout route and settlement currency.
Build a fee model using last month's likely order mix.
Create one product and complete a test checkout.
Verify the paid-order webhook and entitlement logic.
Review the buyer receipt, invoice, refund path, and descriptor.
Read the contract terms that define the covered transaction.
This process turns a broad "best platform" search into an evidence-based choice.
Frequently asked questions
What is the best Merchant of Record for a new SaaS?
There is no single winner for every new SaaS. First check seller approval, billing and tax requirements, then model a low-volume month including payout costs. Anyway is an option for eligible founders who need hosted links and a supported payout route; Paddle and Lemon Squeezy are worth comparing when automated transaction-tax handling is essential.
Is a Merchant of Record the same as a payment gateway?
No. A gateway helps transmit payment information. An external Merchant of Record takes the seller role for covered transactions; check its agreement and implemented services for the exact tax, refund and reporting scope. A SaaS company can use several payment components without changing who is legally recorded as the seller.
Does every SaaS need a Merchant of Record?
No. A company with its own entities, tax registrations, finance staff, and payment operations may prefer a processor stack. A small team selling globally can use an MoR to place those transaction duties with one provider.
Can an individual founder use a Merchant of Record?
Some providers support individual merchants, subject to identity and product verification. Anyway's public verification guide includes both Business and Individual account types. Applicants should confirm current eligibility and payout support for their location.
How quickly can a SaaS launch with a Merchant of Record?
The technical checkout can be created quickly when a hosted payment link is available. The full launch time also includes account and product verification, webhook setup, entitlement testing, and a review of the buyer experience.
Start with one real product
Create the plan customers already ask for, connect the paid-order event to your access system, and test the full path from checkout to payout record. Create an Anyway account to evaluate that workflow with your own SaaS.
Official sources checked
Anyway fees and MoR scope
You might also like
Merchant of Record vs payment processor: decide which seller responsibilities your team wants to own.
Subscription billing software for SaaS: compare the billing workflows behind a recurring plan.