Merchant of Record for Gaming: What It Actually Means

Imagine buying coffee in a foreign country, struggling with unfamiliar payment prompts, and realizing global taxes are a bureaucratic nightmare. Now multiply that experience by thousands of players across dozens of borders. Monetizing games globally breaks simple commerce rules - a Merchant of Record (MoR) exists to handle that complexity.

What a Merchant of Record actually is

A Merchant of Record ('MoR' for short) is the entity legally responsible for selling to the end customer. The MoR appears on the receipt and assumes responsibility for payments, tax collection and remittance, regulatory compliance, refunds, and disputes.

In practical terms, the MoR becomes the legal seller and runs the commerce layer - so your studio doesn't have to become a tax and payments expert in every jurisdiction.

Why MoR matters in gaming

Gaming combines microtransactions, subscriptions, cross-border buyers, and instant digital delivery. That mix creates operational strain at scale:

• VAT/GST obligations across multiple countries
• Local payment method expectations
• Fraud risk and chargebacks
• Recurring billing complexity

The EU’s VAT One Stop Shop (OSS/IOSS) framework exists specifically because cross-border VAT compliance is complex at scale - a complexity most studios are not built to manage internally. Left unmanaged, this becomes a full-time compliance and finance operation - not just a checkout page.

What an MoR typically handles

For game businesses, an MoR generally covers:

• Global payments: Supporting the payment methods players trust in their local markets.
• Tax calculation, filing, and remittance: Handling cross-border VAT/GSTglobally.
• Compliance and receipts: Clear legal seller designation and audit trails.
• Fraud and chargebacks: Dispute management and reduced operational burden. (Mastercard projects 324 million disputes annually by 2028 - underscoring how operationally heavy dispute management can become at scale.)
• Settlement and payouts: Recurring and on time transfers without building a full internal finance ops team. (With payout times impacting cash flow liquidity.)

How Tebex approaches MoR for games

Tebex acts as the Merchant of Record for game sales, in-game purchases, and UGC monetization, handling the commerce infrastructure so studios can focus on gameplay and growth. In practice, that includes:

• Checkout options built for games: Hosted storefronts, embedded checkout (Tebex.js), and headless APIs for in-game or custom flows.
• Global payment coverage: 130+ local payment methods.
• Chargeback and fraud protection: Seller insurance including chargeback and fraud protections.
• Payout cadence: 7-day average settlement, with instant withdrawals available.
• Scale: More than $1.5B processed to date.

Two quick micro-scenarios (what MoR looks like in real life)

Example 1: Buyer + server operator

A player in Germany buys a cosmetic rank on a community game server using a local payment method. Tebex, as the MoR, processes the payment, issues the receipt, calculates and collects applicable tax, and manages any future dispute. The server operator receives their payout settlement, and the buyer gets the item delivery via the server’s store integration.

Example 2: Buyer + game studio

A player purchases a monthly subscription for premium perks on a studio’s webstore. Tebex, as the MoR, handles the recurring billing flow, including retries if a payment fails, provides the buyer’s checkout experience, and manages refunds or chargebacks if they occur, while the studio focuses on delivering the subscription benefits in-game.

---

MoR Feature Checklist: Tebex vs. “Build It Yourself”

Feature	Tebex (MoR)	Typical Alternative: Self-managed PSP + Tax Vendor
MoR legal seller of record	Yes	No, you are usually the seller
Global payment methods	130+ local methods	Depends on your PSP(s) and integrations
Chargeback insurance	Seller insurance on eligible disputes	Typically you manage disputes and liability
Payout cadence	~7-day average, instant available (depending on payment method)	Depends on PSP and banking rails
Game-native integrations	Official plugins, Tebex.js, headless API	Usually custom engineering work
Hosted store + mobile	Hosted webstores, mobile-native design	Often separate vendors/tools
Developer API support	Yes, APIs/SDKs	Varies by PSP/tax stack
Tax filing & remittance	Handled by MoR	You/tax vendor handle registrations

Is an MoR right for your studio?

An MoR model is often a strong fit if:

• You sell (or plan to sell) cross-border.
• Tax and payment operations are consuming internal bandwidth.
• You want broader payment coverage without managing multiple PSP contracts.
• You need monetization across web, in-game, and mobile environments.

The tradeoff: You exchange some margin and control for speed, regulatory coverage, and reduced operational risk.

Bottom line: If your studio wants to scale globally without building its own tax and compliance stack, a Merchant of Record model - such as Tebex - centralizes the complexity so you can focus on your game.

Common Questions

Who’s liable for chargebacks?

Under an MoR model, the MoR manages disputes and chargebacks. Always review contract terms and coverage limits.

Do we still need tax registrations?

The MoR typically handles B2C tax filing and remittance within scope. Studios should confirm residual obligations with their advisors.

What about PCI scope?

Using a hosted MoR checkout reduces how much card data your systems handle, shrinking your PCI DSS (Payment Card Industry Data Security Standard) exposure.

Will integration slow us down?

Hosted storefronts launch quickly. Embedded and headless integrations require more engineering but allow deeper UX control.