Selling software across borders quietly exposes you to tax registration, audits, and chargeback liability in markets you have never visited. A Merchant of Record (MoR) removes that exposure by becoming the legal seller of your product. You license your software to the MoR; the MoR handles tax, chargebacks, fraud, and settlement downstream.

This guide explains what an MoR is, the three hidden costs it removes, how it differs from a payment processor like Stripe, what Waffo Pancake handles as your MoR, and exactly when switching pays off.

The three hidden costs of selling globally

Most of these costs never appear as a line item on a payment dashboard — which is exactly why they go unmanaged.

1. The global tax trap (VAT, GST, sales tax)

If you sell digital goods to customers outside your home country, you are very likely liable for tax in the customer's jurisdiction. This is law, not a gray area.

• There are more than 12,000 tax jurisdictions in the United States alone (Vertex, 2024).
• The EU applies VAT to digital services sold to EU consumers with a zero revenue threshold for non-EU B2C sellers.
• Singapore's Overseas Vendor Registration scheme applies 9% GST once global turnover exceeds SGD 1,000,000 and Singapore B2C digital sales exceed SGD 100,000 per year.
• Japan requires foreign sellers to register for 10% Japan Consumption Tax and, without a local establishment, to appoint a Japanese tax agent.
• Post-Brexit, the UK runs its own VAT regime for digital services, separate from the EU.

Doing this manually across 100+ markets is not a finance problem. It is a structural one.

2. Silent FX leakage

Most software is priced in USD but paid for in EUR, GBP, JPY, and more. Many gateways advertise global payments while embedding a markup into the exchange rate — commonly 1–3%, rarely shown as a separate fee. On USD 1,000,000 of revenue with 40% from non-USD markets, a 3% spread quietly costs around USD 12,000 a year with no line item to audit.

3. Frozen funds and rolling reserves

A revenue spike — often the direct result of a successful launch — can trip a generic processor's automated risk model and trigger an account freeze. Rolling reserves of 5–15%, held for 90–180 days, are standard practice at many legacy gateways for accounts flagged as elevated risk. That is your own earned revenue, locked away exactly when you need it to grow.

What a Merchant of Record actually is

A Merchant of Record is the legal entity that appears as the seller of the product. When you use an MoR, the MoR — not your company — is the registered seller in the transaction. That carries real legal consequences:

• The MoR collects and remits tax in each jurisdiction.
• The MoR absorbs the financial and legal liability for chargebacks and fraud.
• The MoR is responsible for compliance with local rules where you sell.

Your company becomes the software licensor. The MoR becomes your authorized reseller. Waffo Pancake puts it simply: "We're the seller. You focus on building."

Merchant of Record vs. Seller of Record

The two terms are often used interchangeably, but there is a precise distinction. The Seller of Record is the entity recognized for accounting and revenue-recognition purposes. The Merchant of Record owns the payment transaction — collecting funds, remitting tax, and absorbing fraud and chargeback liability. In most arrangements one entity is both. If a vendor acts as one but not the other, get the split of liabilities in writing.

How it works in practice

Here is a simplified flow with Pancake as your MoR:

1. A customer in Germany pays €49 (VAT-inclusive) for your product at checkout.
2. Pancake processes the payment as the legal seller on record.
3. Pancake calculates and collects 19% German VAT at the point of sale.
4. Pancake settles the net amount to you and remits the VAT to the German authorities on the applicable schedule.
5. You receive clean net revenue — with no VAT obligation, filing deadline, or audit exposure in markets where Pancake holds the registration.

The entire tax lifecycle closes before money reaches you.

MoR vs. PSP (Stripe): the structural difference

Many founders conflate an MoR with a Payment Service Provider like Stripe. A PSP is a pipe — it moves money from the customer to you, and you stay the legal seller with every compliance obligation. An MoR is a shield — it stands between you and the legal, tax, and regulatory complexity of global sales.

(Note: Stripe launched Stripe Managed Payments in April 2025, acting as MoR for digital goods sold through Stripe Checkout in 35+ countries at launch. The structural comparison below still applies to standard PSP setups.)

What Waffo Pancake handles as your MoR

As your Merchant of Record, Pancake becomes the registered seller across 173 countries and takes on three core jobs.

Automated tax, calculated at checkout. Pancake determines the customer's location from the information collected in the first checkout step and applies the correct local rate — for example 10% JCT in Japan, 19% VAT in Germany, or 9% GST in Singapore — then collects, remits, and reports it. You do not file or remit tax in the markets Pancake covers.

Legal and chargeback liability. Because Pancake is the seller on record, disputes and fraud exposure sit with the MoR, not your account. This matters structurally: card networks monitor chargeback ratios at the merchant level, and Mastercard's standard threshold is 1% (Visa's updated VAMP program tightens toward 1.5% in North America and the EU from April 2026). Under an MoR, those records are not against your company.

A conversion-optimized checkout. Pancake's two-step checkout collects email, country, and billing details first (for tax and order processing), then payment. It accepts Visa and Mastercard, Apple Pay, and Google Pay, renders in English, Chinese (Simplified), and Japanese, and supports theme, logo, and dark-mode customization. Each product can be priced in multiple currencies through an ISO 4217 price map.

Why trust Waffo as your MoR

Waffo Pancake is built on Waffo's payment platform. Waffo is PCI DSS v4.0 Level 1 certified, backed by HSBC, and built by a founding team from Alipay and Ant Group, with over $30M raised. For context, the industry first-attempt subscription renewal rate averages roughly 57% (Cashfree, 2024); across the Waffo platform, merchants have recorded up to a 45% improvement in payment success rate and recovered about 18% of previously failed orders (based on Waffo platform data).

Transparent, predictable pricing

The hidden-cost problem above has a simple antidote: publish every fee. Pancake does, with no monthly fees and no setup costs.

There are no surprise reserve policies hidden in the contract and no undisclosed FX markup baked into the rate. What you see is what you are charged.

Built for AI and usage-based businesses

Pancake is built for developers shipping AI products, API services, and any usage-based business. Two billing patterns cover most cases, and they combine cleanly:

• Subscriptions with usage quotas — tiered plans (weekly, monthly, quarterly, or yearly), each carrying a different token, request, or task allowance.
• On-demand charges — one-time orders or dynamic pricing computed at runtime, for overages and credits.

You integrate once with the TypeScript SDK @waffo/pancake-ts (REST API and read-only GraphQL are also available), and webhooks keep your quotas in sync as subscriptions activate, change, or renew. There is even an official Waffo Pancake Skill for AI coding agents, so you can scaffold your catalog and integration plan directly from your pricing model.

When should you switch to an MoR?

Answer yes to any of these and the cost of staying on a PSP-only setup is likely already higher than switching.

1. Are you selling into more than two countries? Tracking registration thresholds across even three jurisdictions becomes a recurring operational task.
2. Is your MRR above USD 10,000? A 3% FX spread on 40% non-USD revenue is roughly USD 1,440 a year at that level — and it scales linearly as you grow.
3. Are you spending more than five hours a month on tax and finance admin? At a conservative USD 100 an hour, that is USD 6,000 a year of product and growth time lost.
4. Have you ever had a frozen account, a holiday-delayed payout, or a surprise reserve? Those are reliability signals, not one-offs.

The best time to remove compliance as a growth constraint was your first international sale. The second-best time is now.

This article is general information, not tax, legal, or financial advice. Tax rates and rules change; verify current requirements with the relevant authority or a qualified advisor before acting.

Related articles

Global Compliance

How to Handle SaaS Sales Tax (VAT/GST) Without a Headache

Global Compliance

Do You Need a Merchant Account? MoR vs. PSP Explained (2026)

Global Compliance

LLC vs. Inc for a SaaS Business: How to Choose (2026 Guide)