> ## Documentation Index
> Fetch the complete documentation index at: https://docs.macropay.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Why a Merchant of Record Beats Stripe for SaaS Companies
> Stripe processes the payment but leaves you the tax bill. See why a Merchant of Record like Macropay ships global, compliant billing for one flat fee.
## The line item nobody quotes you
A payment processor charges you to move money. A **Merchant of Record (MoR)** does that *and* becomes the legal seller of your product — which means the global tax, compliance, and chargeback burden lands on us, not on you.
That single distinction is the whole story. Stripe is a great processor, and for plenty of teams it's the right call. But the moment you sell digital goods across borders, "processing payments" and "running a compliant billing operation" stop being the same job. This page is about the gap between the two — and who pays for it.
## What a Merchant of Record actually takes off your plate
When Macropay is your MoR, your customer is buying from *us*. Macropay is the name on their card statement, the entity on the invoice, and the party a tax authority talks to. Concretely, we:
* **Are the seller of record** — we carry the tax liability so you don't.
* **Register, collect, and remit** sales tax, VAT, and GST in every jurisdiction your customers buy from.
* **Issue compliant invoices** with the right tax treatment per country, automatically.
* **Own the chargeback relationship** with the card networks, and work to keep dispute rates low.
* **Absorb PCI scope** — cards are tokenized in our PCI DSS Level 1 compliant vault, so they never touch your servers.
You ship product. We handle the part of selling it that has a legal department.
## Where Stripe quietly hands you the tax bill
Stripe is a processor, not a seller of record. Sell globally on it and the obligations below become *yours*:
| Jurisdiction | What you owe |
| -------------------------- | --------------------------------------------------------------- |
| EU | VAT across 27 member states, each with its own rate and rules |
| UK | Separate post-Brexit VAT registration |
| US | Sales tax in 45+ states, every one with its own nexus threshold |
| Canada / Australia / India | GST / HST |
| Everywhere else | A growing list of digital services taxes |
Tooling can *calculate* the right amount to charge. Calculation is step one of four. You still have to **register**, **file**, and **remit** in every place you owe — and keep doing it as thresholds and rates change underneath you.
A MoR collapses register → file → remit into a fee you already pay. There is nothing to integrate, no new jurisdiction to onboard, and no quarterly filing to miss.
## Run the real numbers
The sticker fee is the cheap part. Here's the honest cost of "we'll handle tax ourselves" versus a MoR, on a hypothetical SaaS doing meaningful cross-border volume.
### DIY on a processor
| Cost | Annual amount |
| ---------------------------------------- | ------------------------------ |
| Processing (\~2.9% + 30¢) | Variable |
| Tax calculation add-on (\~0.5%/txn) | Variable |
| Filing service, per jurisdiction | $1,200 – $3,000 each |
| Accounting firm for compliance | $5,000 – $15,000 |
| Engineering to build the tax integration | 2–4 weeks up front |
| Ongoing tax-rule maintenance | 1–2 days/month |
| **Effective rate on \$100** | **\~5–7% + heavy fixed costs** |
### Macropay (Merchant of Record)
| Cost | Annual amount |
| ------------------------------------ | ---------------------- |
| Processing (4.5% + 50¢) | Variable |
| Tax calculation, filing & remittance | Included |
| Registration management | Included |
| Engineering | 1–2 hours |
| Ongoing maintenance | None |
| **Effective rate on \$100** | **4.5% + 50¢, all-in** |
The headline gap between 2.9% + 30¢ and 4.5% + 50¢ evaporates once the fixed compliance stack is on the table. Past a handful of jurisdictions, the MoR is frequently the *cheaper* line — and it's always the simpler one.
Selling internationally adds **+1.5%** on non-US cards and subscriptions add **+0.5%**, both already inside the all-in rate — no separate tax SKU, no surprise invoice.
## Chargebacks: who's actually on the hook
On a processor, *you* are the merchant. When a customer disputes a charge:
* You eat the dispute fee whether you win or lose.
* You assemble evidence and respond inside tight deadlines.
* Cross a dispute-rate threshold (\~0.7%) and you land in a card-network monitoring program with penalties.
* Sustained problems can get your account frozen or closed.
With Macropay as MoR, the dispute is **ours** to manage. We respond on your behalf, work proactively to keep rates under network thresholds — including preemptive refunds when that's the cheaper outcome — and stand between your business and direct network penalties. Our dispute fee is a flat **\$30**, win or lose, with nothing else hidden behind it.
## The AI-billing edge
Most "Stripe vs. MoR" comparisons stop at tax. If you're building AI products, there's a second axis that matters just as much: **how you bill for consumption, and how an agent gets paid for the work it does.**
Macropay is built for usage- and outcome-based pricing, not bolted onto it:
* **Meter by usage, activity, or outcome.** Ingest **events**, roll them into **meters**, attach a metered price, and settle against prepaid **credits**.
* **OpenAI-compatible AI proxy** at `/ai/v1` — swap your base URL and token cost is captured per request, automatically.
* **Agents are first-class.** Stream activity and outcome **signals** to attribute work to a specific agent, mint **value receipts** that certify ROI (time saved, revenue generated, cost avoided), and watch **agentic margin** — billed revenue against AI cost (COGS) — per agent.
Bill an AI feature in a few lines:
```bash theme={null}
# Send the AI proxy request — token cost is captured automatically
curl https://api.macropay.ai/ai/v1/chat/completions \
-H "Authorization: Bearer $MACROPAY_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "gpt-4o-mini",
"messages": [{"role": "user", "content": "Draft a release note for v2.3"}]
}'
```
```bash theme={null}
# Attribute an outcome to an agent — rolls up into a value receipt
curl https://api.macropay.ai/v1/signals \
-H "Authorization: Bearer $MACROPAY_ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"signals": [{
"kind": "outcome",
"event_name": "ticket_resolved",
"agent_id": "agent_support_triage",
"external_customer_id": "cus_8421",
"external_id": "ticket_8Qp2",
"data": { "tickets": 1 }
}]
}'
```
No processor gives you this. It's the difference between billing for an API call and billing for the result an agent delivered.
## So, who should pick which
A MoR isn't the answer for every business. Be honest about your case.
You need total control over the payment flow, sell B2B inside one simple-tax country, already run a multi-jurisdiction finance team, need custom money movement (marketplace splits, complex payouts), or process volume so high that per-transaction rate beats compliance cost.
You're a small-to-mid SaaS selling across borders, have no tax team and don't want one, want to launch globally on day one, are building AI products that need usage or outcome metering, or simply want to ship product instead of tax infrastructure.
## Bottom line
A processor hands you a payment API. A Merchant of Record hands you a billing *business* — tax, compliance, disputes, and AI metering already wired in. The base-rate difference is real, and it stops mattering the moment you price in what it actually costs to sell globally and stay compliant.
Open an account and accept payments in minutes — zero tax registration on your side.
All-in pricing, nothing hidden: 4.5% + 50¢ per transaction.