MERCHANT OF RECORD
Merchant of Record vs Payment Processor: Costs & Roles
Anyway Team
· 9 min read ·
The central difference between a Merchant of Record and a payment processor is responsibility. A payment processor moves the payment while your business remains the seller. An external Merchant of Record becomes the seller for the transactions covered by its agreement. Its responsibilities and included tax, billing and support services must be checked separately.
Choose a payment processor when your company is ready to run the legal-seller operation itself. Choose a Merchant of Record when you want one provider to carry that transaction role while you deliver the SaaS product.
Merchant of Record vs payment processor at a glance
Question | External Merchant of Record | Standard payment processor setup |
|---|---|---|
Who sells to the customer? | The MoR for covered sales | Your SaaS business |
Who moves the payment? | The MoR and its payment partners | The processor and payment partners |
Who handles transaction tax? | Check covered markets, contractual duties and implemented services | Your business retains seller duties; tax tools may assist |
Who issues customer documents? | Seller details should match the MoR sale | Your business or its invoicing system |
Who handles refunds and disputes? | Payment-side workflow under the MoR terms; you may supply delivery evidence | Your team manages them through the processor |
Who delivers and supports the software? | Your SaaS team | Your SaaS team |
How should fees be compared? | Transaction, payout and exception costs, plus any services left to you | Processing plus billing, tax, filing and operating costs you need |
Both models can use hosted checkout and subscriptions. The deciding question is who carries the seller role for the specific sale. For the terminology behind that role, see Merchant of Record vs Seller of Record.
What a payment processor does
A payment processor carries payment instructions between the buyer, the card or payment network, and the merchant’s financial setup. Modern processors may also offer hosted checkout, billing, invoicing, reporting, and tax software.
Those tools can cover a large part of the workflow, but software features do not automatically change the legal seller. In a standard processor setup, your SaaS business sells directly to the customer. It decides where it must register, calculates and files applicable taxes, defines invoice content, responds to disputes, and keeps the records needed for accounting.
That model gives an established company direct control over its commercial operation. It fits teams that already have the required entity, internal owners, and professional support.
What a Merchant of Record does
A Merchant of Record combines payment collection with legal responsibility for covered sales. The MoR appears as the seller on the transaction and handles the transaction duties tied to that position.
For SaaS, the service commonly covers:
Hosted checkout and payment collection
Applicable sales tax, VAT, and GST calculation and filing
Customer invoices and receipts
Recurring subscription transactions
Refund and dispute administration
Order and balance records
Net payouts to the SaaS merchant
This is a common service bundle, not proof that every MoR offers every item in every market. For example, Anyway's current scope says its per-order tax automation has not launched.
The SaaS company still builds the software, grants access, supports the product, and records its business income. The MoR owns the customer-sale role specified in the agreement.
Merchant of Record vs PSP: is that the same decision?
A payment service provider, or PSP, may bundle payment processing, checkout, payment methods and other services. In a standard PSP arrangement your business remains the seller. An MoR arrangement changes that role for covered transactions. Compare the actual product and contract, because one provider can offer both models.
For example, Stripe Managed Payments is an MoR offering. It should not be described as identical to a standard Stripe Payments setup. Likewise, a payment gateway transmits payment information; adding a gateway does not by itself outsource the seller role. The separate MoR vs payment gateway guide covers that technical distinction.
Compare costs using the same SaaS month
Consider a hypothetical SaaS with 100 customers each paying $20 per month. Monthly sales are $2,000 and there are 100 payment events. This is an illustration, not a customer result or a quoted processor offer.
Processor route: $2,000 × your quoted processing percentage + 100 × its fixed fee, then add the billing, tax, filing, payout and support costs you actually need.
MoR route: $2,000 × the quoted MoR percentage + 100 × its fixed fee, then add applicable surcharges, payouts and services outside the agreement.
Anyway base-fee illustration: $2,000 × 3.9% + 100 × $0.50 = $128, before payout, conversion, refund or other charges. This does not include an automated per-order tax service.
Use the same customer locations, payment methods and refund assumptions for both routes. A higher fee can buy work you would otherwise do yourself; a lower rate only helps if the remaining service scope fits your team.
The responsibility test
Ask one question before comparing features: Who is the seller on the customer’s transaction?
If the answer is your company, you are operating the direct-seller model even if several software tools help with tax and billing. Your company can itself be the merchant of record in that setup. If an external MoR provider is the seller for the covered transaction, you are using an outsourced MoR arrangement.
This affects five practical areas.
1. Transaction tax
Digital-product tax rules depend on the buyer’s location, customer type, product classification, and local thresholds. A direct seller must determine its obligations and maintain the related registrations and filings. Many MoR services include calculation, collection and remittance for covered sales. Verify the exact markets, product categories, implementation and contract instead of treating the MoR label as confirmation of an automated service.
See sales tax vs VAT vs GST for SaaS for the terms founders encounter most often.
2. Customer documents
An invoice or receipt should reflect the legal seller for the transaction. Under a processor model, the SaaS business supplies those documents. Under an MoR model, the MoR issues transaction documents under its seller details.
3. Subscriptions
Recurring billing creates a sequence of sales, not just one checkout. Each renewal needs an order status, customer record, tax treatment, and balance entry. Both models can support subscriptions, but the seller responsibility remains different.
4. Refunds and disputes
In the direct model, the SaaS company sets its customer policy and manages the processor workflow. In the MoR model, the MoR carries the payment-side transaction role while the SaaS company follows a clear product refund policy and provides evidence about delivery when requested.
5. Payout and reconciliation
A processor settles processed funds according to its account structure. An MoR first records the sale, tax, fee, refund, and any adjustment, then pays the merchant’s net revenue. In both cases, the founder should match order records to the final payout.
When a payment processor fits
The direct-processor model can fit a SaaS company that has:
A business entity ready to contract as seller
A finance owner for order and payout records
A tax process for registration, calculation, and filing
An invoice system tied to the correct seller entity
An operating process for refunds and disputes
A reason to keep direct control of the customer transaction
This is a business-operations choice, not only a checkout choice.
When a Merchant of Record fits
The MoR model is often a strong match for:
Solo developers preparing for first revenue
Small SaaS teams selling across borders
Founders who want sales tax, VAT, and GST handled inside each covered sale
Products that need one-time payments or recurring subscriptions
Teams that want hosted checkout, order events, balances, and payouts in one flow
Founders who want to spend their operating time on the product and customers
Read Merchant of Record for SaaS for a launch checklist.
How Anyway brings the MoR model together
Anyway is the Merchant of Record for eligible sales made through Anyway Business. Its current documentation describes hosted payment links, one-time payments, recurring Card/USD subscriptions, renewal tracking, end-of-period cancellation, refunds and chargeback workflows. Automated per-order tax calculation, collection and remittance has not launched, and current orders contain no separate tax amount.
The standard card and digital-wallet price is 3.9% + $0.50 per successful transaction, with no monthly or setup fee. Payout fees are separate: the standard charge is 1%, with a $10 minimum per request; account terms may differ.
The basic SaaS flow is:
Apply as an individual or business merchant and complete review.
Create the product and supported price.
Add the hosted payment link to the website.
Attach a non-sensitive reference to the purchase.
Verify signed webhooks and the paid order on your server.
Grant the matching customer access in your application.
Reconcile order records and request an available USD payout through Finance.
The application still controls access and product delivery. Buyer-editable payment-link metadata is a correlation aid, not authorization. SaaS payment reconciliation explains how to check orders against receipts as volume grows.
How to make the decision
Use this three-question test:
Do we want to be the legal seller in every target market? If yes, plan the processor, tax, invoice, and reporting stack. If no, evaluate an MoR.
Do we have the people and systems to run that work now? Count recurring filings and transaction support, not only integration time.
Which model gets us to a correct, traceable sale with less operating overhead? Compare the full workflow and total cost.
If your shortlist includes Anyway, confirm that its supported billing flow, approved payout route and current tax scope meet your requirements. If automated indirect-tax handling is essential, resolve that requirement before choosing the provider.
Frequently asked questions
Is a Merchant of Record the same as a payment processor?
No. A processor moves the payment while the merchant usually remains the legal seller. A Merchant of Record is the legal seller for covered transactions and takes on the related transaction duties.
Does a payment processor handle sales tax?
Some processors sell tax calculation, registration, or filing tools. In a standard processing setup, the SaaS business still remains the seller and is responsible for meeting its obligations.
Does an MoR replace my SaaS company?
No. Your business still owns and operates the product. The MoR takes the seller role for the transactions covered by its agreement.
Can Anyway process subscriptions?
Yes. Anyway supports recurring Card/USD subscriptions. Its subscription documentation lists daily, monthly and yearly intervals, renewal-order records and cancellation at the end of a billing period. Do not assume every one-time payment method supports renewals.
What does Anyway charge?
Anyway publishes a price of 3.9% + $0.50 per successful transaction, with no monthly fee and no setup fee.
Sources and related reading
Product details checked October 26, 2026. This is a comparison of documented service models, not a test of payment performance.
Anyway MoR scope and fees.
Stripe Managed Payments: why the specific Stripe product matters.
Paddle pricing and included services: an example of bundled MoR services.
Eight Merchant of Record providers for SaaS: compare providers after choosing the model.