An honest breakdown of what's structurally broken with every Merchant of Record on the market today, and what it costs the businesses that depend on them.
Merchant of Record is sold as the easy button for global payments. You hand off tax, compliance, and fraud. They handle the mess. You focus on your product.
That's the pitch. The reality is different.
After helping run hundreds of millions in volume through these platforms and rebuilding the stack from scratch, here's what's actually broken with every Merchant of Record on the market today.
1. The fees are insane, and most of them are hidden
The public pricing is never the real pricing. Once you stack everything, you're paying 7 to 15% per transaction.
Typical breakdown:
- Base fee: 4 to 5%
- Non-US card surcharge: +1.5%
- Billing fee: +0.5 to 0.7%
- Payout fee: +0.2 to 0.5%
- FX fee: +1%
You discover half of these after you've signed. The other half only show up once you start scaling internationally.
2. Every Merchant of Record depends on a single Payment Service Provider (or acquirer)
This is the part nobody talks about, and it's the single biggest risk in the model.
99% of Merchants of Record run on one Payment Service Provider (or acquirer). If that Payment Service Provider (or acquirer) cuts them off, the Merchant of Record cannot process. Not reduced capacity. Zero capacity. Overnight.
It also means the Merchant of Record inherits every flaw of that one Payment Service Provider (or acquirer):
- Mediocre acceptance rates
- Expensive FX
- Legacy infrastructure
- Layered fees you can't negotiate away
And here's the part that makes it worse: even if the Merchant of Record wants to switch Payment Service Providers (or acquirers) later, they can't.
When a customer pays for the first time, their card gets tokenized. The token is what powers every payment after that: subscriptions, one-click checkout, saved cards, returning customers. No token, no recurring charge.
There are two kinds. Payment tokens are issued by the PSP and only work inside their system. Network tokens are issued by Visa or Mastercard themselves, and were explicitly designed to be portable across processors so merchants wouldn't get locked in.
Sounds like network tokens solve the problem. They don't. Every network token has a Token Requestor ID (TRID) that says who owns it. PSPs default to a shared TRID, meaning they own the tokens, not the merchant. To get a dedicated TRID (the one that's actually portable), you have to negotiate it explicitly, before signing, against a PSP that has zero reason to grant it. Most merchants don't even know TRIDs exist.
The result: both token types are non-portable in practice. The PSP has no obligation and no incentive to hand them over to a competitor, so they don't. They drag their feet, charge fees, or simply refuse.
Which means migration forces every customer to re-enter their card and re-authorize. On a business with recurring revenue, that's a death sentence. The Merchant of Record is locked in by design, and you inherit the lock-in.
3. Every Merchant of Record depends on a single payout partner
Payouts go through the same Payment Service Provider (or acquirer) or through intermediaries like Stripe Connect or Payoneer. Which means your payouts are subject to a second approval layer that can refuse your geography or your business model overnight, and that adds hidden fees on top of the ones you already pay.
Most merchants find this out way too late.
4. If your Merchant of Record goes down, you go down with it
Read this one carefully. This is the scenario nobody prepares for, and it's the one that kills companies.
When a Merchant of Record gets cut by its Payment Service Provider, it doesn't happen with a 30-day notice. It happens overnight. One morning, your transactions start failing. Every charge, every renewal, every new signup. Zero income. And it stays that way for as long as the Merchant of Record takes to onboard another processor, redo the technical integration, pass compliance again, and reroute traffic. In real cases, that has been weeks to months. During that entire window, you cannot collect a single euro from your own customers.
Then comes the second hit. Even after processing comes back, you can't just resume. Because your tokens aren't portable (see point 2), every recurring customer has to re-enter their card and re-authorize. On a business with meaningful MRR, expect to lose 20 to 40% of your recurring revenue permanently in that transition. Customers who left will not come back. Customers who never noticed they were charged will discover their subscription, look at the price, and cancel.
So the real damage is not just "a few bad days." It's: weeks of zero revenue, then a permanent step-down in MRR, then the slow churn of customers who lost trust during the outage. Compound that with payroll, server costs, ad spend, and your runway, and most companies don't survive it.
This isn't a hypothetical. It's exactly what happened to Digital River merchants and to Paddle merchants. Read their stories before signing with anyone.
5. Settlement takes 7 to 21 days
Industry standard. Sometimes longer when the intermediary decides to hold funds. Your cash is stuck while your burn runs normally.
6. Most countries and most business models are excluded
Because Merchants of Record are locked to what their single Payment Service Provider (or acquirer) can process and what their single payout partner can onboard:
- Most emerging markets: no
- Physical products: usually no, or reviewed for months
- Marketplaces: no
- Infoproducts: rejected or stuck in review
Merchants of Record market themselves to SaaS specifically because SaaS is the only vertical easy enough to screen at scale.
7. Platform risk is real
This isn't theoretical. It has already happened, repeatedly:
- Digital River went insolvent and held creator funds for months
- Paddle withheld payouts from merchants, responded only with automated templates, and only released funds when merchants started leaving
- Flurly got shut down by Stripe with a $425,000 fine because of one bad actor on the platform
Merchants of Record hold your money. If they mismanage it, misuse it, or get cut off, you're an unsecured creditor. Good luck.
Accounts also get blocked without warning, even with clean sales history. Support is AI templates. There is no recourse.
8. You can't actually verify anything
This one ties everything else together, and nobody talks about it.
On every existing Merchant of Record, you cannot independently check:
- Where your funds are held, right now
- Whether they've been commingled with other merchants' money
- Whether they're being used as working capital to plug holes elsewhere on the platform
- When settlement will actually occur
You trust the dashboard. You trust the monthly statement. That's it. The Digital River and Paddle situations were only detectable after the cash had already stopped moving. By then it's too late.
9. You don't own your customer data
Cards, subscriptions, payment methods: none of it is portable. If you ever want to leave the Merchant of Record, you lose most of your MRR in the migration because your customers have to re-enter everything manually.
The Merchant of Record model is designed to make leaving expensive.
10. The API and support are not built for serious businesses
- No real server-to-server integration
- No highly customizable checkout
- No dedicated account manager
- Technical support that takes days
Gumroad, Paddle, and Lemon Squeezy have replaced their front-line support with chatbots. Invoice corrections, billing fixes, basic admin tasks turn into multi-week ordeals.
What we built instead
Inflowpay is the Merchant of Record we wanted to exist when we were running our own businesses.
4% all-in. Yes, all-in.No non-US card surcharge, no hidden billing fee, no payout fee, no FX markup. One number.
Multi-Payment Service Provider routing. We aggregate multiple Payment Service Providers (or acquirers) and route each transaction through the one with the best acceptance rate. This takes merchants from 70% to over 90% acceptance, and it de-risks the entire stack. If one of our partners cuts us off, your business keeps running on the others.
Pssst, you don't know what acceptance rate is? Check this out, it's the single most important metric when you do business online.
PS: when Uber or Amazon are looking for a payment partner, they always talk acceptance rate before they talk fees.
Local pay-ins. We only use Payment Service Providers (or acquirers) for pay-ins, and we route locally whenever possible. Lower fees, higher conversion.
Payouts owned end-to-end. Payouts are 100% managed by us through our Inflow Connect infrastructure. Local rails, lower fees, and we control final settlement times.
4-day settlement, with instant payout available. Not 7. Not 21.
Every country except OFAC-blacklisted. We onboard geographies other Merchants of Record refuse.
Every business model. Marketplaces, physical products, SaaS, digital goods. We don't force you into the SaaS-only box.
Customer data stays with you. Cards, subscriptions, payment methods. Portable. If you ever want to leave, you leave with your MRR intact.
Enterprise-grade stack. PCI Level 1 compliance, true server-to-server integration, fully customizable checkout, dedicated account manager, and an SLA-backed technical support commitment.
Fully transparent, audited and verifiable 24/7. This is the part no other Merchant of Record offers. Inflowpay's settlement layer is fully transparent and continuously auditable. You don't have to take our word for it. You can verify, in real time:
- Where your funds are held, at any moment
- Settlement timing and the rail used
This eliminates the single biggest risk of the legacy Merchant of Record model:
waking up one morning without access to your money.
On every other platform, you trust a dashboard and a monthly statement and hope the float is actually there. On Inflowpay, the float is observable in real time on a public ledger that anyone can check. You can prove, continuously, that we are not playing with your money. Don't trust, verify.
The Digital River and Paddle scenarios become impossible to hide on our infrastructure. If something is wrong with the float, it's visible immediately, by anyone.
The Merchant of Record model worked when merchants had no other option. They do now.
