Why SaaS Founders Need a Backup Merchant of Record
Anyway Team
· 9 min read ·

A merchant of record is not only a checkout. For many SaaS products it is also the system that recognizes the customer, invoices the sale, collects the card, and, on covered transactions, stands as the legal seller. That concentration is convenient until the provider is slow, under review, or no longer the place you want the next renewal to run. A backup is a second approved path, not a second “best MoR” list.
A backup is real only if it is approved, the catalog can be recreated there, and you have rehearsed a cutover. A signup link in a bookmark is not a backup. Keep entitlements in a database you control. Webhooks should update that store; they should not be the store. You may defer a second MoR when revenue is still exploratory. You should not defer it because a provider has been uneventful, or because an official transition post has no deadline.
This is not a migration playbook, and it is not a ranking of alternatives. Lemon Squeezy’s official 28 January 2026 update describes a quieter period, a goal of an easy migration toward Stripe Managed Payments, and no shutdown date. A transition with no deadline is still a reminder that your billing provider can change shape while customers keep expecting access. Facts about Anyway below were checked on official pages on 12 November 2026.
What concentration risk actually is
The risk is operational, not theatrical. A single merchant of record typically holds some combination of:
the live checkout and saved payment methods;
the subscription schedule and renewal attempts;
customer records tied to those subscriptions;
invoices, tax treatment on covered sales, refunds, and dispute correspondence;
the balance you will later withdraw.
If that account is delayed, restricted, or simply no longer a fit, the failure is not only “we cannot charge a new card today.” It can also be that you cannot prove who is paid through when, or that a renewal has nowhere eligible to go. Providers also review accounts, limit products, and can issue refunds under their own rules. None of that is unique to one brand, and this article does not claim that any named merchant of record, including Anyway, is unable to review or restrict an account.
The Lemon update is one public illustration, not a prediction. The company stated a migration goal and did not publish a finished official one-click importer in that post, nor a forced end date. Founders who treated “we will move later” as a plan discovered that later still requires a destination that will accept them, a catalog that already exists there, and records that do not live only inside the outgoing platform. The same reminder applies when a provider’s public pricing changes, as in Polar’s 2026 fee change: a rate change is not automatically a reason to leave, but it is a reasonable moment to approve a second path.
Data you should keep outside the processor
A backup merchant of record is useless if the only current copy of “who bought what” is inside the primary provider. Keep a system of record you control, and treat the MoR as the charging and invoicing layer that you can point at that system.
At minimum, store in your own database or a durable export you can rebuild from:
a stable customer identifier and a contact email you are allowed to use;
the product or plan the customer is entitled to, including quantity and any add-ons;
the current period start and end, and whether the subscription should renew;
the last successful payment, the last failed payment, and the provider’s order or subscription IDs as references, not as the only key;
refund, dispute, and cancellation events, with dates;
a mapping from your plan IDs to the product IDs on each provider you might use.
Webhooks should update that store; they should not be the store. The event design is covered in SaaS payment webhooks. Exports should be scheduled, not pulled for the first time during an incident. Entitlements — whether the customer may sign in and use the product — should be granted and revoked from your database, not inferred at runtime from a provider dashboard.
You will still need the primary MoR for payment-method updates, tax invoices on sales it processed, and historical payout statements. Keep invoice and receipt exports, and know how refunds and chargebacks were handled on the original seller. The goal is not to duplicate a billing platform. It is to make sure a second platform can start new checkouts and, if you later move renewals, can be told who is owed access without a forensic recovery. Failed-payment recovery should also be rebuilt on the backup, not left only on the primary.
A two-provider cutover plan
A backup is real only if it is approved and rehearsed before you need it.
Choose and verify the second provider while the first one still works. Verification, prohibited-product review, and payout-account setup all take time. “We have a signup link in a bookmark” is not a backup. The second provider can be another dedicated merchant of record, or, if you are eligible, Stripe Managed Payments inside an account you already hold. Anyway can sit in either seat: primary checkout today, or a second approved merchant account you do not have to stand up under pressure.
Keep the catalog current on both sides, or have a script that can recreate it. Products, prices, trial rules, and tax-relevant descriptions should not exist in only one dashboard. A quarterly check that the backup catalog still matches the live plans is enough for most small teams; skip it and the backup is a second empty shop.
Decide in advance what “cutover” means. The usual split is: new customers and new upgrades go to the backup immediately; existing subscriptions stay on the primary until each renewal is migrated, cancelled and recreated with consent, or left to run out. Charging twice and dropping prepaid access are the two failures to design against. The detailed mechanics of a Lemon-style move belong in How to migrate off Lemon Squeezy; the backup plan only needs the decision rules, the owner, and a dry run.
Run a drill. Create a test product on the backup, take a sandbox or low-value payment, grant entitlement from your own database, issue a refund, and request a payout to a supported account if the provider allows it in that environment. Confirm that your webhook handler accepts the second provider’s events without overwriting the primary’s IDs. A drill that you have never run is a document, not a plan.
Write the customer message before you need it. If checkout has to move, you will need a short explanation, a new payment link, and a way for the customer to confirm the plan they already have. Drafting that on the day the primary path breaks is how invoices go out late and support queues fill up.
When Anyway is a reasonable primary or backup
Anyway is a dedicated merchant of record: on eligible sales it is the buyer’s contractual counterparty and appears on the invoice, as described in what a merchant of record is. Documented tax coverage on 12 November 2026 is VAT on USD-priced digital goods and services sold to consumers in the EU and the UK. The published standard rate is 3.9% + $0.50, with no monthly or setup fee, and a payout fee of 1% with a $10 minimum, on the current fees documentation. Payouts currently go to bank accounts in the United States, the United Kingdom, Hong Kong, or mainland China — and, in mainland China, to a bank or Alipay account in CNY.
Those limits are why Anyway can be a strong backup for some teams and a poor one for others. If your receiving account is not on that destination list, approving Anyway in a hurry will not complete a cutover. If you need documented tax coverage beyond the EU and UK VAT workflow Anyway publishes, you should know that before you name it as the fallback. If you already have an eligible Stripe account, Managed Payments may be the shorter backup path because it stays inside a stack you already operate — subject to the same eligibility review that applies when it is the primary. The processor-versus-MoR split is in Stripe vs Merchant of Record.
Use Anyway as the primary when you want owned checkout and a dedicated MoR today, and keep a second approved option if your volume or risk tolerance says one commercial relationship is too many. Use it as the backup when your primary is already elsewhere and you want a merchant account that can be turned up without first forming a new company. In both cases, complete business verification and a payout test before you need the switch.
When you may not need a second MoR yet
A backup is a cost: a second review, a second integration, and a second set of tax and payout rules to keep straight. You may reasonably defer it when revenue is still exploratory, when a single provider already meets every current constraint, or when you are deliberately winding a product down. You should not defer it because a provider has been uneventful so far, or because an official transition post has no deadline.
You also do not need two merchants of record if the second “backup” is only a receiving account, a company-formation service, or a payout wallet. Those tools do not sell to the customer. Concentration risk lives in the seller-of-record and subscription layer. Pick a second path that can actually charge and invoice, keep entitlements in a database you control, and practice the cutover once. That is the work. The brand on the backup can be Anyway or another eligible provider; the mistake is to have only one, and to discover that fact in production.
Frequently asked questions
Is a second MoR the same as migrating off Lemon Squeezy?
No. A backup is an approved second path you can turn up under pressure. A migration is the inventory, catalog recreation, and subscriber cutover once you have chosen a destination. Use How to migrate off Lemon Squeezy for the cutover, and Best Lemon Squeezy alternatives for the destination choice.
Can Managed Payments be the backup instead of another dedicated MoR?
Yes, if you already hold an eligible Stripe account and the product qualifies. Eligibility is still a review. The processor-versus-MoR context is Stripe vs Merchant of Record.
Does Anyway guarantee it will never review or restrict an account?
No. This article does not claim that any named merchant of record, including Anyway, is unable to review or restrict an account. That is why a backup path you have already approved matters.
What records should I export first?
Customer identity and contact email, plan entitlements, period dates, payment and cancellation events, and a mapping of your plan IDs to each provider’s product IDs. Keep invoice history, and wire webhooks into your own database.
When is Polar’s 2026 fee change a reason to approve a backup?
A rate change is not, by itself, a requirement to leave. It is a reasonable moment to do the approval work, especially if you might later switch some volume. That decision is Polar’s 2026 fee change.