A merchant of record is the legal entity that appears on a buyer’s credit card or bank statement and carries that transaction’s tax, regulatory, and dispute obligations. In practice, it buys the product from the original seller and immediately resells it to the customer, making itself the legal seller for everything downstream: sales tax registration and remittance, chargebacks, refunds, and consumer protection compliance. If you sell digital products, subscriptions, or physical goods across multiple tax jurisdictions, using a merchant of record shifts a large block of legal exposure off your company and onto the entity whose name shows up on the statement.
How the Arrangement Actually Works
The mechanic is a resale. A software company, course creator, or marketplace seller partners with a merchant of record, and that entity becomes the legal seller in every customer transaction. The customer’s bank statement shows the merchant of record’s name, not yours. That placement is not cosmetic. It determines which entity a card network, tax authority, or regulator holds accountable when something goes wrong.
Because the merchant of record takes legal title to the product, even if only for a fraction of a second in what the industry calls a “flash title” arrangement, it owns the compliance chain. It collects and remits sales tax, handles chargebacks, processes refunds, and responds to regulatory inquiries. You receive a payout after those obligations are met, minus fees. That is what insulates you from direct exposure to tax audits, payment disputes, and consumer claims in jurisdictions where your company has no presence.
An acquiring bank moves the actual money. It settles card transaction proceeds into the merchant of record’s account and then distributes funds to you.1Office of the Comptroller of the Currency. Comptroller’s Handbook – Merchant Processing The acquiring bank keeps risk of loss and responsibility for settlement with the card network, which is why banks vet merchant of record applicants heavily before granting accounts.
What It Does for Your Sales Tax Obligations
Calculating and collecting the right amount of sales tax, VAT, or GST on every transaction is one of the main reasons businesses use a merchant of record. The tax owed depends on where the buyer is located. For a digital product sold globally, that means tracking rates across thousands of jurisdictions. U.S. sales tax rates vary significantly by state and locality; VAT rates in some European countries exceed 25% for digital goods.
The 2018 Supreme Court decision in South Dakota v. Wayfair established that a state can require a business to collect sales tax without a physical presence there, as long as the business crosses an economic activity threshold. South Dakota’s benchmark was $100,000 in annual sales or 200 separate transactions delivered into the state.2Congress.gov. State Sales and Use Tax Nexus After South Dakota v. Wayfair Most states have since adopted their own economic nexus rules, often modeled on that threshold, though the exact numbers differ.
Marketplace Facilitator Laws
Nearly every state with a sales tax has enacted marketplace facilitator laws that shift the obligation to collect and remit tax from individual sellers to the platform or entity facilitating the sale. A merchant of record acting as the legal seller falls squarely within these laws and must register, collect, and file returns in each applicable state. The compliance burden is real: every state has its own registration process, filing frequency, product taxability rules, and rate structures. There is no federal sales tax framework unifying these requirements.
For a business selling nationwide, using a merchant of record eliminates the need to register for sales tax permits in every state where you meet economic nexus. The merchant of record handles those registrations, files the returns, and remits the taxes. Failing to remit collected tax can trigger interest penalties, personal liability for company officers, and in extreme cases, criminal prosecution for tax evasion.
Form 1099-K Reporting
When a merchant of record collects payments from customers and distributes proceeds to underlying sellers, it takes on federal tax reporting obligations under 26 U.S.C. § 6050W. The entity that submits instructions to transfer funds to a participating payee is responsible for issuing Form 1099-K reporting the gross amount of reportable transactions.3Office of the Law Revision Counsel. 26 USC 6050W
Reporting rules split by transaction type. For payment card transactions, the merchant acquiring entity must report all payments to participating payees with no minimum dollar threshold. For third-party network transactions processed through a third-party settlement organization, reporting is required only when payments to a single payee exceed $20,000 and involve more than 200 transactions in a calendar year.4Internal Revenue Service. Understanding Your Form 1099-K Congress passed legislation to lower that threshold significantly, but the IRS has issued repeated transitional relief delaying full implementation.
Even when a merchant of record contracts with a third party to prepare and file these returns, it remains liable for penalties under IRC sections 6721 and 6722 if the reporting is wrong or late.5Internal Revenue Service. Form 1099-K FAQs – Third Party Filers of Form 1099-K The entity’s name, address, and taxpayer identification number must appear on every 1099-K it files, regardless of who physically prepares the form.
Chargebacks and Dispute Liability
Because the merchant of record’s name sits on the buyer’s statement, card networks and issuing banks hold it responsible when a customer disputes a charge. The merchant of record gathers evidence that the transaction was legitimate and the product was delivered, then presents that case to the issuing bank within tight deadlines. If the bank rules for the customer, the merchant of record absorbs the lost revenue plus a chargeback fee that generally runs $20 to $100 or more per dispute, depending on the acquiring bank and the business’s risk profile.
Card Network Monitoring Programs
Visa and Mastercard both run programs that flag merchants with elevated dispute rates. Visa’s Acquirer Monitoring Program (VAMP) identifies merchants whose combined fraud and dispute ratio reaches 220 basis points (2.2%) of settled transactions in most regions, with that threshold dropping to 150 basis points (1.5%) as of April 2026.6Visa. Visa Acquirer Monitoring Program Fact Sheet 2025 Mastercard’s Excessive Chargeback Program triggers at 100 chargebacks in a calendar month combined with a chargeback-to-transaction ratio of 1.5% or higher, and a second tier begins at 300 monthly chargebacks with a 3% ratio.
Landing in one of these programs brings escalating consequences: fines, mandatory remediation plans, and ultimately loss of the ability to process cards on that network. For a merchant of record serving hundreds or thousands of sellers, one seller’s problematic product can drag the whole portfolio toward these thresholds. That is why most merchant of record providers monitor individual seller dispute rates closely and suspend sellers who generate too many chargebacks.
Rolling Reserves
To cover potential chargeback losses, acquiring banks typically require a merchant of record to maintain a rolling reserve. The bank withholds a percentage of each transaction, commonly between 5% and 15%, and holds those funds for six months to a year before releasing them. High-risk industries like travel or subscription services face longer hold periods and higher reserve percentages. Those reserves protect the acquiring bank, and the cost passes through to sellers as higher fees or delayed payouts.
Data Protection and PCI Obligations
As the entity collecting payment details, billing addresses, and sometimes shipping information, a merchant of record functions as a data controller for that transactional data under privacy frameworks like the EU’s General Data Protection Regulation. That classification carries weight. The data controller is the entity regulators fine when consent is missing, data subject requests go unanswered, or cross-border data transfers violate the rules. GDPR fines can reach 4% of annual global revenue or €20 million, whichever is higher.
In the United States, the name on the bank statement establishes the merchant of record as the first point of contact for law enforcement or regulatory inquiries about a transaction. If a dispute arises over how customer data was handled, the entity on the statement bears the burden of showing that its practices met applicable standards. State-level privacy laws increasingly impose similar obligations, though the specifics vary. For you as the underlying seller, this offloads a substantial compliance burden. It also means ceding control over customer data to the merchant of record.
On the card data side, PCI DSS version 4.0 became the only active version of the standard after version 3.2.1 retired in March 2024, and 51 future-dated requirements took effect on March 31, 2025.7PCI Security Standards Council. Guidance for PCI DSS E-Commerce Requirements Effective After 31 March 2025 Compliance involves regular audits, penetration testing, and encrypting cardholder data in transit and at rest. Non-compliance penalties come from the card networks through the acquiring bank, not directly from PCI SSC. Early-stage non-compliance at lower volumes may incur penalties around $5,000 per month, while prolonged non-compliance at higher volumes can reach $100,000 per month. A data breach traced to a non-compliant merchant of record adds forensic investigation costs, customer notification expenses, and potential card network fines on top.8PCI Security Standards Council. PCI Security Standards
How It Differs From a Payment Facilitator or Seller of Record
These three models look similar and get confused, and the confusion matters because liability lands in different places.
- A merchant of record takes flash title to the goods and becomes the legal seller. Its merchant account receives settlement funds. It bears primary liability for chargebacks, tax remittance, and regulatory compliance.
- A payment facilitator (PayFac) is a registered intermediary that processes transactions for sub-merchants through its own merchant account but does not take title to the goods. Sub-merchants keep primary liability for their own transactions, and the payment facilitator carries residual liability to its sponsoring bank. Card networks require payment facilitators to register and undergo due diligence, including review of anti-money-laundering procedures and sub-merchant agreements.
- A seller of record is the entity legally responsible for delivering the product, handling returns, and ensuring goods match what was advertised. On platforms where roles split, the marketplace may act as merchant of record for payment and tax purposes while the individual vendor remains the seller of record responsible for product quality, fulfillment, and warranty claims.
A plain payment gateway or payment service provider handles the technical plumbing of moving money but leaves tax collection, chargeback defense, and consumer protection compliance entirely with the seller. If you sell into dozens of tax jurisdictions and do not want to register in each one, a merchant of record solves that problem. If you already handle your own compliance and just need to accept cards, a payment gateway or payment facilitator is lighter-weight.
Contract Terms That Decide Whether the Shield Actually Holds
The agreement between a merchant of record and the businesses using its platform is where liability allocation actually gets decided. A handful of provisions matter more than the rest, and sellers who skip this review tend to find the gaps only after something goes wrong.
- Indemnification. Most merchant of record agreements require the seller to indemnify the merchant of record for losses caused by the seller’s products, including chargebacks stemming from product defects, false advertising, or failure to deliver. The merchant of record handles the dispute process, but the financial loss often flows back to the seller through holdbacks or account deductions.
- Reserve and holdback terms. The contract specifies what percentage of sales revenue the merchant of record withholds as a reserve, how long it holds those funds, and under what conditions the reserve increases. Sellers in higher-risk categories or those with short operating histories face steeper reserves.
- Payout timing. Settlement to the seller rarely happens instantly. Typical payout cycles run from a few days to several weeks, and the contract governs whether delays are permissible during disputes or investigations.
- Termination triggers. Exceeding chargeback thresholds, selling prohibited product categories, or failing to respond to compliance requests can all give the merchant of record grounds to terminate the relationship and freeze remaining funds.
- Data ownership. Because the merchant of record collects customer payment and contact information, the contract should clarify what data the seller can access. Some agreements restrict seller access to customer email addresses or billing details, which limits the ability to build a direct customer relationship.
Pay close attention to how the contract handles tax liability if the merchant of record miscalculates or fails to remit correctly. In most arrangements the merchant of record assumes that risk, but some agreements carve out exceptions for product classification errors where the seller provided incorrect information about what was being sold. Getting the product categorization right at the outset avoids unpleasant surprises during an audit.