Appealing a Shopify Payments decision, and you sell cannabis seeds. Migrate everything to a new Shopify store.
The decision came down by email, and the temptation is to write back immediately. Stop. Before you draft anything, you need to know what you are actually appealing — because Shopify Payments decisions split into two different categories, and only one of them can be reversed. If the decision turned on a fact — a mislabelled product, an unclear payment descriptor, a missing licence, or disputes you can now prove were fulfilled — then evidence can change the outcome. If the decision turned on your product category itself, then no reviewer has authority to except you from the processor's policy, and the appeal will fail no matter what you write. The difference matters because merchants who appeal the second kind waste weeks waiting for silence while their store runs on checkout alone, unable to plan around the real timeline. So diagnose first. Write second. Start plan B on the same day you appeal, not after.
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
- Email saying Shopify Payments cannot support your business, with no detail on which fact or category triggered the review
- Checkout still working for days or weeks after Payments deactivated, creating false hope that the problem might reverse itself
- Support responses repeating the same brief reason without elaborating on what specifically was found
- Requests to provide evidence met with 'appeal to Stripe' — passing the merchant to Shopify's processor without direct contact
- Radio silence lasting weeks after submitting an appeal, with no published timeline for a response
The checkout clock is a trap. It creates the impression you have time to appeal while payouts are actually frozen. The real deadline is the one Shopify does not advertise — when it decides whether to review your store a second time and close the whole account. That usually comes weeks in, which is why plan B must start immediately, not after the appeal fails.
Why it happened — specifically for cannabis seeds
Stripe, which underwrites Shopify Payments, lists cannabis and its derivatives as prohibited. Cannabis seeds fall into that category by association: even though seeds themselves contain no active cannabinoids, they are inherently intended for cultivation into a controlled substance. The secondary trigger is your jurisdiction. Some US states allow seed sales as collectibles or agricultural stock; others ban them outright. A processor reviewing your store sees the category risk first and your local legality second—or doesn't look at it at all.
Rule out the easy fix first — then deal with the real one
There is no documented Shopify route for cannabis seeds. What merchants typically try first is either hiding the category under 'botanical supplies' or applying to Shopify Payments and hoping the reviewer misses what you sell. Both fail. The honest path is that you need an acquirer who has explicitly chosen to underwrite seed banks—and that means going outside the Shopify Payments rails entirely to a third-party high-risk provider who can front you through Shopify using a standalone gateway integration. Those providers exist, but they are not hidden in a settings menu; you will need to contact them directly with your store details and jurisdiction, and they will run their own underwriting.
It only helps if all of these are true:
- You must operate in a jurisdiction where seed sales are explicitly legal or tolerated
- Your store must not imply or state that seeds are for human consumption
- You must be able to document the legality of your specific business in your specific location
- You cannot use Shopify Payments—you must connect a third-party high-risk gateway
- You must accept a substantially higher rate and a rolling reserve of 10–25% held 180+ days
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
⚖️ Legal status is genuinely contested or actively changing
Legal status that is contested or changing makes processors price legislative risk, not just chargeback risk. Shopify Payments may have disabled you not because of your compliance, but because the category itself is uncertain in law. An appeal based on 'it is legal in my jurisdiction' often fails because the processor avoids regulatory ambiguity entirely. Your appeal succeeds only if you can show the legal question has been definitively resolved in your favour by recent case law or statute. If the law is still genuinely contested, the processor will likely not reverse. Check the legal landscape first—if it is still moving, appeal is a formality. Start plan B immediately.
📦 Thousands of SKUs, deep variant matrices, distributor feeds
Thousands of SKUs across deep variant matrices make a hand-rebuild impractical, so migrating to a new processor must be automated. An appeal buys time only if that time lets you plan the technical migration properly. A successful appeal on product claims or compliance means nothing if you cannot execute the re-work at scale. Before you appeal, confirm you can migrate your catalog programmatically—via API, CSV with metafield support, or a migration service—and verify the target processor accepts your category. If the appeal fails and you have no migration path, the delay cost you more than it gained. Plan the infrastructure move before you submit the appeal.
What you actually have to fix
Underwriters do not change their minds because you asked. They change them because the facts changed. For cannabis seeds, these are the facts that move the decision:
Rewrite every product description to remove cultivation language and intent signals
This is the single highest-yield fix. Any text that frames seeds as inputs for growing cannabis—'ready to cultivate', 'yields', 'ideal for outdoor growing', 'high THC genetics'—signals to an underwriter that you are knowingly facilitating drug production. Reframe as collectibles, souvenirs, or breeding stock. Audit product names, variant labels, descriptions, blog posts, email templates and any customer-facing graphics. A reviewer will read everything.
Obtain written legal confirmation that your jurisdiction permits seed sales in your category
Most acquirers will not touch you without this. You need either state or local legislation that explicitly permits seed sales, a regulatory ruling from your state's agriculture or cannabis board, or a written opinion from a lawyer licensed in your jurisdiction confirming that your specific business model is legal. This is not optional—it is the document that separates a merchant with a legal business from one that is guessing. Email a copy to the acquirer before they even request it.
Verify your business is registered correctly and matches all legal paperwork
Use your legal name consistently across your business registration, tax ID, bank account, domain registrant information and store admin account. Mismatches flag you as a shell entity or a deliberate obfuscation, which kills underwriting. Check that your stated location matches where you are actually operating and selling. If you have moved or rebranded recently, document the chain of continuity so you are not mistaken for a fresh entity trying to evade history.
Document your customer verification and prevent high-risk patterns
Do not sell to addresses in states or countries where cannabis cultivation is prohibited. Implement age verification if your jurisdiction requires it. Monitor for bulk orders, reseller patterns or shipments to states with stricter laws—these trigger compliance reviews mid-relationship. Keep records of customer communications so you can show you made a good-faith effort to prevent misuse. An acquirer reviewing you six months in will look at your transaction patterns as proof that you are managing the category responsibly.
What underwriting will ask you for
- Articles of incorporation or business registration showing your legal entity name and formation date
- Proof of your jurisdiction's legality for seed sales—legislation, regulatory guidance, or attorney opinion letter specific to your state or country
- Your store's product descriptions and any marketing materials that detail how you describe the intended use of seeds
- Bank statements from the past 6 months showing transaction history and average monthly volume
- Copies of your terms of service and any customer agreements that disclaim responsibility for end-use
- Your processing history with any previous acquirer, including the reason for any termination
- Identity documents for all beneficial owners and signatories
Getting underwritten for cannabis seeds
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite cannabis seeds. 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 cannabis seeds
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
- Identify whether the decision turned on a fact or a categoryRead the email carefully. It will say something like 'cannot support' or 'incompatible with our policies'. The next step depends on which it is. If the decision mentioned a specific product, descriptor, licence, or type of dispute, then it may be a fact problem — and facts can change. If it mentioned your business type, industry, or product category as the reason, then no reviewer has authority to except you. Calling Shopify support at this stage usually produces the same email language again, so focus on diagnosis first.
- Gather the evidence for one written appeal — and do it todayThis is the step with a deadline you do not control. Do not wait for the appeal result. Do not assume checkout will keep working while you appeal. Collect the specific evidence that addresses the decision: corrected product screenshots, updated payment descriptors, licence documents, fulfilment records, customer consent, delivery proof. File them all in one place so you can reference them in writing. Set a deadline for the appeal to arrive with Shopify within 48 hours — not because speed guarantees anything, but because waiting is a sunk cost that keeps you from building plan B.
- Appeal once in writing, with only the evidence that counters the decisionWrite directly to the email address that notified you. Be specific: 'You cited [reason]. Here is the evidence that [corrected fact].' Attach or link the documents. Do not argue that the decision is unfair, do not ask for another review, do not promise future compliance. Processors see hundreds of these, and generic appeals are routed as low-priority. You are simply putting the fact on record. If the decision was based on a category prohibition rather than a fact, say so in your diagnostic email to yourself and move on.
- Start plan B the same day: migrate to an accepting gatewayDo not treat the appeal as your plan. Treat it as something you put in motion and then ignore while building what actually survives. A new store on a different payment processor — built into a fresh Shopify domain or migrated into one — with a provider that underwrites your category is the real recovery. The migration takes days, costs a fixed price, and runs in parallel to your appeal. Many merchants never hear back from the appeal. Those who moved the same week have zero downtime in the one business metric that matters: can they take payment.
- If the appeal succeeds, shut down the new store or keep it running dual-processorSuccess is rare and usually takes weeks. If it comes, you will be notified that Shopify Payments is re-enabled. At that point you have a choice: move back to Payments and deactivate the other gateway, keep both running, or stay on the new processor. Dual processing costs more but insures against a second deactivation. Many merchants who have been through this once choose to stay dual, or to stay with the accepting gateway entirely, because the reputational cost of promising customers they can take payment and then freezing is higher than the processing fee difference. That is a business call you make once you are not in crisis mode.
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 seed bank's data breaks in a very specific way during a manual migration: the genetics matrix. Cannabis seeds are sold in deep variant structures—dozens of strains crossed with auto-flower vs. photoperiod timing, male vs. female, seed count per pack—and these relationships live in metafields, not in standard Shopify variant naming. When you move by hand or via CSV, metafield connections snap silently. A customer looking for 'feminized auto-flower Northern Lights' sees the products exist but the filtering logic is broken. On a catalog-heavy site this creates cascading returns and support work. Automated migration re-links them correctly.
| What you own | How much of it | What breaks doing it by hand | What we do instead |
|---|---|---|---|
| Product images | 5,200images≈ 22 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 | 650descriptions≈ 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 | 11,700variants≈ 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 | 9,100metafields≈ 61 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 | 1,072records≈ 7 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 | 8,400customers≈ 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 | 19,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 | 52discounts≈ 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 | 42articles & 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 does not reset your underwriting history. If your seed business has previously been declined or terminated by a processor, the beneficial owners behind it will be flagged under MATCH for five years, regardless of whether you incorporate under a new name. Underwriters will find the connection. Your best move is not a new company—it is finding an acquirer who accepts seed merchants and being transparent about your history from the start.
Frequently asked
Can I use Shopify Payments for a seed bank?
No. Stripe, which powers Shopify Payments, prohibits cannabis and cannabis-related products, and seeds fall under that category. You must use a third-party gateway provider who specializes in high-risk businesses and explicitly accepts seed merchants. This requires a separate merchant account with that acquirer and integration into Shopify via a standalone gateway, not Shopify Payments. The setup is straightforward but it is not a checkbox—you have to apply and be approved.
Which gateway should I connect?
Multiple acquirers publicly advertise cannabis seed merchants, including Bankful, DigiPay, PaymentCloud, Corepay, Easy Pay Direct and Durango, among others. Each has different underwriting, rates and reserve terms. Rather than cold-email a dozen providers, we maintain a live referral form on this page—fill it with your store details and jurisdiction, and qualified providers will contact you directly. This cuts months of back-and-forth rejection.
What happens to my existing orders and customer list during a migration?
Order history and customer data can be fully migrated to your new store. Your payment processing history does not move—your new acquirer will have no record of your old transactions. This is actually useful: you are starting your underwriting relationship with a processor who has chosen to accept seed merchants, rather than carrying a decline notice forward. Your customer list remains yours to use for reactivation email and retargeting.
Will my product variants and genetics data survive the move?
Standard product data—names, descriptions, prices, images—transfers cleanly. But if your strain genetics, cannabinoid profiles, growing characteristics or breeding notes live in metafields, a hand migration or CSV export loses them. Automated migration captures metafields correctly. That is why a seed bank catalog move is higher-risk than a standard ecommerce move: a broken genetics matrix means lost filtering, broken search and a degraded browsing experience for customers. We run the migration twice and compare counts to catch it.
Can Shopify Payments be turned back on if I appeal?
Only if the decision was based on a fact — a mislabelled product, unclear descriptor, missing licence, or disputed orders you can now prove were fulfilled. If the decision turned on your category being on the processor's prohibited list, then no reviewer has authority to make an exception, and the appeal will not change it. The decision tells you which it is if you read it carefully.
How long does an appeal take?
There is no published SLA. Merchants commonly report anywhere from a few weeks to no response at all. Some receive a yes or no answer; others receive the same generic reason again without elaboration. The lack of transparency is why you should not wait for the result before building a backup plan. Filing the appeal and then moving to a different processor in parallel is the only timeline you control.
What evidence actually works in an appeal?
Evidence that addresses the specific decision, not the general principle. If you were rejected for mislabelled product names, show the corrected listings. If for unclear payment descriptors, show what the new descriptor is. If for missing licences, provide the document. If for disputed orders, provide proof of fulfilment — tracking, delivery signature, or customer communication proving the goods were as described. Generic promises to comply do not work because the processor's decision was based on documented risk, not intent.
What if Shopify Payments is re-enabled but then disabled again?
This pattern is common. Merchants report being re-enabled, trading for a few weeks, and then receiving a second deactivation notice. If this happens to you, the underlying decision was likely not actually overturned — it was suspended pending more observation. This is why having a backup payment processor in place before the first appeal is worth the setup cost. You are no longer betting the business on a single gateway.
If I move to a different processor, do I have to close my Shopify store?
No. Your store stays live. You simply connect a different gateway for payments — Stripe, Square, PayPal, Braintree, or another processor that underwrites your category. The store itself, your catalog, your customers, and your orders are unaffected. If your new processor later deactivates you as well, migration to a third processor is the same move again. The goal is to find a gateway whose underwriting actually fits your business model and stick with it.
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 →