Prohibited business type, and you sell functional mushrooms. Migrate everything to a new Shopify store.
You applied for Shopify Payments and got a rejection that said your business type is not supported. You then searched Shopify's help centre for the prohibited list and found nothing, because Shopify does not publish one. Here is why that matters, and what to do. Shopify Payments is underwritten by a payment processor — Stripe, PayPal or Adyen, depending on your country. Shopify's own terms defer to the processor's underwriting rules. That means the restriction you hit is not Shopify's rule. It is the processor's rule, and it lives in a document you need to find and read. The operative document is your processor's restricted-businesses list. That list is not a vague policy. It is a specific set of business types, and if you can prove you do not belong in it, or that you belong in a carve-out, you have a move. If you do belong in it, a third-party gateway — one with a different acquiring bank — may accept you. Find out which one you hit first.
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 business type is not currently supported" — with no link to which list that came from
- Shopify help articles about Stripe's restricted list, but no link to Stripe's actual list — and Stripe's list changes
- Confusion about whether this is a Shopify decision or a processor decision
- Assumption that switching to another Shopify theme or store will reset it
- Search results for "Shopify prohibited business" returning other merchants' stories, not policy
Time matters here, but not for the reason you think. The decision is final unless you have new facts. A processor will not reconsider on the same evidence. But if you can submit a real carve-out — a specific merchant code, a subcategory exception, a proof of age or licence — the window to reapply stays open only as long as your business looks the same to their automated screening. The move is to find which processor will take you, and that is urgent because the longer you operate without a payment gateway, the harder it becomes to get one.
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
For anything swallowed, inhaled or applied, you are caught between two decisions: Shopify's platform policy and your processor's restricted list. Shopify Payments itself does not publish its own prohibited list — it delegates to the processor (Stripe, PayPal or Adyen depending on your country). So the operative document is your processor's list, not Shopify's help centre. Health claims are the usual trigger. A product page saying 'supports healthy joints' is treated differently from one saying 'eliminates inflammation'. Before approaching a new processor, have your product claims reviewed by someone who reads them the way a regulator would. Dispute rates matter too: consumables attract 'it did not work' chargebacks, which processors price heavily.
🔁 Recurring billing is a large share of revenue
Shopify Payments delegates to your country's processor (Stripe, PayPal or Adyen). If you lose that processor, your stored payment methods stop working immediately, and every subscriber's next billing attempt fails. Those stored methods are held by the processor, not by you, and they cannot be exported or moved. A subscription business loses new orders and then bleeds existing revenue every day the account stays closed. Restarting means either a processor-to-processor migration arranged in advance, or asking thousands of customers to re-enter a card — which never fully recovers. Before anything else, deal with your subscription book and whether your replacement processor can take it on.
⚖️ Legal status is genuinely contested or actively changing
Shopify Payments delegates to your processor (Stripe, PayPal or Adyen). That processor's acquiring bank is pricing legislative risk, not just chargeback risk. If your legal status is contested or changing, acquirers step back — not because you are committing fraud, but because the regulatory ground is moving. They reserve the right to exit overnight if the law shifts. That is distinct from being prohibited outright. You need a processor who explicitly prices legal-volatile categories and holds capital against the political risk. Stripe's restricted list and your country's processor's policies are checkable. But you also need to know: would a replacement processor accept you if legality became temporarily ambiguous? Ask that before you migrate.
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
- Find your processor and read its actual restricted listFirst: confirm whether you are in Shopify Payments or applying now. If you are in a Shopify store already, your processor is in your admin under Settings → Payment providers. If you are applying, your processor is determined by your country — see shopify.com/legal/processor-list. Once you have the name, find the processor's restricted-businesses document. For Stripe, this is at stripe.com/docs/connect/restricted-businesses. Do not rely on secondhand descriptions or forum posts. Read the actual list. Your business type may be listed with a carve-out you did not know existed.
- Check whether you meet a documented exceptionRestricted lists often include carve-outs. A category like "adult" may permit age-gating and ID verification. A category like "financial services" may permit licensed brokers but not unlicensed advisors. A category like "gambling" may permit lottery retailers but not online betting. Find the line that describes your business and read every word after it. If there is a condition you can meet — a specific merchant code, a government licence, a regulatory exemption — note it. This is the only path to reapplication on the same processor.
- Reapply with documentation of the exceptionIf you found an exception that applies to you, gather the documentation it requires: a licence, a registration, a certification, a merchant code, proof of age-gating, or whatever the list specifies. Submit a new application to the same processor with that documentation attached and a short note saying: "I believe I meet the exception at [the exact line]. My documentation is attached." Include the reference to the specific exception in the list itself. Do not argue that the rule is unfair. Do not submit a general appeal. The processor's automated screening will reject you again unless you are answering a specific carve-out.
- Get a verified copy of your store — before applying elsewhereIf the processor will not move, you will move to a different gateway. This is the moment to export a full backup of your store, before anything else changes. You need your catalog, your customers, your order history, your SEO metadata, your theme settings, your discount codes — everything. Shopify's CSV export cannot carry metafields, orders, gift card codes, videos, menus, discounts or redirects. That is the strongest reason to move to a new store built around a processor that will accept you: a fresh build with a proper migration handles the things CSV cannot. Get the backup now, while you have access and the store is still live.
- Move to a new store with a processor that accepts your businessOnce you know which processor rejected you, and whether you can appeal it, find a payment gateway that accepts your category. This means a different processor, which usually means a new Shopify store built around that gateway. A migration service can move your catalog, images, SEO data, theme, customers, orders and other data into the new store, then run the migration twice and compare counts to check nothing was lost. The move costs money and time, but it is the legitimate path from a misfit processor to a fit one. You are not hiding anything; you are disclosing your category truthfully to a processor who will accept it.
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.
Is there a Shopify Payments prohibited business list I can check?
No. Shopify Payments does not publish a list of prohibited business types. The payment processor for your country publishes one instead. Shopify's terms say the processor decides which categories are supported. If you were rejected, you need the processor's actual list, not Shopify's. You can find your processor at shopify.com/legal/processor-list, then search that processor's website for "restricted businesses".
Why did I get rejected if my business is legal?
Legal status and payment processor underwriting are different things. A processor may restrict a category for compliance, fraud, or chargebacks — not because it is illegal, but because the processor's risk profile does not cover it. Adult services, gambling, CBD, debt settlement and firearms are commonly restricted even where they are legal. The processor makes the call, and legality is not the only factor.
Can I reapply to the same processor?
Only if you have new facts. A processor will not reconsider on identical information. But if the restricted list includes a carve-out for your business — a specific merchant code, a licence requirement, an age-gating requirement — and you can document that you meet it, you can reapply with that evidence. Read the actual list line by line. Many merchants miss the exceptions because they are buried in small text.
What if I open a new store or company?
A new store on the same processor will be screened against the same criteria you just failed. A new company does not change your screening category. The processor is evaluating your business type and category, not your legal entity name. If Stripe rejected your business type as an individual, Stripe will reject it again when you apply as a limited company. The category itself is the issue, not your legal structure.
Can you turn Shopify Payments back on or move me to a different processor?
No. We cannot persuade a processor to accept your category or change their underwriting decision. What we do is help you move your entire store — catalog, customers, orders, SEO data, theme, everything — to a new store built around a processor that will accept your business type. We move the data, you provide the processor. The move is fixed price from £247, and we run the migration twice to compare counts against what was lost.
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 →