Do You Need a Merchant Account? MoR vs. PSP Explained (2026)
Most SaaS founders never need a merchant account. Learn what one is, why PSPs replaced it, and how a Merchant of Record compares on tax and liability.
A merchant account is a bank account that lets a business accept card payments — and most SaaS founders never need to apply for one. A Payment Service Provider (PSP) like Stripe gives you that infrastructure in minutes, while you stay the legal seller. A Merchant of Record (MoR) like Waffo Pancake goes further: it becomes the legal seller across 173 countries and absorbs your tax, chargeback, and fraud liability.
- A merchant account is a settlement layer at an acquiring bank — it does not handle checkout, fraud, tax, or subscriptions.
- Most SaaS companies no longer apply for one: a PSP aggregates many businesses under its own shared merchant account.
- A PSP moves money but leaves you the legal seller with every tax and compliance obligation.
- A Merchant of Record becomes the legal seller, registering, collecting, and remitting tax and absorbing chargeback and fraud liability.
- Waffo Pancake is an MoR covering 173 countries at 3.9% + $0.50 per transaction, with no LLC required and no monthly fees.
Most SaaS founders hit the phrase "merchant account" early in their payment research and assume it is something they must set up before they can take a single card. In most cases, they do not need one. The more useful question is not whether to get a merchant account, but which infrastructure model fits your stage: a Payment Service Provider (PSP) or a Merchant of Record (MoR).
This guide explains what a merchant account actually is, how PSPs changed the calculation for nearly every modern business, how an MoR compares on tax and liability, and how to decide which model is right for you — without building on the wrong foundation.
What is a merchant account?
A merchant account is a type of bank account that allows a business to accept card payments. It is held at an acquiring bank and acts as an intermediary holding account: when a customer pays with a card, funds move from the issuing bank through the card network to the merchant account, where they are held briefly before being swept to the business's standard bank account.
Under the traditional model, without a merchant account a business had no path to receive card payments directly.
How a traditional merchant account works. The business applies directly to an acquiring bank. The bank reviews the application — business type, transaction volumes, chargeback risk, financial history — and either approves or declines. If approved, the business receives a unique Merchant ID (MID) and can process transactions through its own dedicated account, with negotiated rates, defined reserve requirements, and contractual terms for chargeback liability.
What a merchant account does not do. It does not handle checkout, fraud detection, currency conversion, invoicing, tax collection, or subscription lifecycle management. It is a holding and settlement layer only. Everything above it in the stack — the gateway, the processor, the fraud layer — requires separate infrastructure.
Why most SaaS companies no longer apply for one
The traditional model required every business to go through underwriting with an acquiring bank. That changed when Payment Service Providers entered the market.
A PSP aggregates many merchants under a single shared merchant account held by the PSP itself. When a business signs up with Stripe, Square, or a similar provider through standard onboarding, it is not getting its own dedicated merchant account in the traditional sense. It is getting access to the PSP's shared merchant account infrastructure, with the PSP absorbing the acquiring relationship and underwriting risk.
For the merchant, this has three practical effects:
- Faster setup. A traditional merchant account application can take days to weeks. PSP onboarding typically takes minutes, with identity verification run automatically.
- No direct acquiring relationship. The PSP handles the acquirer. You do not negotiate rates with a bank, manage reserve requirements directly, or hold a dedicated MID.
- Shared risk pooling. Because many merchants share the PSP's infrastructure, the PSP manages aggregate chargeback and fraud rates across its portfolio. Low-volume merchants benefit from this pooling, but can face account holds or terminations if their own metrics drift outside acceptable ranges.
For most early-stage SaaS companies, a PSP removes the overhead of obtaining a merchant account while providing immediate card processing. The real question then becomes whether the PSP model is the right architecture for the business at all.
New to these terms? Start with the primer in What Is a Merchant of Record? for a full breakdown of how MoR compares to a PSP across tax, compliance, and liability.
Beyond the PSP model: Merchant of Record
The PSP model handles payment mechanics but leaves you responsible for tax collection, chargeback disputes, and regulatory requirements in each jurisdiction. As a SaaS company scales into new markets, those responsibilities accumulate fast.
A Merchant of Record is a different model entirely. The MoR is the legal entity of record in each transaction. It appears as the seller, holds the acquiring relationship, and assumes full legal responsibility for tax collection and remittance, chargeback liability, and compliance with local payment regulations.
Under an MoR model, the SaaS company is not the merchant — the MoR is. Your product, pricing, and customer relationships stay entirely yours. From a legal standpoint, the MoR acts as the seller in each transaction, reselling your software to end customers. You receive net revenue payouts; the MoR handles every downstream obligation. Waffo Pancake puts it simply: "We're the seller. You focus on building."
What this means in practice. When Waffo Pancake acts as MoR for a SaaS company, the flow works like this:
- A customer in France pays €49 (VAT-inclusive) for your product at checkout.
- Pancake processes the payment as the legal seller on record.
- Pancake calculates and collects 20% French VAT at the point of sale.
- Pancake settles the net amount to you in USD and remits the VAT to the French authorities on the applicable schedule.
- You receive clean net revenue — with no French VAT registration, no local acquiring relationship, and no separate merchant account for European transactions.
Because Pancake becomes the merchant and legal seller of record, you do not need to form an LLC or hold a foreign tax registration to start selling. Pancake's existing infrastructure covers it across 173 countries (23 sanctioned countries are blocked).
MoR vs. PSP: the structural difference
Many founders conflate an MoR with a PSP. 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. The choice is not primarily technical. It is a compliance and risk-allocation decision.
| Dimension | PSP (e.g. standard Stripe) | Merchant of Record |
|---|---|---|
| Legal seller on record | Your company | The MoR |
| Tax calculation | Add-on / extra cost | Included |
| Tax filing and remittance | Your responsibility | The MoR's responsibility |
| Tax audit liability | Your company | The MoR |
| Chargeback and fraud liability | Your company | The MoR |
| Setup speed | Minutes | Single integration |
| Compliance overhead for you | Grows with each new market | Near zero |
| Business entity to start | Often required | No LLC required with Pancake |
| Best fit | Domestic-first, in-house compliance | Global SaaS, compliance-constrained teams |
A PSP moves money. An MoR moves money and absorbs legal responsibility. That is the structural difference.
The line between the two models is blurring. Stripe launched Stripe Managed Payments in 2025, acting as Merchant of Record for digital goods sold through its checkout in a set of launch countries. The comparison above still describes a standard PSP setup, which remains the default for most Stripe accounts — so confirm which model you are actually on before assuming tax is handled.
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% Japan Consumption Tax, 20% VAT in France, or US state sales tax across 45+ states — then collects, remits, and reports it. Pancake handles EU VAT through the OSS scheme and UK VAT, so you do not register for, file, or remit tax in covered markets.
Legal, chargeback, and fraud 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 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 carries a Merchant of Record statement in the footer. Each product can be priced in multiple currencies through an ISO 4217 price map, with settlement in USD.
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).
Do you actually need a merchant account?
The answer depends on what you mean by the question.
- Apply for a traditional merchant account directly with a bank? For most SaaS startups and growth-stage companies, no. The overhead of a direct acquiring relationship — underwriting, reserve negotiations, MID management — outweighs the benefits at typical volumes. A PSP or MoR handles the acquiring layer for you.
- Need your own dedicated MID eventually? At very high volume, roughly $10M or more in monthly processing (a general industry benchmark), some companies negotiate direct acquiring to cut per-transaction costs. This is a later-stage optimization, not a starting point.
- Which payment model is right for your SaaS? The more useful question is PSP versus MoR. That decision turns on two variables below.
1. How many markets are you selling into? One or two domestic markets: a PSP can work with separate tax tooling. Three or more international markets: maintaining active registrations, quarterly filing schedules, and audit exposure in each jurisdiction typically requires in-house resources or external tax counsel — a recurring cost that compounds with every new market. An MoR removes it.
2. Do you have dedicated legal, finance, and tax resources? A PSP model assumes you have internal capacity, or external counsel, to handle compliance as you scale. An MoR model assumes you would rather pay a per-transaction fee to eliminate that overhead. For many teams, the total cost of operating a PSP plus tax tooling, legal counsel, and filing infrastructure across several markets approaches or exceeds the MoR fee.
Transparent, predictable pricing
A merchant account comes with negotiated rates and reserve terms you have to manage. Pancake takes the opposite approach and publishes every fee, with no monthly fees and no setup costs.
3.9% + $0.50per successful transactiondocs.waffo.ai/mor/fees $0monthly + setup feesdocs.waffo.ai/mor/fees| Fee | Amount |
|---|---|
| Successful transaction | 3.9% + $0.50 |
| Failed transaction | $0.30 per attempt once 3DS is triggered; $0 otherwise |
| Refund | $1.00 (original transaction fee not returned) |
| Payout | 1% of amount, minimum $10.00 |
| Chargeback | $25.00 first · $10.00 representment · $25.00 pre-arbitration |
| Monthly / setup | $0 |
There are no surprise reserve policies hidden in a contract and no undisclosed FX markup baked into the rate. What you see is what you are charged.
Every fee, on one page — no monthly minimums, no setup cost.
See full pricingWhen to keep a PSP, and when to switch
A PSP works well when you are selling primarily in one or two domestic markets, your engineering team wants maximum control over billing logic and checkout UX, and you have in-house legal and finance capacity to manage tax compliance.
An MoR becomes the better infrastructure when:
- You are expanding into markets with complex tax obligations — EU VAT, UK VAT, Japan Consumption Tax, US state sales tax.
- Compliance overhead is consuming engineering or finance time that should be on product.
- You have experienced account reserves or freezes from your PSP that disrupted cash flow at a critical moment.
- You would rather not stand up a legal entity and tax registrations just to sell internationally.
For new customer signups, switching to an MoR requires minimal operational change. Migrating existing subscribers takes a structured plan, but most companies onboard new customers through the MoR first and migrate existing subscribers on a schedule, avoiding any forced cutover.
Choosing the right model at the start is significantly less expensive than migrating at scale. The question of whether you need a merchant account usually resolves to a simpler one: which payment model fits your stage and market footprint?
See the side-by-side breakdown of the MoR and PSP models for your product.
Compare Pancake vs. StripeThis 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.
Frequently Asked Questions
Do I need a merchant account to accept payments?
In most cases, no. A merchant account is a bank account at an acquiring bank where card funds settle. Payment Service Providers like Stripe aggregate many businesses under their own shared merchant account, so you get card processing without applying to a bank yourself. A Merchant of Record goes further and becomes the legal seller.
What is the difference between a merchant account and a payment processor?
A merchant account is the holding account at an acquiring bank where card funds are received before transfer to your business bank account. A payment processor handles the technical transmission between your checkout, the card networks, and the acquirer. Most modern processors provide shared merchant account access, so you do not apply for one separately.
What is the difference between a PSP and a Merchant of Record?
A PSP such as standard Stripe moves money from the customer to you while you stay the legal seller, keeping every tax, chargeback, and compliance obligation. A Merchant of Record like Waffo Pancake becomes the legal seller itself, so it registers for, collects, and remits tax and absorbs chargeback and fraud liability in the markets it covers.
Does Waffo Pancake require an LLC or business entity?
No. Pancake becomes the merchant and legal seller of record across 173 countries, so you do not need to form an LLC, hold a local acquiring relationship, or register for foreign tax to start selling. You license your product to Pancake, and Pancake resells it to your customers as the seller on the transaction.
How much does Waffo Pancake cost compared to a PSP?
Pancake charges 3.9% + $0.50 per successful transaction, with no monthly fees and no setup costs. A standard PSP advertises a lower headline rate but leaves tax tooling, filing, and audit liability with you. Once you sell into several taxed markets, the bundled MoR fee often offsets that separate compliance spend.
Can I use both a PSP and a Merchant of Record?
Technically yes, but running one market through a PSP and another through an MoR creates dual reconciliation systems and splits compliance reporting across models. Most teams choose a clean approach: onboard new customers through the MoR first, then migrate existing subscribers on a schedule rather than forcing a single cutover.
When does it make sense to apply for a direct merchant account?
At very high volume — roughly $10M or more in monthly processing, a general industry benchmark — some companies negotiate a direct acquiring relationship for lower per-transaction rates and tighter control over routing and reserves. Below that level, the underwriting and reserve overhead of a direct merchant account outweighs the savings for most businesses.
What payment methods does Waffo Pancake support?
Pancake's two-step checkout accepts Visa and Mastercard, Apple Pay, and Google Pay, and renders in English, Chinese (Simplified), and Japanese. Each product can be priced in multiple currencies through an ISO 4217 price map, so customers see local pricing while you settle in USD.
Waffo Pancake is a Merchant of Record platform for developers and solo founders — we handle global payments, tax, and compliance across 173 countries so you can focus on building. Our team writes these guides from hands-on payments and billing experience.
About Waffo Pancake →
