Merchant of Record vs payment processor
The most important payments question is not whose checkout looks best. It is whose name is on the sale and who remains responsible after the payment succeeds.
The short version.
- A processor helps move money while your business normally remains the seller.
- An MoR becomes the seller for eligible covered transactions and assumes the documented transaction obligations.
- The fee comparison is not one-to-one because the two models purchase different operating scopes.
- The value of outsourcing depends partly on the administrative work your business would otherwise retain in its operating country.
A processor moves money
A payment processor or payment service provider helps your business accept a card, wallet, bank debit, or transfer. Your business normally remains the seller to the customer, so your terms, invoices, refund obligations, indirect-tax registrations, filings, and product support remain yours.
Tax calculation software can reduce manual work without changing that legal relationship. A processor offering tax calculation is not automatically a Merchant of Record.
An MoR becomes the seller
A Merchant of Record buys or licenses the eligible product from you and resells it to the customer. It appears in the buyer-facing transaction and assumes the documented transaction responsibilities, commonly including indirect-tax calculation, registration, filing, remittance, fraud, disputes, and billing support.
The exact boundary is contractual. Product delivery, product support, bookkeeping, income tax, privacy obligations, and unsupported markets can remain with you.
The fees buy different things
A processor's headline rate usually prices payment acceptance. An MoR's rate usually bundles a broader operating role. A useful comparison shows the processing fee, add-ons, international and FX costs, refund and dispute behavior, payout costs, and the work your team still performs.
Do not invent a dollar value for legal, accounting, or staffing work. Add your known costs and keep unknowns visible.
A practical decision rule
Choose an MoR when eligible global digital sales, indirect-tax operations, and transaction support would otherwise slow the business more than the fee and control tradeoffs. Remain the merchant when control, product breadth, checkout flexibility, direct customer ownership, or scale economics matter more and you can operate the retained responsibilities.
Country changes that calculation. A business operating in Italy or Germany may find that VAT, invoicing, filing, accounting, and related administration makes the MoR fee worthwhile, while a business with simpler local obligations or existing operational support may not. Assess the work for your own entity, product, customer mix, and team rather than treating country as an automatic verdict.
Decision checklist.
- Confirm the legal seller shown in terms, invoices, receipts, and statements.
- List the indirect-tax, fraud, dispute, and transaction-support tasks each contract covers.
- Assess the VAT, invoicing, filing, accounting, and transaction-support workload for your own legal entity and operating country.
- Price the operating work that remains with your team.
- Check product, seller-country, buyer-country, and channel eligibility.
- Review data, token, and subscription portability before signing.
How this shows up in real businesses.
These are anecdotes and first-party accounts, not policy evidence. Use them to discover questions worth verifying.
A long-running founder discussion surfaces recurring questions about fee add-ons, onboarding, support, checkout flexibility, payout costs, and the value of transferring tax operations to an MoR.
Comments span several years, include conflicting accounts and vendor promotion, and must not be used as current pricing evidence.reddit · communityA first-time SaaS founder weighs MoR onboarding against flexibilityThe discussion shows how early-stage founders prioritize speed, country eligibility, tax relief, documentation, and operational simplicity before advanced billing features or marginal fee differences.
This is a small community thread with self-reported experiences, not a representative survey or an onboarding guarantee.reddit · first personA founder in Egypt chooses around seller-country constraintsA solo founder describes country and entity constraints as the primary selection filter, then updates the thread after choosing Lemon Squeezy for a straightforward initial onboarding experience.
One founder's onboarding outcome can change with product, country, entity, website readiness, risk review, and provider policy.company blog · customer storyLess Annoying CRM explains its customer-facing move to PaddleThe company explains that the billing-platform change affects tax collection, statement identity, receipts, and what customers will see, demonstrating why migration communication is part of payment architecture.
This is one company's announcement and describes its own implementation, customer base, and contract.founder blog · first personA solo founder recounts two weeks migrating from Stripe to PaddleThe founder describes the implementation and operational differences encountered while replacing a direct Stripe integration with Paddle's Merchant of Record model.
This personal account has not been independently verified and may omit product-specific constraints or later platform changes.Review the evidence.
- Stripe explanation of Merchant of RecordReviewed 2026-07-27
- Paddle Merchant of Record termsReviewed 2026-07-27