Shopify Payments disabled, and you sell supplements. 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 supplements
Shopify Payments is underwritten by Stripe, which allows supplements but prohibits those that are 'not safe or make harmful claims'. The primary trigger is disease claims: anything stating or implying your product treats, prevents or cures a condition reads as marketing an unapproved drug. The secondary trigger is subscription refund disputes — when a customer cancels because the product 'did not work', the chargeback rate can spike, which is why free-trial-to-subscription models are a specific, well-documented decline reason across acquirers.
Rule out the easy fix first — then deal with the real one
Rule this out first. Shopify does not document a platform route for supplements — there is no attestation or pre-approval gateway. What merchants try first is connecting Shopify Payments and hoping the underwriting review misses the claims. It usually does not. If you are reading this, that review has already declined you. The honest move is to find an acquirer who specializes in ingestible categories and whose underwriting is built around the claims audit, not a blanket refusal. That is not faster, but it is the actual path.
It only helps if all of these are true:
- Your product descriptions contain no disease claims — only structure and function language.
- You use payment methods other than free trial to subscription, or you accept a higher chargeback reserve.
- Your current processing history shows a chargeback rate below the acquirer's stated threshold.
- You have documented supplier credentials and, where applicable, third-party testing results.
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.
🔁 Recurring billing is a large share of revenue
A disabled gateway hurts a subscription business twice. New orders stop, and then every existing subscriber's stored payment method stops billing too — so the revenue you thought was predictable decays every day the situation persists. Payment methods are held by the processor and cannot simply be exported, so 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. Deal with the subscription book before you deal with anything else.
📦 Thousands of SKUs, deep variant matrices, distributor feeds
A large catalog does not affect the underwriting decision much, but it dominates everything that happens afterwards. Thousands of SKUs with deep variant matrices, distributor-fed data and years of accumulated metafields are exactly what does not survive a hand-rebuild — and a store this size is where merchants discover, weeks in, that the CSV route silently dropped the fields their theme renders from. If a move is on the table, the size of your catalog is the single biggest factor in how it should be done.
What you actually have to fix
Underwriters do not change their minds because you asked. They change them because the facts changed. For supplements, these are the facts that move the decision:
Remove or rewrite every disease claim on your store
This is the single highest-yield fix. Anything that says or implies your product treats, prevents or cures a condition — anxiety, pain, sleep, inflammation, immunity — reads to an underwriter as a drug claim, which moves you from restricted to prohibited. Audit your product descriptions, your blog, customer reviews you display, your email flows and your FAQs. Reframe in terms of structure and function: 'supports joint health' instead of 'cures arthritis', 'promotes relaxation' instead of 'treats anxiety'. Check every claim against FDA guidance on dietary supplements.
Get product liability insurance and verify coverage for ingestibles
Most acquirers will not move forward without a current certificate. This is not optional. The policy must cover your specific product type — protein powders, botanical extracts, sports nutrition — and the certificate should state that clearly. Email your broker or insurer to confirm coverage for the formulations you actually sell. When you apply, provide the certificate with effective dates and policy limits visible. Underwriters will call to verify it before they approve anything.
Document your supplier chain and testing for every product SKU
Acquirers ask for formulation sheets, ingredient sourcing, and either third-party testing results or cGMP certification from your manufacturer. This matters especially if you use botanical extracts, proprietary blends or anything that requires batch verification. Organize this by SKU and have it ready to upload with your application. If you do not have it, ask your supplier for it now. A missing COA or sourcing sheet often stalls an underwriting review for weeks.
Fix your subscription billing model if you use free trials
Free trial followed by automatic subscription is a known chargeback trigger — customers cancel late and dispute the first paid charge. If you use this model, you have two options: switch to paid trial or add a charge-delay period with clear confirmation language before the first payment. Acquirers will ask about your cancellation rate and your refund process. Lower the friction to cancel and you lower the dispute rate, which makes underwriting easier. Disclose your actual chargeback percentage upfront when you apply.
What underwriting will ask you for
- Product liability insurance certificate (required for all ingestible categories and the single most common request).
- Complete product formulations and ingredient sourcing documentation.
- Copies of all marketing claims — product pages, email flows, social media and reviews displayed on your store.
- Testing certificates or cGMP documentation for manufactured products.
- Chargeback and refund history from your current processor for the past 12 months.
- Subscription terms and cancellation rates if you use recurring billing.
Getting underwritten for supplements
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite supplements. 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 supplements
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
A supplement store's data is dangerous to move by hand because compliance content lives in metafields. Batch numbers, testing certificates, ingredient sourcing notes and allergen flags are all reference or text metafields that a CSV export cannot carry — and if copied naively they keep pointing at files in the old store, so pages render but the compliance data is silently blank. On a regulated ingestible, that audit failure can trigger processor review even after onboarding.
| What you own | How much of it | What breaks doing it by hand | What we do instead |
|---|---|---|---|
| Product images | 1,250images≈ 5 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 | 250descriptions≈ 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 | 2,000variants≈ 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 | 3,000metafields≈ 20 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 | 433records≈ 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 | 15videos≈ 1 hrsre-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 | 8,000customers≈ 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 | 12,000orders≈ 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 | 4menus≈ 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 | 85discounts≈ 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 |
| Gift card balances | 200gift cardsno manual routecannot be moved by anyone | By handthis is the one thing on this page that truly cannot be moved by anyone. Gift card codes are unreadable through EVERY Shopify API, by design — no tool, ours included, can copy them. Those balances are real money you owe real customers, and abandoning the old store does not abandon the liability: the customers still turn up expecting you to honour it | Automatedwe re-issue each card with an identical balance, customer and expiry date, and hand you the new codes as a CSV with customer email copy ready to send — the only honest way to move them |
| Blogs & pages | 63articles & pages≈ 4 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 processing history. MATCH — the database processors use to screen high-risk merchants — follows the beneficial owner for five years, so opening a new company and applying again will flag the same decline reason. The only genuinely useful reason to form a new entity is to separate a compliant product line from a non-compliant one, but only if the entity structures are fully separate. Otherwise, save the cost and fix the claims.
Frequently asked
Will a new gateway turn my payments back on?
No. Your payments are off because a processor declined you, not because the gateway is wrong. A new gateway by itself does not fix the underlying reason — usually disease claims or a subscription refund dispute rate that is too high. You need an acquirer built for ingestibles, which means their underwriting focuses on your claims audit and your chargeback history, not a blanket refusal. The gateway you use is secondary. Find the acquirer first, then they will tell you which gateway to connect.
What reserve should I expect?
Most acquirers in this category hold 5–10% of your monthly volume in a rolling reserve, released 90–180 days after the transaction. The exact number depends on your volume, your chargeback rate and your supplier credentials. Larger orders and lower dispute rates get you to the lower end of that range. If you have a history of chargebacks or refunds from customers claiming the product did not work, expect the higher end or a longer hold period. Ask the acquirer upfront what they charge for this specific profile.
Do my product descriptions survive a store move?
Yes, if you migrate them correctly. The risk is that your claims descriptions — the exact language that triggers processor review — move with them word-for-word, and your new processor sees the same compliance problem the old one did. A migration is a good moment to audit every product page and rewrite disease claims as structure-and-function language. Do not just copy your old store. Use the move as a chance to fix the thing that got you declined in the first place.
What happens if I just rebrand and start over?
MATCH, the database processors use to screen merchants, follows the beneficial owner, not the company name. Opening a new store under a new business name with the same owner will flag the same decline reason. So you cannot evade an underwriting decision by rebranding. The only way forward is to fix the compliance problem — remove the claims, get the insurance and documentation — and apply to an acquirer who specializes in supplements with that profile fixed. It is slower, but it is the honest path.
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 →