Shopify Payments terminated, and you sell functional mushrooms. Migrate everything to a new Shopify store.
The termination notice is shorter and colder than a deactivation: your Shopify Payments account has been permanently closed. You cannot reapply, cannot appeal, and cannot switch to a different Shopify Payments underwriter because there is only one — Stripe. What makes termination distinct from a deactivation is that you may now be reported to MATCH, the card networks' Terminated Merchant File. This is not automatic, and you will not be told it has happened. MATCH lists the people behind the business as well as the business itself, for five years, and every payment processor screens it when you apply. A deactivated account is a warning. A MATCH listing is a record. Most merchants do not know which has occurred, and that confusion drives the first ruinous mistake: opening a new company and expecting a clean slate. It does not work that way. The move here is not to hide — it is to understand what actually happened, what you can and cannot fix, and which gateways will underwrite your real business model.
Move all of it into a new store, from $247
One-time packages, no per-record metering, no quotes. The order form unlocks the moment you pay, counts are matched against your old store, and the entire migration then runs a second time — the second pass has to create nothing.
What you are looking at
- "Your account has been permanently terminated and may not be reactivated" — with no pathway to appeal or re-apply
- Checkout still functioning for days or weeks, creating the false impression the termination is not real
- A sudden payout freeze with unclear hold periods, sometimes stated vaguely as "under review"
- No statement of whether the termination includes a MATCH report — you are left guessing
- Support responses that repeat the policy without engaging your actual circumstances
Both clocks matter because they move at different speeds and create different pressure. The checkout clock is psychological — it feels like you have time, which is the danger. The payout clock is the real one. Money already collected sits frozen, and every day that passes while you are still using that shop is a day you are not building elsewhere. Act on the assumption that checkout access could end suddenly, not that you have weeks.
Why it happened — specifically for functional mushrooms
Shopify Payments is underwritten by Stripe, and Stripe's restricted-businesses list groups all mushroom products together because the same retailers sell both legal functional mushrooms and controlled substances like psilocybin or amanita muscaria. A reviewer sees "mushroom" in your product titles or claims and cannot tell whether you are selling reishi or psilocybin without drilling in. The secondary trigger is vague marketing language — if your copy says "mind-enhancing" or "consciousness-expanding", the reviewer assumes the worst and declines without a second look.
Rule out the easy fix first — then deal with the real one
Rule this out first, because Shopify does not document a route for functional mushrooms. What happens instead is that merchants apply under the name they have, Stripe's system flags the word, and a human reviewer gets the ticket. That reviewer's job is to confirm you do not sell controlled substances. Most declines come not from policy but from reviewers unable to confirm what you actually sell — your product names are ambiguous, your claims sound psychoactive, or your supplier list is missing. A fresh application with crisp product names and a clear supplier declaration sometimes works. An acquirer outside Stripe's ecosystem will underwrite from scratch, which is slower but more straightforward.
It only helps if all of these are true:
- Your product names must not use "magic", "consciousness" or "psychoactive" language.
- You must have a documented supplier list with full names and addresses.
- Your product pages must clearly state the species and absence of psilocybin or amanita.
- You cannot claim the products treat or cure any medical condition.
- Your store must not cross-sell any controlled substances or plant material.
If any one of them does not hold, you are where everyone else on this page is: you need a store built around a gateway that will actually accept you — and everything you have built has to move into it without losing the catalog, the customers, the order history or the rankings.
What this means for a business like yours
💊 Sold to be swallowed, inhaled or applied — health claims and product-liability risk
When Shopify Payments terminates for a consumable brand, the reason is usually claims language on your product pages, not the product itself. Processors treat marketing copy as regulatory claims: a formula that 'boosts energy' reads differently than one that 'cures fatigue'. They also watch dispute rates closely because consumables naturally attract 'it didn't work' chargebacks. Before approaching a new processor, have your product descriptions and any health or efficacy statements reviewed by someone familiar with FTC and FDA boundaries. A new account with the same pages will fail the same way. The claims review is the load-bearing fix; everything else follows from it.
🔁 Recurring billing is a large share of revenue
Shopify Payments termination is doubly damaging for subscription businesses. New orders halt, but your existing subscribers' recurring charges stop immediately because their stored payment methods are locked to the disabled processor. Those cards cannot be exported or migrated; they live in Shopify Payments' vault. Revenue you believed was predictable decays every day the situation persists, and asking thousands of customers to re-enter payment details recovers only a fraction. The new gateway you choose must support a stored-card migration path or a customer re-authentication flow before you switch. This is not a sales problem—it is a technical and cash-flow problem. Deal with the subscription book first.
⚖️ Legal status is genuinely contested or actively changing
When a jurisdiction's legal status is contested or actively changing, payment processors price legislative risk, not just chargeback risk. Shopify Payments termination for your category usually reflects uncertainty about future regulation, not current illegality. A replacement processor must be willing to accept that legislative risk, which narrows your options significantly. Some acquirers will require you to monitor legislative activity and notify them of material changes; others will not enter the space at all. You cannot fix this by changing your business model slightly—the processor is making a bet on the category's legal future, not on your individual compliance. Approach new processors with realistic expectations about underwriting timelines and reserve requirements.
What you actually have to fix
Underwriters do not change their minds because you asked. They change them because the facts changed. For functional mushrooms, these are the facts that move the decision:
Rewrite product titles and descriptions to name the exact species
This is the single highest-yield fix. "Magic mushroom extract" and "consciousness support" land you in the controlled-substance pile. Use the binomial name or the common name of the species: lion's mane, reishi, cordyceps, chaga. Then say plainly what it is — a dried mushroom or mycelium powder for supplement use. Describe the normal use case: cognitive support, energy, immune function. Remove any language suggesting euphoria, hallucination, alteration or enhanced consciousness. Audit your product pages, email campaigns, blog posts and any paid ads, because reviewers read all of them.
Compile a supplier list with certifications and COAs
An acquirer needs to see where each product comes from and that it is what you say it is. For each SKU or strain you carry, obtain the supplier's name, address and phone number. Ask your suppliers for a certificate of analysis (COA) showing the species, the active compound levels (beta-glucans for reishi, hericenones for lion's mane) and a negative result for psilocybin and controlled alkaloids. If your supplier cannot produce a COA, you cannot sell the product to a high-risk processor. Store these documents and be ready to share them in application or underwriting.
Get supplier attestations that products contain zero psilocybin
Reviewers want to rule out cross-contamination and intentional adulteration. Contact each supplier in writing and ask them to confirm in writing that their mushroom products contain no psilocybin, no amanita alkaloids and no controlled substances. Keep their replies. If a supplier balks or goes silent, source that product elsewhere or stop carrying it. An attestation from the supplier is not a legal guarantee, but it shows you did your homework and were not negligent — and it moves a reviewer from suspicion to confidence.
Audit your entire site for ambiguous or drug-like language
A single stray sentence can cost you. Search your store for words like "trip", "high", "psychedelic", "altered state", "transcendent", "hallucino". Check your blog archive, your email unsubscribe page, your FAQ, any customer reviews you display, and your social-media links. If a reviewer finds it, you lose. Replace it with something specific and honest: "supports focus", "promotes restful sleep", "used in traditional medicine". Be boring. That is the goal.
What underwriting will ask you for
- Supplier list with names, addresses and product certifications or COAs for each strain
- Product ingredient declarations showing exact species (e.g. lion's mane, reishi) and absence of psilocybin
- Marketing materials and product page screenshots demonstrating no drug-like claims
- Business formation documents and government-issued ID for all beneficial owners
- Processing history and chargeback records from any previous merchant account
Getting underwritten for functional mushrooms
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite functional mushrooms. What none of them will tell you up front is the number that actually matters: what your business gets offered, once they have seen your volume, your claims and your history. Rate, reserve and settlement terms vary enormously between applicants in the same category.
Get real quotes from high-risk processors that accept functional mushrooms
Six taps and three details. We put it in front of the high-risk acquirers that actually underwrite your category and come back with what they will offer you — rate, reserve and settlement terms — so you are comparing real numbers instead of cold-emailing brokers for a fortnight.
The recovery playbook
- Establish whether you are on MATCH before you actYou need to know what actually happened, because the next three steps depend on it. A Shopify Payments termination does not automatically trigger a MATCH report — Stripe may terminate an account without reporting it to the card networks. The only way to find out is to check the MATCH database yourself. You can query MATCH through third-party screening services or by applying for a merchant account with a new processor and asking them to run a check. If you are listed, you are listed for five years from the termination date and every acquirer you apply to will see it. If you are not listed, the termination is local to Shopify and Stripe, and your options are much broader. This step takes a few days and it determines everything that follows.
- Get a verified copy of your store while you have access — todayThis is the step with a deadline you do not control. A termination means checkout will eventually close and admin access may follow. Once that happens, there is no API, and without an API your catalog, orders, customer list, consent records and every piece of metadata your theme references are unreachable. Not deleted — just gone from your control. Shopify's own CSV export cannot carry metafields, metaobjects, orders, gift card codes, videos, themes, menus, discounts or redirects, which means a simple download is incomplete. You need a third-party migration tool to pull a true copy, or a developer to script the API before the access ends. If you own gift card codes, know now that they cannot be read through any Shopify API by anyone — you can only re-issue them. Start this today, not after checkout closes.
- Decide whether to appeal or move onIf you are not on MATCH, an appeal is worth exploring, because the termination may reverse and you get your Shopify Payments account back. The appeal goes to Stripe through Shopify support, and Stripe's answer is final. If you are on MATCH, the appeal is not the move — the move is migration, because no other processor will take you while you are listed. Waiting out the five years is passive and it leaves your money frozen. Moving to a new entity is the move people suggest, and it is the move that fails: MATCH follows the people, not the company. A new business with the same beneficial owner does not present as a new applicant to any processor screening MATCH. That is not a legal opinion — it is how the system works. The right reason to form a new entity is structural — a genuine operational separation — never to evade a record.
- If you are not on MATCH, migrate to a gateway that accepts your categoryNot all payment processors screen the same way, and some will underwrite a business that Stripe will not. Gateways that publicly advertise support for higher-risk categories include Wise, Stripe Connect partners in your category, and alternative processors specializing in your industry. Never assume acceptance — apply truthfully, with your full transaction history, and let the underwriter decide. Build your new store on the new processor's infrastructure before you lose access to your Shopify export. You are moving your entire operation: catalog, images, descriptions, SEO metadata, theme, products, variants, metafields, videos, customers, orders, menus, redirects and discounts. A complete migration takes time, and you do not have much of it. This is where we come in: a fixed-price migration service that pulls your store into a new platform, re-runs the full export a second time, and compares counts to catch what moved and what did not. Nothing is ever lost in a migration — but some things are commonly missed, and we are the tool that finds them.
- If you are on MATCH, build your new business on a processor outside the card network screening loopMATCH is screened by every acquirer licensed to take cards. If you are listed, traditional payment processors — including Stripe, Shopify Payments, Square and most banks — will decline you. Your options narrow to two: processors that do not screen MATCH (typically crypto or alternative rails), or waiting out the five-year listing period. If you choose the latter, that five years starts from your termination date, not from today. In the meantime, your money is frozen and your business is paused. If you have been terminated unfairly or as a result of a category misidentification, consider legal counsel — the card networks do take appeals, and some merchants have won reversals. That is contested ground and worth exploring with a lawyer, not a migration service. Our role is to move your store when you have a destination. If you do not have one yet, that is the conversation to have first.
And then there is the part that actually loses businesses
If you do need a new store, the payments problem turns out to be the easy half. This is what is sitting in your current store right now, and what happens to each piece when someone tries to move it by hand:
Why this category in particular
A functional mushroom store's data is dangerous to move by hand because the compliance content lives in metafields. COAs, test results, species confirmations and supplier IDs are often reference-type or file-type metafields that a CSV export cannot carry at all. If they are copied naively they keep pointing at files in the old store, so the product page renders and the lab results are silently blank. On a regulated supplement product, a missing COA is not a cosmetic bug — it is the thing an underwriter asks for first.
| What you own | How much of it | What breaks doing it by hand | What we do instead |
|---|---|---|---|
| Product images | 480images≈ 2 hrsbulk re-upload, ~15 sec each | By handthe CSV carries image URLs and alt text, but they point at your OLD store's CDN — so the moment the old store goes, every image 404s. Re-upload and Shopify appends a dedupe suffix to the filename, which breaks every theme section and product description that referenced the original URL | Automatedevery file re-uploaded through the API with its alt text and variant attachment intact, its content type preserved so image-restricted fields still accept it, and every reference to the old URL rewritten |
| Product descriptions | 120descriptions≈ 2 hrsone pass to repair inline image links — the CSV carries the text | By handdescriptions are full of inline images and links pointing at the old store's CDN. Paste them into the new store and the text survives perfectly while every embedded image quietly dies — which you usually discover from a customer, not from a report | Automatedbodies copied verbatim, then a second pass rewrites every source-CDN URL inside them to the re-uploaded file on the new store |
| Product attributes & variants | 360variants≈ 45 minthe CSV carries these; the time is verifying option order | By handoption ORDER is part of the product's identity. Rebuild "Size, Colour" as "Colour, Size" and every theme swatch, saved customer URL and app that keys on variant position breaks — silently, because the product page still renders | Automatedvariants upserted by SKU with option names and order preserved, so swatches, deep links and app data keep working |
| Metafields & metaobjects | 720metafields≈ 5 hrsonly the reference, JSON and metaobject fields, ~1 min each | By handthe product CSV carries simple text and number metafields — but not metaobjects, and not reference or JSON types, which is exactly where app data and theme content live. Reference fields are the real trap: copy the value and it still points at objects in the OLD store, so the page renders and the custom block is silently empty | Automatedwritten in dependency order after their targets exist, with embedded references re-pointed at the new store's objects — and any value whose reference cannot be resolved is dropped rather than written broken |
| SEO data & redirects | 212records≈ 2 hrsredirects one at a time, plus a handle audit | By handany handle that changes becomes a dead URL with no redirect, and existing 301s are not in the product CSV at all. Years of accumulated ranking and backlinks end up pointing at pages that no longer resolve — the most expensive thing on this page to get wrong, and the slowest to notice | AutomatedSEO titles, meta descriptions and handles carried across, and every existing 301 recreated, so nothing that used to rank starts 404ing |
| Your custom theme | 1theme≈ 6 hrs2–10 hrs depending on how customised it is | By handa theme is not just its files. The settings, section content and block ordering are stored against the store, so a file copy gives you the layout and none of the content. Hardcoded asset URLs and tracking snippets also still point at the old store | Automatedyour live theme pulled and pushed as-is, then scanned for tracking snippets and hardcoded URLs that need re-pointing |
| Product videos | 8videos≈ 32 minre-upload and re-attach, ~4 min each | By handthe product CSV does not carry video or 3D media, so every one is a manual re-upload. They also cannot be pulled straight from a remote URL — the bytes have to be downloaded and staged first, and a wrong content type lands the file as a generic attachment that media-restricted fields then reject | Automatedvideo bytes downloaded, staged through a proper upload target, re-attached to the right product, and verified as processed rather than silently failed |
| Customers | 800customers≈ 2 hrsCSV import, then cleaning up the rows that fail | By handthe importer works, but marketing consent is the exposure: the CSV carries the current opt-in state and NOT the timestamp or source behind it. Re-opting someone in is a compliance breach, dropping them burns list revenue you paid for, and you cannot prove which happened afterwards. Default-address designation is also lost | Automatedcustomers upserted by email with every address, the default-address designation, and email and SMS consent states and timestamps preserved exactly as they were |
| Order history | 2,200orders≈ 8 hrsa paid third-party importer, plus a day of mapping and reconciliation | By handShopify's own CSV importer cannot create orders at all, so the hours here assume you buy a third-party importer — key them in by hand instead and 9,400 orders is closer to 390 hours, which is why nobody does that and why order history is simply abandoned in most DIY moves. Then support cannot answer a warranty claim, repeat-purchase segments are empty, and every returning-customer flow starts from zero. Getting the mapping wrong duplicates orders or re-dates them to today, and both are worse than not importing at all | Automatedfull order history recreated through the API with line items, properties, customers re-associated, original dates and tracking numbers intact |
| Navigation menus | 3menus≈ 1 hrsabout an hour to rebuild and relink them all by hand | By handmenu items store resource IDs, not paths, so nothing about them is portable — every link has to be re-pointed at the equivalent collection, page or product on the new store | Automatedmenus rebuilt with their nesting, and every item re-pointed at the equivalent object on the new store |
| Discount codes | 22discounts≈ 1 hrsabout 1 hr via the discount CSV, or ~3 hrs rebuilt by hand | By handthe discount CSV covers basic codes, but automatic discounts, quantity breaks and combination rules are not in it and have to be reconstructed by hand. A subtly wrong rule is worse than a missing one, because nobody notices until it has been over-discounting for a fortnight | Automateddiscounts recreated through the API with their rules, usage limits and dates intact, including automatic and free-shipping types |
| Blogs & pages | 47articles & pages≈ 3 hrsrecreated one at a time, ~4 min each | By handno CSV route for either. Articles also have no SEO fields of their own — their title and description tags live in metafields — so a hand-rebuilt blog loses its SEO even when every word of the text is right | Automatedarticles and pages recreated with authors, tags and publish dates, their SEO written to the metafields Shopify actually stores it in, and inline image URLs rewritten |
| Apps & app data | 10apps≈ 10 hrsabout 1 hr per app to reinstall, reconfigure and re-test | By handmost app data lives in metafields on your products and customers, so reinstalling the app gets you an empty app: reviews gone, subscription plans gone, loyalty balances gone, bundles gone. Flows and automations have to be rebuilt by hand and re-tested, and anything with its own billing has to be re-subscribed | Automatedthe metafield data your apps rely on migrates with the products and customers it hangs off, so a reinstalled app finds its data waiting instead of an empty store |
See these numbers for YOUR store, free
The figures above are a typical store in your category. The demo scan connects read-only to yours and counts the real thing — every product, variant, image, customer, order and metafield — then tells you exactly what a migration would carry across. No card, and it never writes to your store.
▶ Run the free demo scanDoes this need a new company?
You do not genuinely need a new legal entity to apply. A new company will not reset your MATCH listing, and an acquirer will underwrite the person and the processing history anyway. If you are applying to a new processor, use the same entity you have. Spin off a separate company only if you want to sell products that are genuinely different in category or risk — and even then, the owner shows up in underwriting.
Frequently asked
Will a new store improve my odds of approval?
Not on its own. A new Shopify store is a clean slate for the platform, but payment processors do not see it that way. They see the person and the processing history. If Shopify Payments declined you, it was because of what you sell or how you market it, not because your store is old. Moving to a new store without fixing the product names, the claims and the supplier documentation just means you get declined faster by the next processor. Fix the store first. Then apply.
Which gateway should we use after Shopify Payments?
The gateway is the easy part. Several high-risk acquirers publicly underwrite functional mushrooms — you can route through Authorize.net on a high-risk MID, or through gateways that work with PaymentCloud, Corepay, Easy Pay Direct, Soar Payments and Inovio. The hard part is the merchant account behind the gateway. Which one will take you, at what rate and with what reserve, depends on your volume, your supplier documentation and whether your product names and claims pass a real human review. Rather than send you to cold-email brokers, use the quote form on this page.
What reserve should we expect?
High-risk acquirers in the supplement space typically hold 5–10% of your monthly revenue in a rolling reserve for 90–180 days. That means if you process 10,000 pounds in a month, 500–1,000 pounds is held back and released slowly as time passes and chargebacks do not appear. The exact number depends on your ticket size, your refund rate and your chargeback history. Subscription revenue is often held longer because chargebacks on recurring charges trend higher. Budget for a 90-day cash gap when you switch processors.
Do supplier COAs survive a store migration?
Not automatically. If your COAs or test results are stored as product metafields or as links to files in your old store, a standard store migration will copy the file paths but not update them. The page renders fine but the link points nowhere and the customer sees a 404. If you migrate, you must either re-upload all compliance files to the new store or update all the metafield references by hand. This is why many mushroom sellers do a test migration first and check a few key products for missing files before going live.
Why can't I just open a new company and reapply to Shopify Payments?
Because MATCH does not list only the company — it lists the people behind it for five years. If you are the beneficial owner of the terminated account, every processor screens you personally, and a new company with your name on it presents the same way. A new entity is the right move for structural business reasons, but it is not a way to look like a different applicant. Anyone selling it to you that way is selling fraud, and it will not work.
How do I know if I'm on MATCH?
Shopify will not tell you. You can query the MATCH database through third-party screening services, or apply to a new processor and ask them to run a check when they decline you. If you are listed, every detail of your termination is there. If you are not listed, the termination is contained to Shopify and Stripe, and you have clearer options for migration.
Can I appeal my termination to Shopify Payments?
The appeal goes to Stripe, Shopify's underwriter, and it succeeds only if you can show a factual error — a misidentified category, a misread of your transaction history, or similar. If Stripe terminated you because your business model itself does not fit their underwriting, no appeal changes that. Stripe publishes no timeline for review and the answer is final.
What happens to my money when Shopify Payments is terminated?
It freezes pending resolution of the underwriting review. There is no published hold period — it can be weeks or indefinite. If you are also on MATCH, the freeze can last years. Once the review closes, you either get access restored and a payout scheduled, or you forfeit the balance. Check your termination notice for the specific details of your hold.
Can you turn my Shopify Payments back on?
No processor can. We are a migration service — we move your store and its data into a new shop built on a gateway that will accept you. We cannot turn Shopify Payments back on and we cannot help you evade MATCH. What we do is extract your complete store — catalog, orders, customers, metadata — before access closes, and rebuild it somewhere you can actually sell. That is only the move if you have a destination processor that will underwrite you truthfully.
Move everything, verified twice, from $247
Pick a package and the migration order form unlocks immediately. Your existing store is only ever read from — we never write to it, so nothing you still have can be made worse. How the migration runs, step by step →