What Is a Merchant of Record? Who's Liable for the Sale
What is a merchant of record? See who carries chargeback, sales tax and VAT liability, and when an MoR platform beats your own merchant account.

Photo: Pixabay
On this page 6 sections
- How Visa Defines the Merchant in a Card Sale
- Merchant of Record Liability: Who Owns Each Duty
- Merchant of Record vs. Seller of Record vs. Payment Facilitator
- Worked Example: When a Merchant of Record for SaaS Stops Paying Off
- Signs an MoR Fits, and Signs You've Outgrown It
- Settle the Card-Data Exit Before You Sign
Key takeaways
- A U.S. company with no business location in the EU owes EU VAT on its first sale to an EU consumer. The €10,000 threshold applies only to sellers based in the EU.
- A payfac doesn't become the seller. Under Visa's rules you're still the merchant, so disputes come to you. Because you're also still the seller, state sales tax collection stays your job.
- To find your break-even, divide your monthly in-house compliance cost by the MoR's fee premium. Recheck it every quarter, because the premium grows with every sale.
- Before you sign with an MoR, get its stored-card export terms in writing. Those terms decide whether you can leave later without losing subscribers.
What is a merchant of record? It's the business that legally makes a card sale. Its name appears on the customer's card statement and its merchant account takes the payment. It is also responsible for the chargebacks, refunds and sales tax or VAT that come with the transaction. If you take payments through your own merchant account, you are the merchant of record. If you sell through an MoR platform, the platform resells your product to the customer and takes on most of that liability in exchange for a higher fee.
Software and subscription sellers usually face this choice first, and ticketing and digital-goods businesses aren't far behind. The trade is easy to describe and harder to price. You pay more per sale, and in return you hand off compliance work you may not have the staff to handle.
How Visa Defines the Merchant in a Card Sale
Every card transaction has a merchant attached to it. That merchant signs an agreement with an acquiring bank, either directly or through a processor or ISO. It receives the settled funds, and the card networks hold it responsible for the sale.
The networks also care whose name the cardholder sees. Visa's Merchant Data Standards Manual gives the example of a magazine sold through a third party. It concludes that the merchant name "must be the name of the magazine," because that is the name the cardholder saw. The statement descriptor matters for the same reason: people dispute charges they can't place.
For most businesses the question never comes up, because the company and the merchant of record are the same entity. It starts to matter when a third party steps into the sale. Visa's Payment Facilitator and Marketplace Risk Guide treats a marketplace that contracts with the acquirer as the merchant of record, not the underlying seller. App stores, reseller checkouts for SaaS companies and ticketing platforms that sell seats for promoters work the same way. The customer is legally buying from the platform, and the platform's name is on the statement. The platform then pays the creator after taking its cut.
Merchant of Record Liability: Who Owns Each Duty
An MoR takes on three main kinds of responsibility, and each looks a little different once you read the contract.
Chargebacks and the Dispute Ratio
Disputes go to the merchant of record. The MoR gets the notice from its acquirer and decides whether to fight. If it fights, it builds the evidence file. Either way, the chargeback counts toward its own dispute ratio. If you've never worked a dispute, reading chargeback reason codes shows how much evidence each type demands.
That ratio has consequences with the card networks. The Visa Acquirer Monitoring Program (VAMP) went live on April 1, 2025, and enforcement began October 1, 2025. VAMP combines fraud reports and disputes into a single ratio. The threshold for an "excessive" merchant started at 2.2%. On April 1, 2026, it dropped to 1.5% for merchants in the U.S., Canada, the EU and Asia-Pacific.
Thresholds vary by region, and acquirers can set stricter limits of their own, so ask your processor which one applies to you. Mastercard runs its own monitoring program. Our explainer on chargeback ratio thresholds and how close is too close covers how these programs escalate. Behind an MoR, your disputes count toward the platform's numbers instead of yours.
Read the contract before you treat that as free protection. Many MoR agreements pass refunded amounts and dispute fees back to the seller, and some pass fraud losses back too. Most also reserve the right to hold payouts or end the relationship if your product draws too many disputes. Under network rules the liability moves to the MoR, but the contract can send much of the financial risk straight back to you.
Sales Tax and VAT
Tax is the main reason software and digital product sellers use an MoR. Tax liability comes from tax law, not card network rules. Because the MoR resells your product, tax authorities generally treat it as the seller. It collects and pays the tax owed where the customer is located, whether that's a U.S. state's sales tax or a foreign VAT.
In the U.S., the duty to collect follows economic nexus. That means making enough sales into a state to owe its tax even with no physical presence there. In South Dakota v. Wayfair (2018), the Supreme Court upheld a South Dakota law with a yearly test. Out-of-state sellers had to collect once they delivered more than $100,000 of goods or services into the state or made 200 or more separate sales there. Every state with a sales tax now sets its own thresholds. States also treat SaaS and digital products inconsistently, taxing some kinds of software and exempting others.
Abroad, the rule that catches U.S. sellers off guard is the small-seller threshold. EU VAT on digital services sold to consumers is due in the customer's country. Businesses based in the EU get a €10,000 EU-wide threshold before that rule applies. Sellers based outside the EU don't, so a U.S. SaaS company owes VAT on its first sale to an EU consumer. The EU's non-Union One Stop Shop is for businesses with no EU establishment that sell services to EU consumers. You register in one member state and pay the VAT for every EU country there. Our guide to EU VAT rules for U.S. sellers covers registration.
On your own merchant account, all of this is your job. You register wherever you owe tax, make sure checkout calculates it correctly, and file on every jurisdiction's schedule. This is general information, not tax advice, so confirm your obligations with a qualified tax professional.
Refunds and Subscription Law
The MoR issues the receipt and processes refunds, and consumer-protection laws look to it first. Many MoRs enforce their own refund policy, which may be more generous than yours. For subscriptions, state automatic renewal laws set disclosure and cancellation requirements. Our guide covers what subscription businesses must disclose under auto-renewal laws. The federal click-to-cancel rule was vacated, but other subscription rules still apply. An MoR typically runs the checkout disclosures and the cancellation flow, but you're still responsible for what your product and your marketing promise.
Merchant of Record vs. Seller of Record vs. Payment Facilitator
People use these terms loosely, but the differences decide who owes what. They also come from two different rulebooks. Card network rules decide who the merchant is and who receives disputes. State and foreign tax law decides who has to collect tax.
Seller of record. Many people treat this as another name for merchant of record. When the two are separated, "seller of record" is the tax and legal term for the entity that owns and sells the goods. "Merchant of record" is the payments term for the entity whose name and account are on the card transaction.
The two roles split on marketplaces, where a third-party seller owns the inventory and the marketplace runs the card sale. Every state with a statewide sales tax now has a marketplace facilitator law that makes the marketplace collect and pay tax on third-party sellers' sales. Hawaii is the exception: it's the one state where selling through a marketplace facilitator doesn't fully release the seller from collecting.
Payment facilitator. A payfac, the model behind many all-in-one payment apps, signs businesses up as sub-merchants under its own relationship with the acquirer. Visa's Merchant Data Standards Manual defines a payfac as an entity that deposits transactions or receives settlement for a merchant but doesn't sell goods or services to cardholders itself. That last part is what separates a payfac from an MoR: it doesn't become the seller.
That leaves you with both sets of duties. On the network side, Visa's payment facilitator model applies all merchant requirements equally to sponsored merchants. You're still the merchant, so disputes come to you. On the tax side, the payfac only moves the money and doesn't resell your product, so you're still the seller, and state sales tax collection stays your job. The descriptor can show your name alone or combined with the payfac's. Acquirers are responsible for both the payfac and its sub-merchants, which is why payfacs often freeze or close accounts quickly when risk spikes.
| Your own merchant account | Payment facilitator | Merchant of record platform | |
|---|---|---|---|
| Name on customer's statement | Yours | Yours, alone or with the payfac's name | The platform's |
| Who receives chargebacks (network rules) | You | You | The platform (losses often passed back by contract) |
| Who collects and pays sales tax or VAT (tax law) | You | You | The platform |
| Who controls stored card data | You, through your gateway | You, within the payfac's limits | The platform |
| Pricing structure | Processing rates, with compliance costs on top | Usually a flat rate | Higher all-in rate |
| Underwriting | Full review up front | Light at signup, then ongoing monitoring | The platform reviews your product and business |
Worked Example: When a Merchant of Record for SaaS Stops Paying Off
The decision comes down to one formula. Start with what handling compliance yourself would cost each month, including tax software, registrations and accounting help. Divide that by the MoR's fee premium, meaning the extra share of each sales dollar the MoR keeps compared with your own processor. The result is the monthly revenue at which the two options cost the same. Below that level the MoR is cheaper. Above it, your own account is.
If either side charges a per-transaction fee, convert it to a percentage of your average sale first. For example (illustrative), a $0.50 fee on a $25 average sale adds 2 percentage points.
The numbers below are illustrative, not quotes. Real pricing depends on the provider, your volume and your risk profile.
Assumptions: A U.S. SaaS company sells a monthly plan. About a third of its customers are outside the U.S., including some EU consumers. The MoR's all-in fee is 2.5 percentage points higher than the rate on the company's own merchant account. Handling compliance in-house, including a non-Union One Stop Shop registration, would cost $800 a month.
Break-even: $800 ÷ 0.025 = $32,000 in monthly revenue.
At $50,000 a month, the MoR premium is $1,250. Subtract the $800 the company would otherwise spend on compliance, and the MoR costs $450 a month more. For that, the platform handles dispute responses and foreign VAT filings. A small team with no finance hire could reasonably decide that's money well spent.
Now grow the same company to $200,000 a month. The premium is $5,000. Assume in-house compliance rises to $1,500 as the company registers in more U.S. states. The MoR now costs $3,500 a month more, or $42,000 a year. That would pay for part-time finance help with money left over. The percentage fee grows with every sale, while compliance costs rise in steps, so recheck the gap every quarter.
Signs an MoR Fits, and Signs You've Outgrown It
An MoR tends to make sense when:
- You sell digital products or SaaS across many states or countries, and nobody on staff owns tax compliance.
- Revenue is below your break-even point, so the premium is small in dollars.
- Your product isn't on the platform's prohibited list. Many MoRs turn away regulated or higher-risk categories.
- Handling dispute responses in-house isn't realistic yet.
Your own merchant account usually wins when:
- Revenue is comfortably above break-even.
- Most sales are domestic, or come from places where you're already registered.
- You want control of checkout and payment retry logic, or want to raise approval rates on stored cards with network tokens.
- You sell something MoR platforms won't carry, which is where a high-risk merchant account comes in.
Events and ticketing sellers also need to settle who pays local admissions or amusement taxes, because some cities tax tickets separately from state sales tax. Our piece on Chicago's amusement tax for tickets and streaming shows how specific those rules can be. If a ticketing platform is the merchant of record, get it in writing whether the platform files those taxes or leaves them to you.
Settle the Card-Data Exit Before You Sign
The stored-card clause decides how hard it will be to leave an MoR. Ask whether the platform will export your customers' card data to a new PCI DSS-compliant processor if you leave, and get the timeline and cost in writing. Without an export, switching means asking every subscriber to re-enter a card, and some of them never will.
If you're thinking about moving to your own account, MannyPay offers merchant accounts and gateways for online payments, with integrations for Shopify, WooCommerce, Authorize.net and NMI. For overseas customers, MannyPay also provides international payment processing with multi-currency acceptance. Start by pulling last quarter's sales by customer state and country, then run the break-even formula with your own figures. Bring those numbers when you request a free processing quote, and a MannyPay specialist will respond within one business day.
Sources
- Visa Merchant Data Standards Manual
- Visa Payment Facilitator and Marketplace Risk Guide
- Visa's Payment Facilitator Model
- Visa's Acquirer Monitoring Program (VAMP): Updated 2025 Guide (Optimized Payments)
- Visa VAMP Threshold April 2026: What Merchants Must Know (Justt)
- South Dakota v. Wayfair, Inc. (Cornell LII)
- Marketplace Facilitator Laws, Explained (TaxJar)
- Understanding the Tax Obligations of Marketplaces in the US (Stripe)
- EU VAT One Stop Shop (Your Europe, European Union)
- Non-Union Scheme, One Stop Shop (Irish Revenue)
- EU VAT for Online Sellers 2026: OSS & IOSS (Taxually)
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.


