Rolling reserve imposed, and you sell delta-8 and THCA products. 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 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
A reserve means your cash flow stops for the duration, and for anything consumed or applied, dispute rates are the primary driver. Processors are protecting themselves against claims that products did not work or caused harm. Your reserve size and length correlate directly to your chargeback history and the strength of your product claims. Before approaching a new acquirer, audit your product pages: any claim that could be read as a drug claim, a disease claim, or a cure will spike the reserve. Get documentation—certificates of analysis, third-party testing, ingredient sourcing—into a format a processor can review in minutes, not days.
⚖️ 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.
🔞 Requires age verification, and shipping is regulated in its own right
A reserve with age-restricted goods hits shipping costs first. Carrier rules and adult-signature protocols already limit your margin, and a reserve on top of that compresses working capital further. Processors reserve against age-verification failures and mis-shipment disputes. Your documentation of age-checking process—what you capture, how you verify, how you flag failed checks—matters more than most merchants realise. Some carriers also require proof of age compliance before they will insure shipments, so a clean verification audit helps negotiate the reserve down faster than volume alone.
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
- 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
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.
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 →