Understanding how merchant of record works is essential for any digital product seller evaluating platforms. The term gets used loosely but behind the label is a specific legal and technical architecture that determines who carries tax liability, who issues invoices, who manages disputes, and who actually gets paid. Get the model right and you can sell globally without a tax advisor. Get it wrong and the compliance burden lands entirely on you.
This article breaks down the 7 core technical layers of a Merchant of Record system what each layer does, why it matters for sellers, and how Vandly implements it in practice.
What a Merchant of Record Actually Is
A Merchant of Record (MoR) is the legal entity that assumes responsibility for a transaction between a seller and a buyer. In practical terms, when you sell through an MoR platform, the MoR is the seller’s record on the buyer’s receipt, the tax authority’s records, and the payment network’s ledger.
This is a fundamentally different model from a payment processor. Stripe processes your payments but you remain the merchant. Vandly acts as the merchant, so Vandly carries the legal, tax, and compliance obligations that come with that role.
The core distinction: A payment processor moves money. A Merchant of Record assumes legal identity. The difference determines who owes VAT, who issues compliant invoices, and who answers to tax authorities.
Understanding how merchant of record works means understanding each of the 7 layers that make that legal identity real and functional.
How Merchant of Record Works: The 7 Core Technical Layers
Here’s the full architecture at a glance before we walk through each layer in detail:
| # | Layer | What It Does | How Vandly Handles It |
| 1 | Legal Entity Layer | MoR becomes the legal seller on every transaction | Vandly, powered by Remotify OÜ, is the seller of record |
| 2 | Tax Calculation Layer | Calculates correct indirect tax at checkout by location | Real-time VAT/GST calculation per customer jurisdiction |
| 3 | Tax Collection Layer | Collects tax from the buyer as part of the transaction | Included in Stripe-powered checkout, buyer pays tax-inclusive price |
| 4 | Invoice Generation Layer | Issues legally compliant invoices to every buyer | Auto-generated per transaction, correct for each jurisdiction |
| 5 | Tax Remittance Layer | Remits collected tax to the relevant authority | Vandly remits, not the seller |
| 6 | Payout Infrastructure Layer | Routes net proceeds to the seller | 60+ countries via SEPA, SWIFT, and local rails |
| 7 | Dispute and Chargeback Layer | Manages buyer disputes as the legal seller | Vandly handles buyer-facing disputes; seller retains financial liability |
Layer 1: The Legal Entity Layer
The foundational layer of how merchant of record works is the legal entity substitution. Under the MoR model, the platform registers itself as the seller on every transaction, not the creator who made the product.
Vandly operates through Remotify OÜ, an Estonian-registered company operating under EU law. When a customer buys your product through Vandly, the legal contract of sale is between Remotify OÜ and the buyer. Your role in the transaction is as a supplier to Remotify, governed by the Remotify Merchant of Record Supplier Agreement.
This substitution is what makes everything else in the MoR architecture possible. It’s the legal foundation that allows Vandly to assume tax obligations, issue invoices under its own name, and represent itself to payment networks as the merchant.
What this means for sellers: You don’t need a registered business entity in the countries you sell to. Vandly’s legal presence covers the transaction.
Layer 2: The Tax Calculation Layer
The second layer of how merchant of record works is real-time tax calculation. Indirect taxes (VAT, GST, sales tax) are destination-based for digital products. The rate applied depends on where the buyer is located, not where the seller is based.
This creates a calculation problem at scale. The EU alone has 27 member states with VAT rates ranging from 17% (Luxembourg) to 27% (Hungary). Add the UK (20%), Australia (10% GST), New Zealand (15% GST), and US state sales tax (0–10.25% depending on state and product type), and the number of possible tax rate combinations runs into the hundreds.
The MoR platform’s tax calculation layer resolves this at checkout in real time: identifying the buyer’s jurisdiction from their billing address or IP, looking up the applicable rate, and applying it to the transaction before the buyer pays. According to the EU VAT rules for digital services, this calculation must be accurate at the point of sale.
What this means for sellers: You set your price. Vandly calculates and adds the correct tax automatically. The buyer sees a tax-inclusive total. You never touch a rate table.
Layer 3: The Tax Collection Layer
Calculating the correct tax is one thing, collecting it from the buyer is another. The tax collection layer is the mechanism that ensures the calculated tax amount is actually captured in the transaction, not absorbed by the seller’s margin.
In Vandly’s implementation, tax collection is built into the Stripe-powered checkout flow. The buyer pays a tax-inclusive price, the subtotal plus the calculated tax, in a single payment. The tax portion is held separately from the seller’s net payout and later remitted to the relevant authority by Vandly. Buyers in the EU also see a “VAT handled automatically” trust signal at checkout, which improves conversion for VAT-conscious European buyers.
What this means for sellers: Tax is collected on your behalf with every transaction. Your net payout is already tax-adjusted, you receive only your earned portion.
Layer 4: The Invoice Generation Layer
A legally compliant invoice is not optional for B2B digital sales or EU consumer transactions. It’s a legal requirement. The invoice generation layer of how merchant of record works is what produces that document automatically for every transaction.
EU VAT invoices must include the supplier’s name and address, the supplier’s VAT number, the customer’s details (for B2B transactions), the supply date, a description of the goods or services, the net amount, the VAT rate applied, the VAT amount, and the total amount. Producing this document manually for every sale across multiple jurisdictions is not scalable for an independent creator.
Vandly generates a compliant invoice automatically for every transaction, populated with Remotify OÜ’s legal details, the correct VAT rate for the buyer’s country, and all required line items. The buyer receives it immediately after purchase. No action required from the seller.
What this means for sellers: If an EU customer asks for a VAT invoice, Vandly has already issued one. You don’t need to produce it, format it, or track it.
Layer 5: The Tax Remittance Layer
Collecting tax is not the final step, it must be remitted to the relevant tax authority on the correct schedule. The tax remittance layer is what closes the compliance loop and is the layer most sellers never see but benefit from most directly.
For EU sales, Vandly files under the EU VAT One Stop Shop (OSS) scheme, which allows a single quarterly filing to cover VAT obligations across all EU member states. For non-EU jurisdictions, Vandly manages remittance on a jurisdiction-by-jurisdiction basis.
This is one of the most technically demanding layers of how merchant of record works and the one that would require the most specialist knowledge to replicate independently. OSS filings require accurate sales data by member state, correct VAT rates applied, and timely submissions. Late or inaccurate remittance triggers penalties from EU tax authorities.
What this means for sellers: Vandly files and remits on your behalf. Your compliance exposure on international digital sales is zero, it transferred when you accepted the Supplier Agreement.
Layer 6: The Payout Infrastructure Layer
The payout infrastructure layer is where the MoR model intersects most directly with the seller’s experience. After tax is collected and the platform commission is deducted, the remaining net payout must reach the seller wherever they are in the world.
This layer is technically distinct from payment processing. Stripe processes the buyer’s payment. The payout infrastructure processes the seller’s receipt, which is a separate transfer from Vandly to the seller’s bank account, denominated in the seller’s currency, routed through the appropriate payment rail.
Vandly’s payout network covers 60+ countries: 41 SEPA countries (Eurozone, UK, Switzerland, Norway, and more) plus 27 local-currency markets including India, Pakistan, Nigeria, UAE, Indonesia, Philippines, Turkey, Japan, and others. Supported rails include SEPA bank transfer, SWIFT international wire, and local bank codes (Routing Number, Sort Code, BSB, IFSC). The net payout formula is fixed:
What this means for sellers: You specify your bank account once. Vandly routes your earnings to it after every completed sale in your local currency, via the appropriate rail for your country.
Layer 7: The Dispute and Chargeback Layer
The final layer of how merchant of record works is dispute management. Because the MoR is the legal seller on every transaction, it is also the entity that payment networks hold responsible for chargebacks and buyer disputes, not the underlying creator.
When a buyer files a chargeback with their card issuer, the dispute is raised against the MoR (Vandly) not against the individual seller. Vandly manages the dispute process, provides evidence to the card network, and handles the resolution. This removes the creator from a process that would otherwise require direct engagement with Stripe, Visa, or Mastercard’s dispute systems.
There is an important nuance here: while Vandly manages the process, sellers retain financial liability for chargebacks under the Supplier Agreement. If a chargeback is lost, the cost is deducted from the seller’s account. Vandly also holds a rolling reserve (up to 10% of daily sales for up to 90 days) as a chargeback buffer, standard practice across all MoR platforms.
What this means for sellers: You don’t deal with card networks or dispute portals directly. Vandly handles it. But chargebacks still cost you financially if lost, the MoR model removes process burden, not financial exposure.
Merchant of Record vs Payment Processor: The Key Differences
Now that you understand how merchant of record works across all 7 layers, here’s how it compares directly to using a standard payment processor:
| Function | Payment Processor (e.g. Stripe) | Merchant of Record (e.g. Vandly) |
| Legal seller | You | MoR platform |
| Tax calculation | You (or Stripe Tax add-on) | ✓ Automatic |
| Tax collection | You | ✓ Included in checkout |
| Invoice generation | You | ✓ Auto-generated |
| Tax remittance | You | ✓ Handled by MoR |
| Payout to seller | ✓ Yes (supported countries) | ✓ Yes (60+ countries) |
| Dispute management | You engage Stripe directly | ✓ MoR handles process |
| Business registration req. | Often required | Not required with Vandly |
Why Understanding How Merchant of Record Works Matters
The 7 layers above are not abstract concepts.Tthey map directly to decisions you make when choosing a platform to sell digital products. Each layer represents a compliance obligation that either lands on you or transfers to the MoR. Get the legal entity layer wrong and you’re the seller in jurisdictions you’ve never registered in. Get the tax remittance layer wrong and you’re filing quarterly VAT returns across multiple countries.
Understanding how merchant of record works is what lets you evaluate whether a platform’s MoR claim is genuine or whether it’s a payment processor with a misleading label. A true MoR assumes all 7 layers. A partial implementation leaves gaps that become your problem.
Vandly implements all 7 layers, governed by Estonian law, powered by Remotify OÜ, paying out to 60+ countries. See how it works for your products →
