Merchant of Record vs Payment Gateway (Plain English for SaaS Devs)

"Merchant of record" gets used constantly in conversations about SaaS payments and almost never gets explained. This is the plain-English version for developers who want to understand the difference before choosing a provider — because the difference determines who does your tax filings, who carries legal liability when something goes wrong, and ultimately how much overhead you carry as a solo founder.

What a payment gateway actually is

A payment gateway — Stripe, Braintree, Adyen, Razorpay — is a piece of infrastructure that authorizes and captures card transactions. It moves money from your customer's card to your bank account. That is its job.

Everything else is your problem.

You are the merchant of record by default. That means you are the legal entity selling to the customer. The customer's card statement says your company name. Your company is liable for VAT in every EU country where you have a customer over the threshold. Your company needs to register for GST in Australia when you exceed their low-value-digital-goods threshold. Your company owes US sales tax in states where you have "economic nexus" — which in most states kicks in at $100,000 in sales or 200 transactions, a threshold a growing SaaS can hit faster than expected.

None of this is Stripe's responsibility. Stripe Tax exists as an add-on and helps calculate the right amounts, but the legal obligation to register, collect, and remit remains yours. That means foreign tax registrations, foreign filings, possibly foreign accountants, and a growing compliance calendar as you add customers in new countries.

What a merchant of record is

A merchant of record (MoR) is a company that becomes the legal seller for your transactions. The customer technically buys from the MoR. The MoR resells to you. Because the MoR is the legal seller:

• The customer's card statement shows the MoR's name (e.g. "PayProGlobal" or "Paddle").
• The MoR registers for VAT, GST, and sales tax in every relevant jurisdiction.
• The MoR collects the right tax amounts at checkout.
• The MoR remits those taxes to the relevant governments.
• The MoR handles chargebacks: it is the party the card network holds liable.
• You receive the net amount (revenue minus the MoR's fee) as a payout.

From a legal standpoint, you are a vendor supplying a product to the MoR. The MoR's fee — typically 5% + a fixed amount — covers the gateway, tax engine, compliance, fraud protection, and chargeback handling.

The components side by side

	Payment gateway	Merchant of record
Processes card transactions	Yes	Yes
Legal seller to customer	You	The MoR
VAT/GST liability	You	The MoR
US sales tax	You	The MoR
Tax registration in each country	You	The MoR
Chargeback liability	You	The MoR
Fraud protection	Partial	Included
Fee	Lower (2–3%)	Higher (5%+)
Compliance overhead	High	Near zero

When a raw gateway makes sense

A payment gateway without MoR is the right call when:

• You are in a Stripe-supported country.
• You have either very few international customers (below global tax thresholds) or the revenue to justify a dedicated accountant and tax-filing workflow.
• You need deep customization — custom checkout UI, complex billing logic, or payment features that MoR providers do not expose.
• You are above roughly $50,000 MRR and the fee savings over an MoR (typically 2–3 percentage points) outweigh the compliance cost.

At scale, the math often shifts toward a raw gateway plus dedicated tax software (TaxJar, Avalara, Stripe Tax). At $500,000 annual revenue, a 2% fee difference is $10,000 — more than enough to pay for a tax service and part-time accountant.

When a merchant of record makes sense

An MoR is almost always the right choice when:

• You are selling globally to customers in many countries.
• You are a solo founder or a small team with no bandwidth for tax compliance.
• You are in a country Stripe does not support — in which case an MoR is also often the only practical gateway to card payments.
• You are below $50,000 MRR and the compliance overhead of a raw gateway would consume more time and money than the fee savings justify.

For a developer in Ukraine, Nigeria, Pakistan, or most of Southeast Asia, the MoR is often both the preferred and the only viable path. Providers like PayProGlobal act as MoR and handle everything — payments, tax, compliance, chargebacks — across 100+ countries, paying out to local banks without requiring you to register a foreign entity.

The fee question

The MoR's higher percentage is the most common objection. It is real. At 5% versus 2.9%, a $10,000 MRR product pays $210 more per month to the MoR than to a raw gateway. At $100,000 MRR that is $2,100 per month.

Against that, account for: tax software subscription ($30–$200/month), accountant or tax consultant fees (varies widely, often $200–$1,000+/month for global filings), your own time spent on compliance, and the cost of getting something wrong (penalties, back-filing, de-registration). For most small SaaS businesses, the MoR fee buys more than it costs until around $50,000 MRR. After that, the calculation becomes product-specific.

FAQ

Does the customer know they are buying from the MoR and not from me?

The card statement and receipt will show the MoR's name, not yours. Most customers do not notice; they bought a software subscription and they got it. If a customer does contact you about a billing charge, you handle it as normal — the MoR is the back-office entity, not the front-facing one. Your product is still your brand.

What happens if I exceed a tax threshold in a country?

With an MoR, nothing changes for you. The MoR monitors thresholds and adjusts collection automatically. With a raw gateway, you need to detect when you have crossed the threshold, register for that country's tax, start collecting the right amount, and file returns. The MoR eliminates this entirely.

Can I switch from an MoR to a raw gateway later?

Yes. Build a provider interface from day one so your application code does not call the MoR's SDK directly. When you switch to Stripe or another raw gateway, you implement the interface for the new provider and update a config line. The harder part is migrating active subscriptions — customers may need to re-enter payment details. Plan for a 30–60 day transition window.

Does using an MoR affect my ability to claim input VAT?

In most jurisdictions, the MoR is the reseller of record, which changes the nature of your sale to them rather than to the end customer. This can affect how input VAT is reclaimed, and the details vary by country. Consult a tax advisor in your specific jurisdiction before making a decision based on VAT reclaim. For most early-stage SaaS founders, this is not a material factor.