MERCHANT OF RECORD
Merchant of Record vs Payment Gateway: What’s the Difference?
Anyway Team
· 6 min read ·
A payment gateway securely sends payment information from checkout into the payment network. A Merchant of Record is the legal seller for a covered transaction and is responsible for payment collection, applicable transaction tax, customer documents, refunds, disputes, and the financial record of the sale.
The gateway is a technology layer. The Merchant of Record is a commercial and legal role. A single customer checkout may involve both.
Merchant of Record vs payment gateway at a glance
Area: Main role; Payment gateway: Passes payment data into the processing flow; Merchant of Record: Acts as seller for covered transactions
Area: Legal seller; Payment gateway: The connected merchant is usually the seller; Merchant of Record: The MoR is the seller
Area: Checkout; Payment gateway: Often provides or connects to a checkout form; Merchant of Record: May include hosted checkout as part of the MoR service
Area: Payment processing; Payment gateway: Connects with processors and financial networks; Merchant of Record: Arranges payment processing for its sales
Area: Sales tax, VAT, and GST; Payment gateway: Not part of the gateway role by itself; Merchant of Record: Calculated, collected, and filed by the MoR where applicable
Area: Invoice or receipt; Payment gateway: Merchant supplies it through its systems; Merchant of Record: MoR issues the transaction document
Area: Refund and dispute role; Payment gateway: Supplies technical payment controls; Merchant of Record: Owns the payment-side process as seller
Area: Merchant payout; Payment gateway: Not defined by gateway status alone; Merchant of Record: MoR pays net revenue under its merchant terms
What a payment gateway does
The gateway is the digital equivalent of the payment terminal at a physical counter. It gathers the buyer’s payment information and sends it into the authorization flow. In a hosted checkout, the gateway provider may also supply the entire payment page.
Typical gateway functions include:
Displaying payment fields or a hosted checkout
Sending payment data for authorization
Returning an approved, declined, or pending response
Applying security controls to the payment session
Passing transaction results to the merchant’s application
A gateway answers, “Can this payment be submitted and authorized?” It does not, through gateway status alone, answer, “Who sold the product?”
What a Merchant of Record does
The Merchant of Record answers the seller question. Its name appears on the customer transaction and it carries the payment, tax, and recordkeeping duties agreed for that sale.
For digital products and SaaS, an MoR commonly provides:
Checkout and payment collection
Sales tax, VAT, and GST handling where applicable
Invoices and receipts under the seller details
Subscription transaction records
Refund and dispute administration
Merchant balances and net payouts
Order information for delivery and reconciliation
The MoR can use a payment gateway behind the scenes. That does not make the terms interchangeable: one is part of the payment technology, and the other is the seller.
Where each layer sits in a SaaS purchase
Consider a customer buying a monthly web-app plan.
The customer clicks the pricing-page button.
The checkout displays the plan and gathers payment information.
The gateway sends the payment request into the network.
The transaction is authorized and recorded.
The legal seller issues the invoice or receipt and handles applicable tax.
The SaaS app receives a server-side event and activates access.
The merchant later reconciles the order and payout.
The gateway is most visible at steps two and three. The Merchant of Record defines the seller responsibility across the sale.
Why the difference matters for SaaS founders
Tax does not end at checkout
A gateway may pass an amount that includes tax, but another party must determine the rate, collect the amount, file the return, and keep the evidence. If your company is the direct seller, that responsibility belongs to your company. If an MoR is the seller, the MoR handles applicable transaction tax for covered sales.
A receipt needs the correct seller
Payment confirmation and a legally useful transaction document are not always the same thing. The invoice or receipt should identify the seller and include the information required for the transaction and region.
A subscription creates repeated sales
Every renewal must be authorized, recorded, taxed as applicable, and connected to the customer’s access. A gateway can carry each payment request. The MoR model also gives each renewal a consistent seller and tax record.
Payouts need a traceable order history
Founders need to explain how gross customer payments become net merchant revenue. The record should connect orders, tax, fees, refunds, adjustments, and payouts. SaaS payment reconciliation shows how to keep that chain clear.
Gateway-only setup or MoR setup?
A gateway-based direct-seller setup fits when
Your company wants to be the legal seller
It already has the entity and financial setup for the target markets
The team runs its own tax, invoicing, refund, and reporting processes
It wants to select and connect each layer separately
A Merchant of Record setup fits when
The provider should be the seller for covered transactions
The product will be sold across several tax regions
Checkout, tax, customer documents, and payout should share one transaction record
The team wants a shorter path from a working product to global sales
For the related processing role, see Merchant of Record vs payment processor.
How Anyway combines checkout with the MoR role
Anyway provides the customer-facing payment link and also acts as Merchant of Record for covered sales. That means the hosted checkout is connected to the legal-seller, tax, invoice, receipt, order, subscription, balance, and payout flow.
The current public price is 3.9% + $0.50 per successful transaction, with no monthly fee and no setup fee.
A SaaS founder can:
Create a product and one-time or recurring price.
Publish the returned payment link on the website.
Add a stable internal purchase reference to the URL.
Receive the signed order webhook on the server.
Verify the order before granting access.
Review orders and balances in the Anyway workspace.
Request a payout to an approved destination when eligible.
This gives one purchase a consistent path from checkout to the merchant’s revenue record. Read payment links for SaaS for implementation details.
Questions to ask any provider
Before selecting a checkout or MoR, ask:
Who is named as the legal seller?
Which sales and product types are covered?
Who calculates, collects, and files transaction tax?
Whose details appear on invoices and receipts?
Which one-time and recurring billing schedules are supported?
What event proves that an order is paid?
How are refunds and disputes recorded?
How do orders map to merchant balances and payouts?
What fees apply to a successful transaction?
The answers will show whether you are comparing two gateway features or two different selling models.
Choose the role before the checkout design
A polished checkout matters, but the seller model determines the work that follows the payment. A gateway moves the payment request. A Merchant of Record owns the covered customer sale.
Anyway joins both parts in a developer-friendly product: a hosted payment experience backed by the MoR role, transaction-tax handling, customer documents, order events, subscriptions, and payouts.
Frequently asked questions
Is a payment gateway a Merchant of Record?
Not by default. A gateway is a payment-technology layer. A provider is an MoR only when it contracts and operates as the legal seller for the covered transaction.
Can a Merchant of Record use a payment gateway?
Yes. An MoR can use gateway and processing technology to collect customer payments while remaining the legal seller.
Does a gateway file sales tax?
Tax filing belongs to the direct seller or its chosen tax service in a gateway setup. An MoR handles applicable transaction tax for the sales it covers.
Is Anyway a gateway or an MoR?
Anyway supplies hosted payment links and checkout while acting as Merchant of Record for covered Anyway Business sales.
Does Anyway support recurring payments?
Yes. Anyway currently lists weekly, monthly, and annual subscriptions alongside one-time payments.