What is a Merchant of Record
A Merchant of Record (MoR) is a legal entity that takes on full responsibility for a transaction on your behalf. It becomes the seller of record, collects payment from the customer, and assumes the tax and compliance obligations tied to that sale.
Under the Merchant of Record model, tax and compliance liability shifts to the MoR. Its core responsibilities break down into three areas:
- Tax remittance: Registering, calculating, and remitting local consumption tax such as GST in Singapore or VAT in Indonesia across every jurisdiction it operates in, including tracking rate changes and registration thresholds as they shift.
- Fraud and dispute management: Handling the chargeback process on your behalf, gathering evidence, managing card-network communication, and responding within dispute deadlines. This doesn't mean the MoR absorbs the cost; most agreements still pass the chargeback fee and disputed amount back to you, but you're no longer the one managing the process.
- Regulatory compliance: Maintaining ongoing compliance with frameworks like PCI DSS and AML controls, so you don't need a local entity or a dedicated compliance function in every market just to process regional sales.
Merchant of Record example
Take a Singapore-based ecommerce company expanding into Indonesia and Malaysia without setting up local entities in either market. Without an MoR, that company would need to register for tax separately in Indonesia and Malaysia, monitor rate and threshold changes in both, handle chargebacks and disputes locally, and stay current on two different regulatory systems.
An MoR takes on that entire stack: it becomes the legal seller in each market, collects and remits the applicable tax, and absorbs the compliance burden that would otherwise scale with every new market added.
Merchant of Record model in APAC: regional tax and regulatory compliance
This is where the MoR conversation gets genuinely complicated for businesses operating across Southeast Asia. APAC is more than just a tax regime. It's a patchwork of them, each with different rates, thresholds, and registration triggers for cross-border and digital sales.
A few examples that matter for Merchant of Record APAC compliance if you're selling into the region:
- Singapore: The Inland Revenue Authority of Singapore (IRAS) enforces a 9% GST rate via the Overseas Vendor Registration (OVR) framework. Foreign digital and low-value goods sellers are legally required to register under the OVR regime once they concurrently pass both a S$1 million global turnover threshold and S$100,000 in local sales.
- Indonesia: The Directorate General of Taxes (DGT) regulates cross-border transactions under the Perdagangan Melalui Sistem Elektronik (PMSE) tax framework, applying an effective 11% digital VAT once a foreign seller crosses roughly IDR 600 million in annual transaction value with Indonesian customers.
- Malaysia: The Royal Malaysian Customs Department enforces a flat 10% Low-Value Goods (LVG) tax on imported goods sold online valued at RM500 or less, which must be collected at checkout rather than at the border. Sellers cross this legal registration threshold once their LVG sales exceed RM500,000 a year.
Merchant of Record for ecommerce: what's different (and why it's worth it)
Everything above applies broadly across SaaS, digital goods, and physical ecommerce. But a few things are specific to running an ecommerce business on an MoR.
Why ecommerce businesses use this model
- Faster market entry: Setting up a local entity to sell compliantly in a new country can take months. An MoR lets you start selling in a new APAC market without waiting on that setup.
- Lower audit exposure: Every market you register for tax in is a market where you can get it wrong, miss filings, have rate changes, or breach thresholds. An MoR concentrates that risk with a provider whose entire business depends on getting it right.
- Less strain on a lean finance team: For a mid-market company without a dedicated tax function in every market, an MoR replaces a growing list of local compliance tasks with one vendor relationship.
Where it gets more complicated for physical goods:
Physical goods carry different tax treatment than digital goods. Singapore's GST on imported low-value goods applies specifically to physical, imported products, separate from the digital services VAT regimes that apply to SaaS or downloadable content. An MoR handling both digital and physical SKUs needs to apply the right regime to the right product, not a blanket rate.
Returns and refunds carry more operational weight, too. A SaaS refund is usually a line-item credit. A physical ecommerce return involves logistics, restocking, and reversing tax that's already been collected and remitted, sometimes across a border.
And since MoR checkout pages are often less customisable, cart abandonment is worth watching closely after a switch. Test conversion rates specifically at checkout, not just backend metrics. A compliance win that costs you meaningfully on conversion is worth knowing about early, not discovering in a quarterly review.
What an MoR takes off your plate
Bringing on an MoR means handing off a specific, defined set of obligations.
- Tax collection and remittance: calculating and filing VAT/GST across every market you sell into
- Chargeback and fraud process management: handling disputes on your behalf, though the cost is typically passed back to you.
- Regulatory compliance: KYC, AML, PCI DSS, and local data privacy obligations like Singapore's PDPA
- Payment processing and settlement: running the transaction and moving funds
- Customer-facing billing and refunds: handling disputes as the seller of record
Coverage varies by provider. Some are strong on tax breadth across a wide set of markets but lighter on physical fulfilment support; others handle chargebacks well but cover fewer jurisdictions. Worth confirming the scope in the contract instead of assuming it from the pitch.
Types of merchant of record providers
Not every MoR is built the same way, and the differences matter more than the pitch decks suggest.
- Vertical-specific MoRs (common for SaaS and digital goods) such as global providers like Paddle and FastSpring tend to have the deepest tax coverage for digital services but weaker support for physical fulfilment and returns.
- Marketplace-style MoRs, often used by platforms with multiple sellers, split liability differently. It is critical to audit exactly where the legal boundary of liability sits for each independent vendor rather than assuming uniform protection across your entire SKU catalogue.
- Regional specialists, like platforms that deliberately restrict their geographic footprint to optimise specific cross-border corridors, such as the Southeast Asian market. By focusing on narrower corridors, these specialists offer superior localised tax compliance networks and native access to fragmented real-time account-to-account rails (like Singapore’s PayNow) in exchange for less reach outside their primary region
The right fit depends on your product mix and market footprint more than on brand recognition. A provider that's excellent for SaaS in Europe isn't necessarily the strongest choice for physical goods across Indonesia and Malaysia.
The payment framework: MoR vs. payment processor vs. gateway vs. payment facilitator vs. seller of record
These four terms get used almost interchangeably in vendor marketing, which causes real confusion at the evaluation stage. Here's how they actually differ:
[Table:1]
Merchant of Record vs. payment processor & gateway
A payment gateway is infrastructure. It moves transaction data between checkout and processor, nothing more. A payment processor handles the transaction relationship but doesn't take on your tax or fraud liability. Neither changes who's legally responsible for the sale. An MoR does.
Merchant of Record vs. Payment Facilitator (PayFac)
This is the comparison that trips up the most CFOs, because both models let you accept payments without becoming a fully registered merchant yourself. The difference is in how much liability actually transfers.
A PayFac lets you operate as a sub-merchant under its master merchant account. It simplifies onboarding and payment infrastructure, but you typically still carry your own tax registration and compliance obligations in each market. An MoR goes further: it takes over as the legal seller entirely, including the tax and regulatory burden a PayFac leaves with you.
Merchant of Record vs. Seller of Record (SoR)
A seller of record is a narrower legal concept. It's about who's responsible for delivering the product or service to the customer, not who's responsible for tax and compliance on the sale. An MoR usually is the seller of record, but the reverse isn't always true.
What an MoR means for your customer relationship
This is the part of the MoR model that surprises businesses after they've already switched.
Why the MoR's name shows up on your customer's statement
Because the MoR is the legal seller, their business name typically appears on the customer's card or bank statement. A customer who doesn't recognize an unfamiliar descriptor is more likely to dispute the charge as fraud, even when the purchase was legitimate. Most MoR providers let you customize the descriptor to include your brand name alongside theirs.
Checkout control trade-off
You give up some control over the checkout experience itself. MoRs typically manage the payment page to stay compliant across every market and card network they operate in, which means less flexibility for custom checkout UI or highly tailored localisation than you'd get running your own payment stack. For most companies this is a reasonable trade for the compliance coverage.
How Merchant of Record payment processing works step-by-step
- Transaction capture: the customer completes checkout; the MoR appears as the seller on their statement.
- Tax calculation: the MoR determines the applicable VAT/GST based on the customer's jurisdiction and applies it in real time.
- Settlement: funds are collected, tax is set aside for remittance, and processing fees are deducted.
- Payout: the net amount, after tax and fees, is transferred to your account, typically on a batch schedule (weekly or monthly, depending on the provider).
- Remittance: the MoR files and pays the collected tax to the relevant local authority on your behalf.
The reconciliation problem most CFOs don't see coming
MoR payouts typically arrive as a single net figure: gross revenue, minus tax already remitted, minus processing fees, batched across potentially hundreds of individual transactions.
For a company operating a single entity in a single currency, that's manageable. For a multi-entity business collecting revenue across Singapore, Indonesia, and Malaysia in three different currencies, matching that one net payout back to individual invoices, customers, and entities becomes a real line-item reconciliation problem.
Do you need an MoR
Whether an MoR makes sense depends less on your industry and more on your entity structure and transaction footprint.
- Multi-entity, cross-border, moderate transaction volume. If you're registering for tax in three or more jurisdictions and your finance team is spending real time tracking rate changes and filing deadlines, an MoR starts to pay for itself in time saved and compliance risk avoided.
- High-SKU, high-volume global ecommerce. At this scale, the tax and chargeback exposure of managing everything in-house typically outweighs the margin you give up to an MoR. Most companies at this stage are already using one or actively evaluating providers.
Where your financial operations take over
An MoR solves your global top-of-funnel tax and compliance liability. It does not solve what happens to that money once it lands in your accounts.
Across multiple entities and currencies, on a schedule that doesn't always match your reporting periods, you still need to reconcile it against actual revenue, allocate it across the right cost centers, and keep visibility on how that cash moves through the business. That's more of a multi-currency operational treasury and spend management problem.
This is where Aspire fits, not as a competitor to your MoR, but as the layer that takes over once its job is done.
For teams already dealing with the reconciliation friction described above, Aspire gives multi-entity finance teams a single place to track incoming payouts against budgets, manage spend across entities, and keep books reconciled without manually piecing together net settlement batches every month.
Managing what an MoR hands off shouldn't become its own full-time job. Whether the payout lands in Singapore dollars, rupiah, or ringgit, your finance team needs one place to see where it went, reconcile it against budget, and move on to the next quarter's decisions.
FAQs
Is Stripe a Merchant of Record?
Stripe's core product operates as a payment processor and gateway, not a Merchant of Record, meaning tax and compliance liability generally stays with the merchant, not Stripe. Some providers offer separate MoR-specific products; always confirm which model applies to your specific account setup.
What is the difference between a Merchant of Record and a payment facilitator?
A payment facilitator (payfac) enables sub-merchants to accept payments under its umbrella merchant account, but liability distribution varies by structure. A Merchant of Record takes on the full tax, fraud, and compliance liability stack, which is a more comprehensive transfer of responsibility than a typical payfac arrangement.
Do I need a Merchant of Record for ecommerce?
It depends on your entity structure and how many jurisdictions you're collecting tax in. If you're selling across multiple APAC markets without local entities in each, an MoR typically reduces both compliance risk and the operational burden on your finance team.
What should I look for in Merchant of Record providers?
At a strategic level: jurisdiction coverage across the specific markets you operate in, payout currency and settlement frequency, and reporting granularity, transaction-level detail, not just net payout summaries. That last point matters most for multi-entity businesses, since it's the difference between a provider that solves your compliance problem and one that just creates a reconciliation problem instead.
What are the risks of using a Merchant of Record?
You give up direct control over the checkout experience and some margin to the MoR's fees. Net, batched payouts can also complicate reconciliation for multi-entity businesses if your finance operations aren't set up to match settlements back to line-item detail.
Is a Merchant of Record the same as a payment gateway?
No. A payment gateway is purely a technical layer that transmits transaction data, it carries no tax or compliance liability. An MoR takes on the full liability for the transaction, which a gateway never does.
How do MoR fees impact profit margins compared to standard PSPs?
MoR fees are typically higher than a standalone payment processor's because the fee bundles in tax handling, compliance, and fraud liability rather than just transaction processing. Whether that trade-off protects or erodes margin depends on how much you'd otherwise spend on in-house tax compliance and dispute management.
Who legally owns customer data when using an MoR?
This depends on the specific contract and the data protection regime in play such as Singapore's PDPA for customers there, and varies by provider. It's worth confirming data ownership and access terms explicitly before signing, rather than assuming standard terms apply.
Can I use an MoR alongside my existing ERP, like NetSuite or Xero?
Most established MoR providers offer some level of integration or exportable reporting for accounting systems, but the depth varies significantly. Some sync cleanly, others require manual reconciliation of batch payouts. This is worth testing before committing, especially if multi-entity consolidation is part of your workflow.
.webp)