Understand what merchant-of-record pricing includes, how to compare MoR providers against direct processing, and which hidden operating costs matter before choosing a SaaS checkout stack.
Merchant-of-record pricing is not just a card-processing fee. A provider may act as the seller to the buyer, collect payment, handle sales tax or VAT workflows, issue invoices, process refunds, manage disputes, and support payment-related buyer questions. That bundled work is why the headline fee can look higher than direct processing.
The real comparison is MoR fee versus processor fee plus tax tooling, accounting time, legal review, engineering maintenance, support workload, refund handling, chargeback operations, and risk. A lower payment fee is not cheaper if the missing work lands back on a small team.
| Cost component | Why it matters | What to verify |
|---|---|---|
| Transaction fee | The visible percentage and fixed fee determine the baseline cost per order. | Check domestic, international, subscription, and payment-method differences. |
| Tax handling | MoR pricing may include tax calculation, collection, remittance, and invoice workflows. | Confirm countries covered, digital-goods rules, registration scope, and documentation. |
| Refunds and disputes | Refund policies, chargeback fees, and dispute handling can change net revenue. | Check who owns evidence, buyer communication, fees, and support process. |
| Payout and currency rules | Payout timing, currency conversion, and minimum payout rules affect cash flow. | Verify settlement currency, payout schedule, thresholds, and FX treatment. |
| Migration cost | Subscriptions, customer data, invoices, and webhook logic can create switching cost. | Check exports, APIs, subscription migration support, and cancellation constraints. |
MoR pricing can win when a SaaS sells globally, has uncertain tax exposure, serves many small customers, wants to launch quickly, or lacks finance and compliance capacity. The provider fee buys operating leverage: fewer internal systems, fewer tax edge cases, and less payment support before revenue is predictable.
Direct processing can win when buyers are concentrated in one market, order values are high, tax tooling is already in place, the team needs full checkout control, or finance operations are mature. In those cases, a separate processor and tax stack may be cheaper than a bundled MoR fee.
| SaaS situation | Pricing risk | Likely decision |
|---|---|---|
| New global micro-SaaS | Tax and support overhead can exceed the early fee savings. | Model an MoR first, then compare direct processing later. |
| Domestic B2B SaaS | MoR convenience may be less valuable if tax and billing are simple. | Direct processing may be more efficient. |
| Low-ticket subscriptions | Fixed fees can take a large share of each payment. | Compare monthly versus annual billing before choosing a provider. |
| Developer product with global buyers | International cards, invoices, VAT, and refunds create scattered work. | MoR pricing may be worth the operational simplicity. |
Start with monthly revenue, order count, average order value, international share, refund rate, and chargeback assumptions. Then add a realistic monthly cost for tax software, accounting help, support time, and engineering. If the MoR premium is lower than the internal operating cost, the higher transaction fee may still be rational.
Merchant-of-record pricing is a stage-sensitive decision. A provider that is perfect at launch may be expensive after the team has stable revenue, a finance process, and known buyer geography. Re-run the model whenever MRR, average order value, or country mix changes materially.
Use the calculator to compare MoR-style pricing against direct payment processing from the same assumptions.
Open the calculatorProvider pricing can change. Always verify current public pricing and plan terms before choosing a payment stack.
Because the provider may bundle tax, invoices, refunds, disputes, buyer support, fraud checks, and compliance workflows into the transaction fee.
Compare net revenue after fees, then add the internal cost of tax tooling, accounting, engineering, support, and risk that direct processing leaves with the team.
No. The cheapest headline rate can lose if it has weaker tax coverage, missing subscription features, slow payouts, poor migration support, or support workflows that add hidden work.
Reconsider the stack when revenue, country mix, order value, or internal finance capacity changes enough that the bundled fee no longer beats owning the workflow directly.