Selling functional mushrooms on Shopify. Payments is the hard part.
Functional mushrooms like lion's mane and reishi are legal supplements, but payment processors pattern-match on the word and decline first. Specificity fixes it.
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.
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
Those are typical figures for this category. The read-only scan counts what is actually in your store, so you know the real scale before you decide anything. No card, and it works even if your storefront is already offline.
▶ Run the free demo scanWhy 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 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.
New company, new merchant account — the honest version
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.
What a MATCH listing actually is
- A listing lasts five years from the date it is added, then ages off automatically. There is no performance-based early release.
- It lists the principals — name, tax ID, address — as well as the business, which is exactly why a new company with the same owners is not a fresh start.
- Only the acquirer that listed you can remove it, and only in two situations: the listing was made in error, or the reason code was PCI non-compliance and you have since become compliant.
- Reason codes are specific and they matter: excessive chargebacks reads very differently to an underwriter than laundering or illegal transactions.
- It is not a card-network ban. High-risk acquirers knowingly board MATCH-listed merchants — at worse rates, with larger reserves, and with volume caps.
- You are entitled to ask the terminating acquirer whether you were listed and under which code. Do that before you apply anywhere else, because you will be asked.
What a new merchant account requires
The entity
Formation documents, EIN or company number, and a business bank account in the company's name with a voided cheque or statement.
The people
Government ID and personal details for every beneficial owner. Underwriting is done on the humans as well as the company — which is why a new company with the same owners does not present as a new applicant.
The history
Three to six months of processing statements if you have any, plus bank statements. A prior termination is disclosed here. Concealing it is the fraud, not the termination.
The website
A live, compliant storefront: clear billing descriptor, contact details, terms, refund and shipping policies, SSL, working checkout, and no claims that contradict your category.
The product
Supplier agreements, certificates of analysis for anything ingestible, licences for anything regulated, and evidence of how you fulfil.
The numbers
Expected monthly volume, average order value and your chargeback history. Understating volume to get approved is a fast route to a frozen account.
A MATCH screen
Run against both the business and its principals. This is the step that decides the application, and there is no way around it — only through it, by disclosing and finding an acquirer who underwrites anyway.
If you do need a new entity, these are the routes people actually use
Costs and timelines below are indicative and go out of date — treat them as a starting point, not a quote.
Wyoming is the default for an ecommerce LLC: ~$100 to file, ~$60/yr to maintain, no state income tax and strong owner privacy. Delaware is the investor standard and costs $300/yr in LLC franchise tax for governing law most DTC stores will never rely on. If you are not raising money, Wyoming is almost always the right answer.
Move everything for a fixed price
One-time packages — no per-record metering, no quotes. The migration order form unlocks the moment you pay, and the whole migration re-runs a second time before any cutover.
How the migration runs
- Book & pay — fixed price, secure Stripe checkout. The order form unlocks immediately after payment.
- Submit your stores — domains and details in the order form; then provide revocable API tokens in your customer area (we never ask for your Shopify password).
- We migrate everything — your live store keeps selling throughout; it is only ever read from.
- Verified twice — the entire migration re-runs and must change nothing; you get the count-matched verification report before any cutover.
See exactly what would move — before you spend anything
The demo scan connects read-only to your current store and counts every product, variant, image, customer, order and metafield in it, then tells you what a migration would carry across. It never writes to your store, and it works even if your storefront is already offline.
▶ Run the free demo scanIf it has already happened
Whatever Shopify has actually done — disabled the gateway, opened a review, frozen your payouts, closed the store — the recovery differs. Find the one that matches your notice:
Shopify Payments Disabled for a Mushroom Brand? How to Recover
Shopify Payments disabled — what it means specifically for functional mushrooms.
Shopify Payments Account Under Review for a Mushroom Brand? How to…
Account under review — what it means specifically for functional mushrooms.
Shopify Payments Not Available for a Mushroom Brand? How to Recover
Application rejected — what it means specifically for functional mushrooms.
High Chargeback Rate Warning for a Mushroom Brand? How to Recover
High chargeback rate — what it means specifically for functional mushrooms.
High-Risk Payment Gateway for Shopify for a Mushroom Brand? How to…
Finding a high-risk payment gateway — what it means specifically for functional mushrooms.
Migrate a Shopify Store to a New Account for a Mushroom Brand? How…
Migrating to a new Shopify store — what it means specifically for functional mushrooms.
New Company for a New Merchant Account for a Mushroom Brand? How to…
New company, new merchant account — what it means specifically for functional mushrooms.
Shopify Payouts on Hold for a Mushroom Brand? How to Recover
Payouts on hold — what it means specifically for functional mushrooms.
Shopify Payments Prohibited Business for a Mushroom Brand? How to…
Prohibited business type — what it means specifically for functional mushrooms.
Shopify Payments Terminated for a Mushroom Brand? How to Recover
Shopify Payments terminated — what it means specifically for functional mushrooms.
Shopify Store Suspended for a Mushroom Brand? How to Recover
Shopify store suspended — what it means specifically for functional mushrooms.
Shopify Payments Rolling Reserve for a Mushroom Brand? How to Recover
Rolling reserve imposed — what it means specifically for functional mushrooms.
How to Reactivate Shopify Payments for a Mushroom Brand? How to…
Appealing a Shopify Payments decision — what it means specifically for functional mushrooms.
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.
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.