Here’s a stat that’ll make you rethink your entire payment stack: 47% of SaaS companies underestimate their true payment processing costs by 40% or more. They look at Stripe’s 2.9% + $0.30 headline rate, do some quick math, and call it a day. Six months later, they’re drowning in tax compliance bills, chargeback fees, and currency conversion costs they never saw coming.
I’ve seen this pattern repeat across dozens of SaaS companies. The confusion usually starts with a fundamental misunderstanding: payment processor, merchant of record, and payment gateway are not the same thing. Each serves a different purpose, carries different liabilities, and comes with a completely different cost structure.
In this guide, I’ll break down exactly what each model does, when to use which, and how to calculate the true cost of your payment infrastructure. No fluff, no vendor bias — just the facts you need to make an informed decision.
What Is a Payment Gateway?
A payment gateway is the virtual equivalent of a point-of-sale terminal. It’s the technology layer that captures and encrypts customer payment information, then securely transmits it to the payment processor.
Think of it as the digital checkout counter. When a customer enters their credit card details on your website, the payment gateway:
- Encrypts the card data using SSL/TLS protocols
- Routes the transaction to the appropriate payment processor
- Returns the authorization response (approved or declined)
- Stores tokens for recurring billing (if applicable)
Key point: A payment gateway does NOT handle the actual movement of money. It only handles the secure transmission of payment data. It’s one piece of a larger puzzle.
Popular payment gateways include Stripe Checkout, PayPal Payments Pro, Authorize.Net, and Braintree. Most charge either a flat monthly fee ($25-50/month) or bundle their costs into the overall processing rate.
What Is a Payment Processor?
A payment processor (also called a Payment Service Provider or PSP) is the service that actually moves money between banks. They handle the authorization, settlement, and funding of transactions.
When your customer clicks “buy,” here’s what happens behind the scenes:
- The payment processor receives the encrypted data from the gateway
- It contacts the customer’s issuing bank to verify funds
- It requests authorization from the card network (Visa, Mastercard, etc.)
- Upon approval, it initiates the transfer of funds
- It settles the transaction by depositing funds into your merchant account
The critical distinction: A payment processor handles the transaction flow but does NOT assume legal responsibility for the sale. You remain the Merchant of Record — meaning you’re on the hook for tax compliance, chargebacks, fraud prevention, and regulatory obligations.
Stripe, PayPal, Square, and Adyen are the dominant payment processors in the SaaS space. Their standard pricing typically starts at 2.9% + $0.30 per transaction, though this varies by volume and geography.
What Is a Merchant of Record (MoR)?
A Merchant of Record is a third-party entity that becomes the legal seller of your product. They assume full responsibility for the transaction — including payment processing, tax compliance, fraud management, chargebacks, and regulatory obligations.
Here’s how the flow differs:
- Your customer pays the MoR (not you directly)
- The MoR handles all payment processing, tax calculation, and compliance
- The MoR remits taxes to each jurisdiction on your behalf
- The MoR manages chargebacks and fraud disputes
- You receive the net proceeds (minus the MoR’s fee)
The key benefit: You remain the Seller of Record (owning the product, setting prices, managing customer relationships) while the MoR handles the legal and financial complexity of the transaction itself.
Leading MoR providers include Paddle, FastSpring, Fungies.io, and Lemon Squeezy (now owned by Stripe). MoR fees typically range from 5% + $0.50 to 8% per transaction — higher than raw processing costs, but inclusive of tax compliance, fraud protection, and regulatory management.
Side-by-Side Comparison: Gateway vs Processor vs MoR
| Feature | Payment Gateway | Payment Processor | Merchant of Record |
|---|---|---|---|
| Primary Role | Secure data transmission | Move money between banks | Legal entity for transactions |
| Tax Compliance | Not included | Not included (add-on available) | Fully included |
| Fraud Protection | Basic encryption | Optional add-on | Fully included |
| Chargeback Handling | Not included | You handle disputes | MoR handles disputes |
| Legal Liability | None | You remain liable | MoR assumes liability |
| Currency Conversion | Not included | 1-2% additional fee | Included |
| Recurring Billing | Token storage only | Requires additional setup | Built-in |
| Typical Pricing | $25-50/month or bundled | 2.9% + $0.30 | 5% + $0.50 to 8% |
| Best For | Any online business | US/domestic focus, high volume | Global SaaS, compliance-heavy |
The Hidden Cost Problem: Why Headline Rates Lie
Here’s where most SaaS founders get burned. They compare Stripe’s 2.9% + $0.30 against Paddle’s 5% + $0.50 and think Stripe is obviously cheaper. They’re wrong.
Let me break down the true cost structure for a typical SaaS company doing $50K MRR with 40% international customers:
| Cost Component | Stripe (Processor) | Paddle/Fungies (MoR) |
|---|---|---|
| Base processing fee | 2.9% + $0.30 | 5% + $0.50 |
| Tax compliance (Stripe Tax) | $0.50 per transaction | Included |
| Currency conversion (intl) | 1-2% | Included |
| Chargeback fees | $15 per dispute | Included |
| Fraud protection (Radar) | $0.05-0.07 per transaction | Included |
| Monthly platform fees | $0-50 | $0 |
| Effective Rate | 4.5-6.2% | 5% flat |
For a SaaS company with international customers, the “cheaper” processor often ends up costing more than the all-inclusive MoR. And that doesn’t even account for the operational overhead of managing tax compliance across multiple jurisdictions yourself.
When to Use Each Model: A Decision Framework
Use a Payment Processor (Stripe, PayPal) When:
- You’re primarily selling to US customers (simpler tax landscape)
- You have the resources to manage tax compliance in-house
- You want maximum control over the checkout experience
- You’re processing high volumes and can negotiate custom rates
- You need deep API customization for complex billing logic
Use a Merchant of Record (Paddle, Fungies, FastSpring) When:
- You sell to customers in multiple countries (especially EU, UK, Canada)
- You don’t want to deal with VAT, GST, or sales tax compliance
- You’re an indie founder or small team without dedicated finance ops
- You want chargebacks and fraud handled for you
- You prefer predictable, all-in pricing without surprise fees
Use a Standalone Payment Gateway When:
- You have an existing merchant account and just need checkout technology
- You’re using a hybrid approach (different providers for different regions)
- You need specific gateway features (like advanced tokenization)
Honestly, most modern SaaS companies don’t use standalone gateways anymore. They’ve been largely absorbed into all-in-one platforms like Stripe (processor + gateway) or Paddle/MoR providers (full stack).
Hybrid Approaches: The Best of Both Worlds?
Some sophisticated SaaS companies use a hybrid model: Stripe for US domestic transactions (where sales tax is simpler and Stripe’s lower base rate provides cost advantage) and an MoR like Paddle or Fungies for international transactions (where tax compliance burden is highest).
This approach can optimize costs, but it adds complexity:
- You need to route transactions based on customer location
- You maintain two integrations instead of one
- Reporting and reconciliation become more complex
- Customer experience may vary by region
For most SaaS companies under $1M ARR, the complexity isn’t worth the savings. Pick one approach and optimize later.
2026 Market Landscape: Key Providers Compared
| Provider | Type | Pricing | Best For |
|---|---|---|---|
| Stripe | Processor | 2.9% + $0.30 (+ add-ons) | Developer-first, US focus |
| Paddle | MoR | 5% + $0.50 | Enterprise SaaS |
| Fungies.io | MoR | 5% + $0.50 | Indie/SaaS founders |
| FastSpring | MoR | 5.9% + $0.75 | Digital goods, software |
| Lemon Squeezy | MoR | 5% + $0.50 | Creators, simple products |
| PayPal | Processor | 3.49% + $0.49 | Consumer products |
| Adyen | Processor | Interchange++ (variable) | Enterprise, high volume |
Red Flags: When Your Current Setup Is Wrong
Here are the warning signs that your payment infrastructure is costing you more than it should:
- You’re spending more than 5 hours per month on tax compliance. That’s time you could spend on product or growth. An MoR eliminates this entirely.
- Your effective processing rate exceeds 5%. If you’re using Stripe with Tax, Radar, and international customers, you’re likely already paying MoR-level rates without getting the compliance benefits.
- You’ve received a sales tax nexus notice. If you’re hitting economic nexus thresholds in multiple states and haven’t registered, you’re exposed to penalties.
- Chargebacks are eating into your margins. MoRs typically have better fraud prevention and handle disputes for you.
- You’re turning down international customers. If tax complexity is limiting your market, an MoR removes that barrier.
Implementation Considerations
Migration Complexity
Moving from one payment provider to another isn’t trivial. Here’s what to expect:
- Payment Processor → Payment Processor: Moderate complexity. You’ll need to migrate customer payment tokens (if the provider supports it) or ask customers to re-enter payment details.
- Payment Processor → MoR: Higher complexity. The MoR becomes the legal seller, so you’ll need to update your terms of service, checkout flow, and potentially your pricing (since the MoR fee structure differs).
- MoR → Payment Processor: Highest complexity. You’re taking on tax compliance responsibility, which requires significant setup and ongoing operational overhead.
API and Integration Differences
Stripe is famous for its developer-friendly API. Most MoRs have caught up, but there are differences:
- Stripe: Maximum flexibility. You can build any billing logic you want, but you’re responsible for more implementation.
- Paddle: More opinionated. The API guides you toward best practices for SaaS billing, but customization is more limited.
- Fungies: Clean, modern API with built-in support for subscriptions, one-time payments, and usage-based billing. Good middle ground.
Frequently Asked Questions
Can I switch from a payment processor to an MoR later?
Yes, but it’s not instant. You’ll need to migrate active subscriptions (most MoRs support this), update your checkout flow, and communicate the change to customers. Most companies see a 2-5% churn spike during migration, which usually recovers within 30 days.
Do I lose control of my customer relationships with an MoR?
No. You remain the Seller of Record — you own the product, set prices, handle support, and maintain the customer relationship. The MoR only handles the transaction layer. Most customers never even know an MoR is involved.
Is an MoR more expensive than Stripe?
It depends. For US-only businesses with simple tax situations, Stripe is usually cheaper. For global SaaS with customers in the EU, UK, Canada, and other jurisdictions, an MoR often has lower total cost of ownership when you factor in tax compliance tools, currency conversion, and operational overhead.
What happens to my data if I switch providers?
Customer data (names, emails, subscription metadata) is yours and can be exported. Payment method data (credit card tokens) is trickier — PCI compliance rules prevent direct export. Most providers support token migration through a secure process, but you’ll need to coordinate between old and new providers.
Can I use multiple payment providers simultaneously?
Yes, but it adds complexity. Some companies use Stripe for US customers and an MoR for international, or offer PayPal as an alternative checkout option. Just be prepared to manage multiple integrations, reconciliation processes, and reporting systems.
Bottom Line: Making the Right Choice
The payment processor vs merchant of record decision isn’t about finding the “best” option — it’s about finding the right fit for your specific situation.
If you’re a US-focused SaaS with a finance team and simple tax needs, Stripe or another processor probably makes sense. You’ll pay lower base rates and maintain maximum control.
If you’re selling globally, hate dealing with tax compliance, or want to focus on product instead of payment operations, an MoR like Paddle or Fungies is likely the better choice. The all-inclusive pricing eliminates surprise fees and operational headaches.
And if you’re currently using a payment processor but your effective rate (including all add-ons) is approaching 5%, it’s probably time to reconsider. You might be paying MoR prices without getting the compliance benefits.
Ready to simplify your payment stack? Create your free Fungies.io account and see how an all-inclusive Merchant of Record can reduce your operational overhead while keeping your global tax compliance handled automatically.
Sources
- Stripe: Payment processor vs. gateway vs. merchant account
- Paddle: What is a merchant of record
- Gapp Group: Merchant of Record vs Payment Gateway
- Ruul: Merchant of Record vs Payment Processor
- Anrok: End-of-year sales tax and VAT report 2025
- Sales Tax Institute: Expanding Digital Goods & Services Taxation 2025
- UniBee: Paddle vs Stripe Ultimate Comparison
- FastSpring: What Is a Merchant of Record
