Merchant of Record vs. Payment Processor for Software Sellers

On this page 8 sections

1. What Is a Merchant of Record, and What Does It Take off Your Plate?
2. Merchant of Record vs. Payment Processor: The Fee Math
3. Tax Liability and Who Files Globally
4. Chargebacks, Refunds, and Fraud Responsibility
5. Limits on Pricing, Checkout Design, and Customer Data
6. Migrating Subscribers off a Merchant of Record
7. When a Merchant of Record for SaaS Makes Sense, by Revenue Stage
8. Next Steps

Key takeaways

• A merchant of record is the legal seller to your customers. It takes on sales tax, VAT, disputes and much of the fraud risk in exchange for a higher bundled fee.
• Headline rates are misleading. Add tax software, filing help, dispute costs and your own time to the processor side before deciding.
• Heavy international B2C sales favor a merchant of record. At low ticket sizes an MoR mainly buys simplicity, and larger, U.S.-centric or B2B revenue often favors owning your processing.
• Before you sign with any merchant of record, confirm in writing whether you can export subscriber card tokens, because that decides how painful leaving will be.

If you sell software, apps, templates or other digital goods online, the merchant of record vs. payment processor decision shapes your margins, your tax exposure and how much control you keep over your customers. A merchant of record (MoR) bundles payments, global tax and dispute handling into one fee. A processor plus tax tools usually costs less per transaction but leaves the compliance work with you. This guide compares the full cost of each model and explains who is liable for what. It also covers the step most founders skip, which is what it takes to leave an MoR later.

What Is a Merchant of Record, and What Does It Take off Your Plate?

A merchant of record is the company that legally sells the product to your end customer. When you use an MoR such as Paddle, FastSpring or Lemon Squeezy, the MoR resells your software. Its name typically appears on the customer's card statement and receipt, and it carries the legal obligations of the seller.

With a traditional payment processor or merchant account, you are the merchant of record. The processor moves the money, but the sale, the tax and the liability are yours.

These responsibilities typically shift to an MoR:

• Sales tax, VAT and GST. The MoR calculates tax, collects it at checkout, registers where required, files returns and remits payment.
• Payment acceptance. The MoR offers cards and often local payment methods, and it handles currency conversion.
• Chargebacks and fraud screening. Disputes are filed against the MoR rather than against you.
• Invoicing and receipts. Invoices are issued in the MoR's name, which matters in countries with strict invoice rules.
• Some consumer-facing paperwork. This includes checkout terms and refund handling under the MoR's policies.

Several things stay with you. You still own the product, customer support, income taxes on your own earnings, and honest marketing and renewal practices. Exactly what the MoR covers varies by contract, so read the terms rather than the marketing page.

Merchant of Record vs. Payment Processor: The Fee Math

MoRs usually charge a bundled percentage plus a per-transaction fee. Some add charges for certain payment methods, currencies, payouts or disputes. A processor charges a lower rate that covers payments only. Tax software, filing help and dispute management then become separate line items.

Fees change often. Check each provider's current pricing page or request a written quote instead of relying on figures from forum posts.

An Illustrative Side-by-Side

The numbers below are illustrative only. The rates are round placeholders chosen so they do not match any named provider's published pricing. The comparison assumes a hypothetical MoR at 6% + 40¢ per transaction and a hypothetical processor at 3% + 25¢. The tax tool and compliance costs are also assumptions.

Scenario A: $20,000 per month in sales, a $40 average transaction and 500 transactions.

Scenario B: The same $20,000 in sales, but with a $10 average transaction, which works out to 2,000 transactions.

These examples point to two lessons:

1. The gap is smaller than the headline rates suggest. In Scenario A, the payment fees alone differ by $675. Once tax compliance is priced in honestly, the difference shrinks to $275.
2. Per-transaction fees dominate at low ticket sizes. Low-priced monthly plans pay far more in fixed fees under either model. In this example, the gap between the two models also widens, from $275 to $500 a month, because the MoR's higher fixed fee applies to four times as many transactions. Model your actual average transaction before deciding.

The tables leave several costs out. These include international card and currency conversion fees, dispute fees, your team's hours, and the cost of a tax audit or back-tax assessment if you get nexus wrong. Any of these can swing the result in either direction.

Paddle vs. Stripe and Lemon Squeezy vs. Stripe: Compare Like With Like

Searches for "Paddle vs Stripe" or "Lemon Squeezy vs Stripe" often lead to comparisons between an MoR's bundled rate and a processor's base card rate. Those two numbers don't measure the same thing. A fair comparison puts the MoR's all-in fee next to the processor's fee plus a tax add-on, any billing or invoicing add-ons, international fees and compliance help.

The same approach applies when you evaluate FastSpring fees. Ask each provider what is included, what is extra and what triggers a higher rate.

Tax Liability and Who Files Globally

Tax is the biggest functional difference between the two models.

With an MoR, the MoR is the seller for tax purposes in the jurisdictions it covers. It decides what to charge, and it handles registration and filing. You generally receive payouts net of tax and fees.

With your own processor, you have to:

• Track where your customers are. You need to know whether your sales create a tax obligation in each location. Many U.S. states apply economic nexus rules based on the sales you make into the state.
• Determine whether your product is taxable. States treat SaaS and digital downloads very differently. Our guide on sales tax on software subscriptions by state walks through the variations.
• Register, collect, file and remit on each jurisdiction's schedule.
• Handle VAT or GST on digital sales to consumers abroad. Many countries tax these sales where the buyer is located. Some apply their rules to foreign sellers with little or no threshold.

Tax software can automate calculation and sometimes filing. The legal obligation still sits with you.

This section is general information, not tax or legal advice. Nexus, taxability and registration rules change and depend on your facts. Confirm your obligations with a qualified tax professional before choosing a model.

Chargebacks, Refunds, and Fraud Responsibility

Digital goods attract "friendly fraud," where customers dispute charges they made themselves. They also attract card testing and subscription disputes from people who forgot they signed up.

Handing off disputes is convenient, but the MoR's risk team still watches your numbers. A spike in disputes or refunds can lead to holds or termination under either model.

Disputes also affect payout control. An MoR pays you on its own schedule, sometimes with minimum payout thresholds or rolling holds. A merchant account deposits funds directly to your bank, subject to any reserve in your agreement.

If you run your own processing, prevention is your job. Several practices help reduce disputes and involuntary churn:

• Use clear billing descriptors.
• Send renewal reminders before each charge.
• Set up card account updater tools for subscription billing.

You also need to follow consumer renewal rules. Our automatic renewal laws compliance map covers the state-by-state requirements.

Limits on Pricing, Checkout Design, and Customer Data

Because the MoR is the legal seller, it sets the rules for how you sell. Ask about these common constraints:

• Checkout. You may be limited to the MoR's hosted or overlay checkout, with restricted styling and fields.
• Pricing models. Usage-based billing, custom enterprise contracts and proration logic may be limited. Wire or ACH invoicing for large B2B deals may also be restricted to whatever options the MoR supports.
• Product categories. MoRs maintain acceptable-use lists, and some digital categories are excluded entirely.
• Customer data. The MoR holds the card tokens and is the customer's counterparty. You may receive customer records but not portable payment credentials.
• Brand presence. Customers see the MoR's name on statements and receipts. That can trigger "I don't recognize this charge" disputes if you don't explain it at checkout.

With your own online payment processing and gateway, you control checkout design, pricing logic and customer data. You also take on PCI DSS responsibilities. A hosted payment page or tokenizing gateway can narrow that scope considerably.

Migrating Subscribers off a Merchant of Record

Many software companies start on an MoR and later want to own their payments. Recurring revenue is the hard part to move. Work through these steps:

1. Check token portability before you sign. Ask whether the MoR will export stored card data to a PCI DSS-compliant processor on request, at what cost and in what timeframe. Get the answer in writing.
2. Plan for re-entry if tokens can't move. Every subscriber will need to re-enter payment details, and some will lapse. Prepare a reminder sequence and a grace period.
3. Register for tax before cutover. Your tax obligations start the moment you become the seller, so have registrations and software live on day one.
4. Warn customers about the new descriptor. A new name on a card statement is a common chargeback trigger.
5. Recheck renewal disclosures. If terms, pricing or the billing entity change, renewal laws may require fresh notice or consent. Confirm with counsel.
6. Run both systems in parallel. Keep the old system active until existing billing cycles roll over, and reconcile carefully.

Our subscription payment processing guide covers the retry logic and dunning to set up before the switch.

Apply honestly, too. Underwriters review software and digital goods closely. Our guide to why digital products merchant accounts get flagged explains what to fix first.

When a Merchant of Record for SaaS Makes Sense, by Revenue Stage

No single model is right for everyone, but some clear patterns hold.

An MoR often fits when:

• You're pre-revenue or early stage and have no finance or tax staff.
• Most of your customers are consumers spread across many countries.
• Your price points are low and you value simplicity over margin.
• You can't yet absorb the cost of a tax mistake.

Your own processor plus tax tools often fits when:

• Your revenue is large enough that the rate difference covers a tax tool and professional help.
• Your sales are concentrated in the U.S. or a few countries, or they are mostly B2B.
• You need custom pricing, invoicing or checkout control.
• You want direct ownership of customer payment data and payout timing.

A hybrid setup is also common. Some companies keep an MoR for global self-serve plans and run enterprise contracts through their own merchant account.

Next Steps

Start with your own numbers:

• Average transaction size
• Share of customers outside the U.S.
• Mix of B2B and consumer sales
• Monthly volume

Price the processor model honestly, including tax and dispute costs. Then compare it with an MoR quote that spells out what's included.

If owning your processing makes sense, MannyPay offers merchant accounts for online and high-risk businesses. We also provide payment gateways such as Authorize.net and NMI, integrations with Shopify, WooCommerce and other platforms, and international payment processing with multi-currency acceptance.

MannyPay does not file your taxes, so pair your account with tax software and a qualified advisor. Request a free processing quote, and a MannyPay specialist will respond within one business day.

ME

About the author

MannyPay Editorial Team

Beyond the Swipe's editorial desk researches the publication's guides and news and cites its sources in every article. Articles reviewed by a named MannyPay editor carry that editor's byline.

This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.