Rolling reserve imposed, and you sell cannabis seeds. Migrate everything to a new Shopify store.
The payout landed, but only part of it. A percentage of your revenue is being held in a rolling reserve — money that belongs to you, but that Shopify Payments controls for 90, 120 or sometimes 180 days before it releases. The email or dashboard note uses the word 'review' or 'risk assessment', which reads like punishment. It is not. A reserve is how payment processors collateralise the disputes they know are coming. Chargebacks, refunds, fraud claims — they all pull from this pool before your account goes negative. Shopify Payments is underwritten by Stripe, and Stripe treats a reserve as a condition of continuing to process at all, not a temporary penalty. The useful news: reserves are negotiable downwards over time. A merchant with months of clean processing history, low dispute rates and stable revenue can make a case to reduce both the percentage held and the rolling period. That conversation does not happen by itself, but it does happen.
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
- "A rolling reserve has been applied to your account for risk management purposes" — with no percentage or end date named
- Payouts that are visibly smaller than your actual sales, week on week, for weeks or months
- Dashboard showing held funds in a separate reserve account, growing faster than it drains
- Support responses that treat the reserve as non-negotiable and permanent
- Gaps in cash flow that make it hard to re-stock or pay contractors, even though the underlying sales were real
The payout clock matters more than the checkout clock here, but it is a slow clock. You have time to work this deliberately. The real danger is treating a reserve as permanent and unchangeable, then panicking into a bad decision — switching gateways, or worse, abandoning the business entirely. Most rolling reserves are negotiable downwards within months of clean processing.
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
A reserve on legally contested goods reflects that legislative risk is priced separately from chargeback risk. The processor is protecting themselves against category-level legal change, not just individual transaction disputes. Your reserve duration may be longer than a merchant in an established category faces, even with identical chargeback rates. The useful truth: reserves are genuinely negotiable downwards over time with clean processing history. A merchant who can show 12 months of zero compliance flags and zero disputes often negotiates a material reduction. That matters more for legally volatile categories, where the processor's risk pricing is higher to begin with.
📦 Thousands of SKUs, deep variant matrices, distributor feeds
A reserve on a large catalog poses a distinct problem: your reserve is typically calculated on aggregate dispute rate across all SKUs, but a handful of problem products may be driving processor concern. If your catalog is thousands of items with distributor feeds or variant matrices, isolating the problem SKUs takes time you do not have while cash is tied up. Processors want to see that you actively monitor product performance and customer feedback, not just volume. Provide them with your top 50 SKUs by volume and their dispute rates separately if possible. Demonstrating SKU-level governance and willingness to remove repeat problem items can accelerate reserve negotiation faster than overall volume growth.
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
- Understand what percentage and rolling period applyLog in to your Shopify admin and find the reserve details under Payments. Note the exact percentage held, the rolling period (typically 90, 120 or 180 days), and any stated review date. Write this down. You will need these numbers to track your release schedule and to make a case for reduction later. If the dashboard does not show a clear end date, contact Shopify Support and ask for clarity — they may have it even if the interface does not display it.
- Pull a verified copy of your store while you still have accessA reserve is a cash-flow problem, not (yet) an access problem. But the sequence matters. Get your store backed up now while you can still log in. This means exporting your product catalog, customer list, order history and consent records — everything Shopify's CSV export reaches. Note that Shopify's export cannot carry metafields, videos, your theme, menus, discounts, redirects or gift card codes, so this is a partial backup at best. But it is vastly better than nothing. If the reserve triggers a full account review later, access can be yanked, and an unreachable catalog is a dead business.
- Document your processing history and dispute ratesReserves are negotiable if you can show Stripe that your dispute and chargeback rates are low, your refund patterns are normal, and your order velocity is stable. Start gathering this data now. Run a report on your disputes and chargebacks from the last 90 days. Compare your refund rate to your sales volume. Check your customer satisfaction metrics if you have them. This is the evidence you will present when you ask for the reserve to be lowered.
- Request a re-evaluation of your reserve termsAfter you have 60–90 days of clean processing history, contact Shopify Support and ask them to escalate your account for a reserve review. Be specific: state your current dispute and chargeback rates, your refund practices, and the stability of your processing. Reserves are a standard tool, not a punishment, but they are also negotiable. Stripe lowers both the percentage held and the rolling period for merchants who demonstrate they are low-risk. A request framed as a re-evaluation is more likely to get traction than one that frames the reserve as unfair.
- If the reserve does not budge, plan a gateway migrationA rolling reserve is a working business problem, not a business-ending one. But if it stays locked at a level that breaks your cash flow, and re-evaluation goes nowhere, you have the option to migrate to a different payment processor. Choose a gateway that accepts your product category and has underwriting criteria that fit your actual business. Migration is not a punishment-evasion move; it is moving from misfit underwriting to fit underwriting. Be prepared to disclose your full history — Stripe's data will appear in any new underwriting review, and honesty about why you moved will serve you better than pretending the reserve never happened.
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.
Why is Shopify holding a percentage of my payouts?
Because Shopify Payments is underwritten by Stripe, and Stripe uses a rolling reserve to collateralise the disputes and chargebacks it knows are statistically coming. It is not a punishment or a temporary hold pending review. It is a condition of the merchant account itself. The reserve amount depends on Stripe's assessment of your risk profile — category, processing history, dispute rates and order velocity all feed into it.
What percentage is normal, and how long will it last?
Industry norms are 5–10% rolling over 90–180 days. Stripe may impose 20–25% on a merchant where risk signals are higher — lower sales history, newer business, higher dispute rates. If Stripe suspects illegitimate commerce, reserves can extend to 365 days. The exact terms are set individually based on underwriting, and there is no single 'normal' that applies to every store.
Can I appeal the reserve or get it removed immediately?
No. A reserve is not a violation or suspension; it is an underwriting condition. You cannot appeal it as if it were a mistake. What you can do is make a case for reduction based on processing performance. After 60–90 days of clean processing — low disputes, normal refund patterns, stable order velocity — you can ask Shopify to re-evaluate the reserve downwards. Stripe does lower both the percentage and the rolling period for merchants who demonstrate they are low-risk.
My cash flow is broken. Can I move to a different payment processor?
Yes. A rolling reserve is a cash-flow problem, not a contract lock. If your current reserve breaks your ability to operate, you can migrate your store to a different payment processor with different underwriting terms. Choose a gateway that publicly advertises acceptance of your product category. Be prepared to disclose your history truthfully — any new processor will see your Stripe data during underwriting, and honesty about why you migrated will be more persuasive than silence.
Will the reserve stay on my account forever?
Not if your processing stays clean. Reserves are negotiable downwards with consistent low dispute rates and stable processing history. Merchants commonly see their reserves reduced — either the percentage held, or the rolling period, or both — within months of demonstrating they are low-risk. This is genuinely useful news: you are not stuck with the initial reserve permanently. The conversation requires documentation and patience, but it does happen.
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 →