Shopify Payments disabled, and you sell delta-8 and THCA products. Migrate everything to a new Shopify store.
The email is short and it reads like a verdict: Shopify Payments has been deactivated, payouts stop, and support points you at the Terms of Service. Here is the part almost nobody tells you, and it is the only part that changes what you should do today. Your store has now been flagged. Shopify Payments is underwritten by Stripe, so your product category tripped a payment processor's policy — but the review happened against your account, and the account keeps that record. Bolt on a third-party gateway and you have changed who settles your money. You have not changed what Shopify knows about your store, and its terms allow it to act again at any time, on notice. Merchants report the same sequence constantly: payments off, a few more weeks of trading, then a second review that closes the store for good. So treat this as step one of two. Get a full copy of your store somewhere you control, now, while you can still log in — even if it is only a backup plan you never use.
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
- "Shopify Payments is no longer supported for your business type" — with no detail about which part of your business
- Payouts stopped, while orders that already went through keep needing to be fulfilled
- Checkout still working for days or weeks afterwards, which feels like a reprieve and is really a countdown
- Support declining to discuss the decision, and pointing at the Terms of Service
- A request for invoices, supplier agreements or fulfilment evidence that arrived shortly before the shutdown
- And the one nobody warns you about: your account now carries a risk-review record that a new gateway does not erase
The hold is the visible problem. The stall is the expensive one — every day without a working checkout burns the ad spend that produced the traffic anyway. But the risk nobody warns you about is the third one: your account has now been through a risk review, and it keeps that record. A new processor changes who settles your money. It does not change what Shopify knows about your store, and the terms let Shopify act again at any time on notice. Assume this is step one of two, and get a copy of everything out while you can still log in.
Why it happened — specifically for delta-8 and THCA products
Stripe, which underwrites Shopify Payments, prohibits cannabinoid products above the local THC limit—and delta-8 and THCA edibles fall squarely into that category. The primary trigger is the intoxicating effect itself. The secondary trigger is volatility: state bans arrive with weeks of notice and federal hemp-derived THC policy is actively changing, which means an acquirer's risk profile can flip between underwriting and settlement. That legislative uncertainty is what makes delta-8 and THCA fundamentally different from CBD—it is not just a chargebacks problem, it is a jurisdiction problem.
Rule out the easy fix first — then deal with the real one
Shopify does not document a route to use Shopify Payments for this category, and you should not spend time looking for one. What merchants typically do instead is cold-email high-risk acquirers, get declined by most, then accept whoever takes them last. That fails because you end up negotiating from desperation, not strength. The honest path is to identify acquirers upfront who publicly advertise this category, prepare your underwriting documents properly, and apply to three or four in parallel so you can choose.
It only helps if all of these are true:
- Your store must clearly display the THC percentage or lab result for each product
- Age verification at checkout must block minors in your jurisdiction
- You cannot make therapeutic claims—structure and function language only
- Your processing history cannot show chargebacks over 0.5% or payment disputes over 2%
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 people swallow, inhale or put on their skin, the trigger is almost always claims, not chemistry. Processors read your product pages the way a regulator would: a supplement that "supports healthy joints" is a supplement, and one that "eliminates inflammation" is being sold as an unapproved drug. Reviewers also weigh dispute rate, because consumables attract "it didn't work" refunds that become chargebacks. Before you approach anyone new, get the claims language reviewed and have your certificates of analysis somewhere a human can find them in ten seconds.
⚖️ Legal status is genuinely contested or actively changing
This is the hardest category to get underwritten, and the reason is not your business — it is that the rules themselves are moving. Processors price legislative risk, not just chargeback risk, because a statutory change can make a compliant merchant non-compliant overnight and leave the acquirer holding the liability. Expect the largest reserves in the high-risk market, expect to re-document compliance more often than other merchants, and build the business so that a rule change in one jurisdiction costs you that jurisdiction rather than your whole company.
🔞 Requires age verification, and shipping is regulated in its own right
Age-restricted categories get declined on process, not product. The underwriter's question is not whether your goods are legal, it is whether you can prove a minor cannot buy them and that you are meeting the shipping regime that applies — carrier restrictions, adult-signature delivery, state registration and remittance where required. A real age gate, a compliant carrier arrangement, and evidence you geo-block the jurisdictions that ban you will change the outcome of the next application far more than any appeal to this one.
What you actually have to fix
Underwriters do not change their minds because you asked. They change them because the facts changed. For delta-8 and THCA products, these are the facts that move the decision:
Map which US states allow your products and restrict accordingly
State bans arrive with weeks of notice and THC limits vary widely. You need a documented inventory of where delta-8 and THCA are legal at the potency you sell, and you must block checkout or refuse shipment to states where they are banned. An acquirer will ask for this audit and will expect you to monitor it continuously. Use your payment processor's geoblocking tools, update your terms of service to reflect current law, and log your compliance checks—do not assume last month's legal map is still current.
Gather lab-verified COAs and test results for every product
Acquirers in this space require third-party certificates of analysis showing THC and cannabinoid content before they will underwrite you. If you do not have them, you will be declined immediately. Order them from a DEA-registered lab, file them as a metafield on each product so they appear on your product pages, and keep originals. Reviewers read these first—if the lab report does not exist or does not match your label, the application dies.
Implement age verification and geoblocking at checkout
Your payment processor will require documented age verification that blocks customers under 21 (or your jurisdiction's limit) before payment. Shopify has age-verification apps; you may also use third-party compliance services. Combine this with geoblocking to prevent sales to banned states. Both must be live and logged before you apply—an acquirer will test them.
Remove all therapeutic language from product pages and marketing
Any claim that your product treats, prevents or cures a condition—anxiety, pain, inflammation, sleep—will cause immediate decline. Rewrite descriptions to use structure and function language only: 'contains delta-8' instead of 'relieves anxiety'. Audit blog posts, email sequences, customer reviews you display, and social-media links. Regulatory reviewers read everything publicly attached to your brand.
What underwriting will ask you for
- Third-party lab COAs (certificates of analysis) for every SKU showing THC and cannabinoid content
- State-by-state hemp legality audit confirming your products meet local thresholds in states you ship to
- Processing history from your previous processor, including chargeback rates and decline codes
- Compliance officer contact and incident disclosure form
- Product compliance and labelling review showing age restriction and potency on packaging and web
- Business tax returns or 1099s for the past two years
- Detailed description of your customer acquisition and fraud prevention
- Underwriting questionnaire covering inventory control and state regulatory monitoring
Getting underwritten for delta-8 and THCA products
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite delta-8 and THCA products. 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 delta-8 and THCA products
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
- Work out which layer actually said noThere are three, and they have completely different consequences. If Shopify Payments declined you, your store is still open and you need a different gateway. If the Shopify platform suspended you under the Acceptable Use Policy, no gateway on earth fixes that. And if a third-party gateway's acquiring bank dropped you, that is a third decision with its own appeal route. Read the notice for which entity is speaking before you spend a day fixing the wrong problem.
- Get a verified copy out while you still have access — todayThis is the step people skip, and it is the only one with a deadline you do not control. A payments deactivation is not the end of the process. It is the first thing that happened. Your account has now been through a risk review and it keeps that history — the flag does not leave when the gateway does. Bolting on a third-party processor changes who settles your money; it does not change what Shopify knows about your store, and Shopify's own terms let it act again at any time, on notice. Merchants report exactly that sequence constantly: payments off, trade on for a few weeks, then a second review that closes the store. And if the store closes, admin access can go with it. That is the part that turns a bad month into a dead business, because with no admin there is no API — and with no API your catalog, your order history, your consent timestamps and every metafield your theme renders from are simply gone. Not deleted; unreachable, which is the same thing. Shopify's own CSV export cannot carry metafields, metaobjects, orders or gift card codes, so "I'll just export it" is not the plan you think it is. Take a full, verified copy into a store you control now, while you can still log in. If you recover, you have lost nothing but the price of a migration. If you do not, you still have the business.
- Fix the thing that triggered itUnderwriters do not reverse a decision because you asked nicely; they reverse it because the facts changed. That usually means product labelling and claims, an age or geography gate you were not running, a clearer billing descriptor, published shipping and refund terms, or evidence of fulfilment for the orders that generated disputes. Unglamorous, and the step that decides whether the next processor keeps you — because whatever tripped the first review will trip the second one too.
- Get underwritten somewhere that wants your categoryHigh-risk acquiring is an entire industry that exists precisely for businesses Stripe declines. You apply as what you are, disclose the termination, and expect worse terms than a low-risk merchant gets — a rolling reserve, higher rates, a volume cap. On Shopify the practical route is a high-risk merchant account fronted by a gateway Shopify supports natively, which keeps checkout on your store rather than sending customers off-site.
- Decide whether you need a new entity — honestlySometimes you genuinely do: a new legal entity is the right answer for an acquisition, a partner split, a change of jurisdiction, or separating a high-risk product line so it can never take your main brand down with it. Sometimes it is being sold to you as a way to look like a different applicant — which is a completely different thing, and is fraud. The section below is blunt about which is which.
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
Delta-8 and THCA stores keep compliance data in metafields: lab COAs, THC percentages, batch numbers, state legality flags and age-restriction rules. When you migrate by hand or use Shopify's native CSV export, metafields are silently dropped—your product pages render, but the lab results and potency data disappear, leaving customers unable to verify what they are buying and exposing you to chargebacks and regulatory risk. A proper migration tool carries those metafields forward and re-validates them in the new store.
| What you own | How much of it | What breaks doing it by hand | What we do instead |
|---|---|---|---|
| Product images | 2,240images≈ 9 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 | 1,680variants≈ 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 | 5,040metafields≈ 34 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 | 437records≈ 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 | 12videos≈ 48 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 | 4,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 | 8,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 | 45discounts≈ 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 | 12apps≈ 12 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 will not help you. Acquirers and MATCH databases follow the person running the business for five years, not the company name. If you were declined or terminated before, opening a new LLC with the same owner will not reset that history—you will still inherit it. The real fix is fixing the compliance gaps, then applying to acquirers with full disclosure of your processing history.
Frequently asked
Will Shopify Payments ever process delta-8 and THCA?
No. Stripe, the processor behind Shopify Payments, prohibits cannabinoid products above the local THC limit. That policy is not changing. If you are on Shopify Payments now, your account will be terminated. Your only path forward is to migrate to a store using a third-party payment processor that openly accepts this category—that requires moving your entire store, not just switching gateways.
Which payment processor should I use?
Several high-risk acquirers publicly advertise delta-8 and THCA, and they integrate with Shopify through Authorize.net, PaymentCloud, Bankful, DigiPay, Corepay, Easy Pay Direct and Durango. The processor itself is not the bottleneck—the underwriting behind it is. Which one will approve you depends on your lab results, your state legality audit, your processing history and your compliance setup. Rather than apply cold to all of them, prepare your documents first, then apply to three or four in parallel.
How much will my payment processor reserve?
Acquirers in this category typically hold 10–25% of your transaction volume in a rolling reserve, often for 180 days or longer. That means if you process $10,000 in a week, your processor keeps $1,000–$2,500 locked away, released slowly. Budget for this as working capital—it is not a fine, it is a buffer against chargebacks and refunds. Ask your processor upfront what their reserve policy is before you sign.
Will my product data survive a store migration?
Standard migrations drop metafields, which is catastrophic for you because your lab results, THC percentages and batch numbers live in metafields. Your products will copy over, but without the compliance data attached. A proper migration tool preserves metafields by reading and writing them through Shopify's API, then validates them in the new store. Verify with your migration provider that they carry metafields forward—if they do not, you will have to re-upload every COA and test result by hand.
Can I get Shopify Payments reinstated?
Occasionally, when the decision rested on a fact you can correct and evidence — a mislabelled product, a missing licence, an unclear descriptor, fulfilment records for disputed orders. If your product category is on the payment processor's prohibited list, no reviewer has the authority to grant an exception, and waiting for one costs you the selling window. Appeal once in writing, then start the alternative the same day.
How long does Shopify hold my money after Shopify Payments is disabled?
A standard hold against chargeback risk runs up to 120 days from the last transaction, because that is roughly how long a cardholder has to dispute one. It can run longer where Shopify suspects illegitimate commerce. The held balance is still yours and is normally released after the window; it is the loss of a working checkout, not the hold itself, that does the real financial damage.
Do I need a new Shopify store, or just a new payment gateway?
If only Shopify Payments was disabled, your store is fine — you need a third-party gateway whose acquiring bank accepts your category, and nothing has to move. You need a new store when the platform itself closed the old one, when you are separating a high-risk product line into its own entity, or when a new provider requires a clean install. Those are genuinely different situations and it is worth being sure which one you are in before you migrate anything.
Will opening a new company get me a new merchant account?
Not by itself, and this is the most important thing on this page. MATCH — the card networks' terminated-merchant file — lists the people behind a terminated business as well as the business, for five years, and every acquirer screens it. A new company with the same beneficial owner does not present as a new applicant. A new entity is the right answer for real structural reasons; it is not a way to look like someone else, and anyone selling it to you that way is selling you fraud.
Can you get my payments turned back on?
No, and nobody outside Shopify and its payment processor can. We are a migration service: if you need to move to a new store built around a gateway that accepts you, we move everything into it — catalog, customers with their consent states, full order history, metafields, theme, redirects — and prove nothing was lost by re-running the entire migration a second time.
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 →