A founder built a Chrome Extension. It took off. Five thousand users signed up, a few hundred started paying, and Stripe notifications were piling up like good news. Then Stripe Tax flagged a VAT form.
He filled it out. At the end of it: a $10,000 penalty for failing to register for VAT in a jurisdiction where his sales had crossed the threshold.
No refund would undo it. No appeal would make it go away. It was just gone.
This story circulated on Indie Hackers and Hacker News in early 2024, and it surfaced one question that every founder should answer before their first international sale: is Stripe a Merchant of Record?
The answer is no. And that distinction will cost you if you don't understand it.
What Merchant of Record Actually Means
The Merchant of Record (MoR) is the legal entity that sells to your customer. Not the entity that built the product. Not the entity that runs the website. The entity that, in the eyes of the tax authority, made the sale.
This matters because whoever is the MoR is legally responsible for collecting the correct tax rate (VAT, GST, sales tax) in the customer's jurisdiction, registering for tax in every country or state where thresholds have been crossed, filing tax returns and remitting collected taxes to the right authorities, and managing refunds, chargebacks, and compliance records.
When you are your own MoR, that list belongs to you. Every country you sell into becomes a potential obligation. In the EU alone, there are 27 different VAT regimes. The US has over 11,000 distinct sales tax jurisdictions.
No, that is not a typo.
What Stripe Actually Is
Stripe is a payment processor. A very good one. It moves money from your customer's card to your bank account, handles authentication, manages fraud signals, and provides excellent developer tooling.
But Stripe is not the entity that made the sale. You are. The customer's invoice says your company name. The tax authority's records show your company as the seller. The compliance obligation lands on your desk.
Stripe confirmed this themselves in a 2021 Indie Hackers AMA: "We don't yet offer a merchant of record service."
That quote is from their own team. It has not changed.
What About Stripe Tax?
Stripe Tax is a product that calculates the correct tax rate at checkout and collects it from the customer. It is genuinely useful. But useful is not the same as sufficient.
Stripe Tax does not register you for VAT in the jurisdictions where you cross registration thresholds. It does not file your VAT returns on your behalf. It does not remit collected taxes to tax authorities. It does not accept legal liability if something goes wrong.
All of that still falls on you. Stripe Tax tells you what the rate should be and collects the amount. Getting it to the government, on time, in the right format, in each jurisdiction, is your problem.
This is the gap that trapped the Chrome Extension founder. Stripe Tax may have been calculating VAT on his sales. But nobody filed the registration paperwork in the jurisdiction where he crossed the threshold. When the tax authority looked, they found unregistered sales going back months. The penalty was $10,000.
Collection is not compliance. Remittance is not compliance. Registration, filing, and remittance together make compliance.
The Compliance Cliff Most Indie Hackers Hit
Here is what the path usually looks like:
You launch. You start getting customers from the US, the UK, Germany, Australia. You are thrilled. You are using Stripe because everyone uses Stripe. Stripe Tax is collecting VAT on EU sales because you turned it on after reading a tweet.
Then, somewhere around $30,000 to $50,000 in annual revenue, you cross a VAT registration threshold in the UK. Or the EU's One-Stop Shop threshold. Or a US state's economic nexus threshold.
Most founders do not notice when this happens. There is no alert. Stripe does not tell you "you are now legally required to register for VAT in Germany." You are expected to monitor this yourself, understand the thresholds in every market, and take action.
For a solo founder doing six things at once, this simply does not happen. The first signal is usually a letter from a tax authority. By then, the back taxes and penalties have had months to compound.
This is not a hypothetical. The $10,000 fine from the IH story came from exactly this sequence.
What a Merchant of Record Does Instead
When you sell through a Merchant of Record, the MoR is the legal seller. The customer's invoice is issued by the MoR. The MoR collects the tax, holds the registration in each jurisdiction, files the returns, and remits the money to the authorities.
You receive a payout. Net of fees. Clean. No compliance obligations in 47 countries.
The MoR accepts legal liability for tax compliance. If something goes wrong with VAT in France, that is the MoR's problem, not yours.
This is what founders mean when they say they "just want to focus on building." An MoR is the structure that makes that possible across borders.
What CREEM Does
CREEM is a Merchant of Record built for indie hackers, AI builders, and lean software teams.
When you sell through CREEM:
- CREEM is the seller of record on every transaction
- VAT and GST are collected at the correct rate for each customer's location, automatically
- CREEM holds all the tax registrations across jurisdictions
- CREEM files and remits all taxes on your behalf
- Chargebacks, refunds, and disputes go through CREEM
You get a dashboard with your revenue. You get payouts. You get global sales without a compliance operation.
CREEM is specifically designed for the solo founder or small team who wants to sell internationally without hiring a tax attorney in every country they grow into.
When Does This Actually Matter?
If you have zero international customers and you sell only in the US, with sales under your state's economic nexus threshold, you may be fine with Stripe for now. Stripe is a legitimate choice for domestic-focused businesses that understand and can manage their own tax obligations.
The moment you go international, the math changes fast. EU customers trigger VAT obligations. UK customers trigger UK VAT. Australian customers trigger GST. Each jurisdiction has its own threshold, its own filing calendar, its own form format.
Going global with Stripe means going global with all of that homework. Most indie hackers underestimate this until they get a letter they did not want.
The Decision Is Simpler Than It Looks
You have two options:
Option 1: Use Stripe, implement Stripe Tax, hire a tax advisor or accountant in each major market you sell into, monitor thresholds across jurisdictions, file returns on schedule, and stay on top of changing regulations. This is viable. It is also a part-time job you probably did not sign up for.
Option 2: Use a Merchant of Record. Pay a slightly higher fee per transaction. In exchange, hand all of that liability off entirely and focus on your product.
For most indie hackers and small software teams selling globally, option 2 is the obvious move. The fee difference is almost always smaller than the cost of one missed VAT filing.
The Chrome Extension founder who got the $10,000 fine was not incompetent. He was building, not doing tax research. An MoR would have cost him a fraction of that fine in additional fees across the entire year.
The Short Version
Stripe is not a Merchant of Record. Stripe Tax calculates and collects taxes but does not handle registration, filing, or remittance. The legal obligation for global tax compliance stays with you when you use Stripe.
A Merchant of Record like CREEM takes on that obligation entirely. You sell globally. CREEM handles the compliance. You keep building.
If you are selling software internationally and you have not thought about this yet, now is the time.
Selling globally without the compliance headache? CREEM handles VAT, GST, and sales tax in 150+ countries so you don't have to. Get started free at creem.io
