MERCHANT OF RECORD
Merchant of Record for SaaS: Sell Globally in 2026
Anyway Team
· 7 min read ·
A Merchant of Record for SaaS is the legal seller for covered customer transactions. It collects payment, calculates and files applicable sales tax, VAT, or GST, issues transaction documents, manages refunds and disputes, and pays the SaaS business its net revenue. For a founder, that turns many separate payment and tax jobs into one operating model.
Why SaaS needs more than a checkout
A checkout can accept a card. A global SaaS business also needs to answer questions that appear after the customer clicks “Buy”:
Which entity appears as the seller on the order?
Does the buyer owe sales tax, VAT, or GST?
Who collects and files that tax?
What happens when a subscription renews?
Who issues the invoice or receipt?
How do refunds and disputes affect the balance?
How does the founder receive the remaining revenue?
These are operating questions, not edge cases. A recurring product creates a new transaction at every renewal, and every transaction needs a clear legal seller and an accurate financial record.
What a Merchant of Record does for SaaS
The Merchant of Record, often shortened to MoR, sits between the SaaS product and the buyer for the sale. The customer purchases from the MoR, while the founder continues to build, host, and support the software.
For covered sales, a SaaS MoR normally handles:
Payment collection. The MoR provides checkout and records the order.
Transaction tax. It calculates, collects, and files applicable sales tax, VAT, or GST.
Invoices and receipts. The customer receives documents that name the legal seller for the transaction.
Subscription billing. Recurring plans create renewal records under the same commercial setup.
Refunds and disputes. The MoR manages the payment-side process and adjusts the merchant balance.
Payouts. The SaaS business receives net revenue after tax, fees, and applicable adjustments.
This is different from a payment processor. A processor moves money, while the SaaS company usually remains the legal seller and keeps the related tax duties. The distinction is explained in Merchant of Record vs payment processor.
How Anyway supports a SaaS sale
Anyway is a Merchant of Record built for developers selling software and digital products. Its current public offer combines hosted payment links, checkout, one-time payments, recurring subscriptions, transaction tax, invoices, receipts, orders, balances, and payouts.
The published price is 3.9% + $0.50 per successful transaction, with no monthly fee and no setup fee.
Start with a product and payment link
Create a product, set its price and billing type, and publish the customer-facing payment link. The link can be attached to a pricing-page button without building a checkout from scratch.
For a recurring product, Anyway supports weekly, monthly, and annual subscription plans. For lifetime access, a credit pack, or another fixed purchase, use a one-time payment.
Connect the order to your app
Use the paymentLinkUrl returned for the published product and add a stable internal reference in its query parameters. That reference lets your server match the paid order to the correct user or purchase record.
After payment, use a signed webhook and a server-side order check before granting access. Keep entitlement logic inside your application so repeated delivery produces one activation.
Read SaaS payment webhooks for the event-handling pattern and payment links for SaaS for a launch-ready checkout flow.
Keep sales and payouts visible
The Anyway workspace records orders and financial balances. This gives the founder a direct path from a customer payment to an order record and then to available net revenue. Approved merchants can add an eligible payout destination and submit a payout request when the documented minimum is met.
For China-based founders, Anyway’s current payout documentation includes Alipay and mainland China bank options. Eligibility and merchant approval still follow the platform’s review process.
When a SaaS founder should choose an MoR
A Merchant of Record is a strong fit when the product is ready to sell but the founder does not want to operate the full legal-seller stack alone.
Common cases include:
A solo founder launching the first paid version of a web app
A SaaS team selling subscriptions to customers in several countries
An AI product selling plans or prepaid credit packs
A developer who wants a hosted checkout and server-side order events
A business that wants sales tax, VAT, and GST handled within the transaction flow
A founder who wants clear order, fee, and payout records in one workspace
An established company may choose to remain the direct seller when it already has payment, tax, accounting, and customer-transaction operations in place. The key decision is who should carry the legal and administrative work attached to each sale.
A SaaS launch checklist
1. Make the offer reviewable
Publish a working website with the product name, features, price, delivery terms, refund policy, privacy policy, terms, and support contact. The checkout description should match the website.
2. Choose the billing model
Use a one-time price for a fixed purchase or credit pack. Use a recurring plan when access renews on a schedule. If the app meters tokens, minutes, or API calls, keep that usage ledger in the product and map it to the plan sold at checkout.
3. Create a stable purchase reference
Generate the purchase in your database before redirecting the buyer. Pass only a non-sensitive reference through the payment URL.
4. Verify paid status on the server
Treat the browser return page as a customer experience, not final proof of payment. Grant service after the server verifies the order and product.
5. Test the complete lifecycle
Test a successful purchase, duplicate webhook delivery, refund, subscription renewal, cancellation, and entitlement removal. Check that the amount and currency in your app match the order record.
6. Reconcile revenue regularly
Match orders, fees, adjustments, available balance, and payout records. SaaS payment reconciliation provides a practical routine.
Merchant of Record pricing in context
The right comparison is not MoR fees versus card-processing fees alone. Direct selling can require payment processing, tax calculation, registrations, filings, invoice logic, dispute operations, reporting, and payout administration.
Anyway publishes one transaction price for the MoR service: 3.9% + $0.50. That price includes the checkout-to-compliance role described on its website, with no monthly or setup fee. Founders can model the cost against average order value and compare it with the time and services required to run the same work directly.
Build the product; give every sale a clear owner
Global SaaS payments work best when payment, tax, customer documents, orders, and payouts follow one traceable transaction. A Merchant of Record supplies that commercial layer while the founder remains focused on product delivery and growth.
Anyway gives SaaS founders a developer-friendly route from product setup to paid order, subscription, tax handling, and net payout under one MoR model.
Frequently asked questions
What is a Merchant of Record for SaaS?
It is the legal seller for covered SaaS transactions. It collects payment, handles applicable transaction tax, issues invoices or receipts, manages payment-side refunds and disputes, and pays net revenue to the SaaS business.
Does a Merchant of Record own the SaaS product?
No. The founder or company continues to own and operate the product. The MoR is the seller for the customer transaction under the service agreement.
Can a Merchant of Record handle subscriptions?
Yes. Anyway supports one-time payments and recurring subscriptions, including weekly, monthly, and annual plans listed on its current website.
Does Anyway handle sales tax, VAT, and GST?
Anyway states that it calculates, collects, and files applicable sales tax, VAT, and GST as Merchant of Record for covered sales.
How much does Anyway cost?
Anyway currently publishes a fee of 3.9% + $0.50 per successful transaction, with no monthly fee and no setup fee.
Can I connect an Anyway payment to a SaaS user account?
Yes. Pass a stable purchase reference with the payment link, then use the signed webhook and server-side order data to activate the correct account.