Prohibited business type, and you sell kratom. 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 kratom
Shopify Payments is underwritten by Stripe, and Stripe's restricted-businesses policy covers substances designed to mimic illegal drugs. Kratom is declined under that clause, not by a named category—it is not explicitly listed, but it sits in a family of botanicals that trigger the restriction by analogy. The secondary trigger is jurisdiction: kratom is banned outright in several US states and countries, which means your buyer's location itself can be a disqualifier even if your store is legal where you operate.
Rule out the easy fix first — then deal with the real one
Rule this out first. Shopify does not document a kratom-specific route. You might try the Attestation for the Sale of Hemp and Hemp-Derived Products, but kratom is botanically distinct from hemp and not covered by that pathway—applying through it will almost certainly be declined. The honest equivalent is that most merchants in this category go straight to third-party high-risk acquirers rather than waste time on platform-layer exceptions. The acquirer will run its own underwriting on your claims, your shipping destinations and your processing history, and that is where the real decision happens.
It only helps if all of these are true:
- You operate and ship only to US states where kratom is not banned.
- Your product descriptions make no medical or therapeutic claims.
- You can document age-gating at checkout to prevent sales to minors.
- You have not been declined by another payment processor for this category.
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.
⚖️ 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.
🔞 Requires age verification, and shipping is regulated in its own right
Shopify Payments delegates to your country's processor (Stripe, PayPal or Adyen), and that processor's restricted list is the decision that matters. But age-restricted businesses face a second layer: carriers and state registration. FedEx, UPS and USPS each have their own rules about what they will ship and to which states. The gateway decision and the shipping decision are separate problems. Even if you find a processor willing to work with you, you still need carriers who will move your inventory. That second conversation is not about payment processing — it is about logistics compliance, and it happens independently. Map both before you commit to a migration.
What you actually have to fix
Underwriters do not change their minds because you asked. They change them because the facts changed. For kratom, these are the facts that move the decision:
Remove all therapeutic claims from product pages and marketing
This is the single highest-yield fix. Any language stating or implying your kratom treats, prevents or cures a condition—pain, anxiety, energy, focus—reads to an underwriter as marketing an unapproved drug. You must audit product descriptions, blog posts, reviews you display, email flows and social media links, because acquirers review all of them. The defensible frame is 'traditional use' or 'botanical source'; therapeutic claims disqualify you outright.
Map your shipping destinations and exclude banned jurisdictions
Kratom is banned in several US states and in countries outside the US. You cannot legally ship to those places, and processors will decline you if they see orders going there. Before you apply, identify which states and countries you will serve, document that decision, and implement shipping restrictions at checkout that match it. Acquirers ask for this map explicitly, and it must be consistent with your actual fulfillment.
Document your age-gating system and enforce it at checkout
Kratom is age-restricted in many jurisdictions. You must have a checkout mechanism that verifies the buyer's age before payment—usually 18 or 21 depending on local law. Screenshot your implementation and document what age gate your system enforces. If you rely on manual verification or honour-system checkboxes, you will be declined.
Gather lab reports and compliance documentation before applying
Acquirers in this category ask for certificates of analysis (COAs) from your suppliers, showing alkaloid profiles and contaminant testing. Have these documents ready, named consistently and hosted somewhere you can quickly share them. If your supplier cannot provide them, find one who can—the absence of lab data is an automatic decline.
What underwriting will ask you for
- Lab report or certificate of analysis (COA) confirming the kratom's origin, alkaloid profile and absence of contaminants.
- Shipping and state-ban compliance map showing which US states and countries you do and do not serve.
- Age-verification system documentation proving you gate sales to 18 or 21 depending on local law.
- Merchant processing history for the past 24 months, including any prior payment processor declines.
- Clear product descriptions showing no medical or therapeutic claims—structure and function language only.
- Proof of regulatory compliance documentation for any state where kratom faces additional licensing or registration requirements.
- Customer acquisition strategy and marketing channels, confirming no claims of health benefits.
Getting underwritten for kratom
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite kratom. 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 kratom
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 kratom store's data is unusually dangerous to move by hand because compliance content lives in metafields. Lab-report file references, alkaloid testing data, COA document links and batch-compliance notes are stored as reference-type or file-type metafields that a CSV export cannot carry at all. If they are copied naively they keep pointing at the old store's assets, so pages render but lab data silently vanishes—and on a regulated botanical product, missing compliance documentation is a risk you cannot take.
| What you own | How much of it | What breaks doing it by hand | What we do instead |
|---|---|---|---|
| Product images | 1,400images≈ 6 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 | 280descriptions≈ 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 | 840variants≈ 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 | 1,680metafields≈ 11 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 | 430records≈ 3 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 | 1,200customers≈ 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 | 4,100orders≈ 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 | 30articles & pages≈ 2 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?
A new legal entity does not reset your payment history. Shopify Payments and other processors maintain records on the beneficial owner, not just the company name, and a new company on the same ownership will be declined the same way. You should form a new entity only if your business model genuinely requires it—not as a workaround for a processor decline. A new entity bought time in the past; it does not now.
Frequently asked
Will Shopify Payments approve kratom if I change my claims?
No. Shopify Payments is underwritten by Stripe, and kratom is declined by category policy, not by the content of your pages. Removing therapeutic claims helps you with a third-party acquirer, but it does not unblock Stripe itself. You must move to a high-risk payment processor that explicitly underwrites botanical or restricted substances. That is a different underwriting path, not a fix to the one you are on.
Which payment gateway will actually approve my kratom store?
Several high-risk acquirers publicly underwrite kratom—PaymentCloud, Soar Payments and Easy Pay Direct are the most established—but approval is never guaranteed and depends on your geography, your claims, your volume and your processing history. Rather than email them cold, use the merchant quote form on this page and we will put you in touch with an acquirer that has capacity in your segment. The gateway is the easy part; the merchant account underwriting is where the decision is made.
What reserve should I expect if I get approved?
High-risk kratom processors typically hold a rolling reserve of 10–25%, sometimes for 180 days or longer. That means if you process 10,000 pounds in sales, 1,000 to 2,500 pounds sits in the processor's account rather than yours. Reserves are higher if you are new to the category or if you have a history of chargebacks. Ask for the reserve terms upfront in writing before you sign anything.
Will my lab reports and compliance metafields survive a store migration?
No. Shopify's CSV export cannot carry metafields, and if you copy them manually they will point at URLs in your old store. Lab reports, COA files and alkaloid data must be re-hosted on the new store and re-linked explicitly. We rebuild these references as part of our migration, but you must gather your source documents beforehand—have them organised and accessible before migration begins.
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 →