Rolling reserve imposed, and you sell cigars and tobacco. 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 cigars and tobacco
Stripe's policy treats tobacco as a restricted business, which means Shopify Payments cannot process it without a specialist underwriter. The primary trigger is the category itself — cigars and pipe tobacco sit on Stripe's restricted list, and a merchant flagged as tobacco will be declined by the default processor. The secondary trigger is undocumented age verification: if your checkout does not prove the customer is of legal age, even a licensed merchant will be declined on the grounds of insufficient controls.
Rule out the easy fix first — then deal with the real one
Shopify does not document a route for tobacco, and the reason is straightforward: there is no single pathway that works everywhere. What merchants typically try first is applying directly to Shopify Payments, which fails because Stripe's underwriting team will see the MCC before any other detail. The honest move is to skip that application and go straight to a specialist acquirer who underwrites tobacco accounts on purpose. They exist, they know what paperwork to expect, and they are faster than trying to convince a generalist processor that your case is an exception.
It only helps if all of these are true:
- Your business must hold a state tobacco license and be registered to collect excise tax.
- You must have documented, compliant age verification at checkout — not just a checkbox.
- Your store cannot display or sell to jurisdictions where tobacco sales are prohibited or restricted.
- You must keep current copies of all required state and federal filings.
- Your merchant processing history cannot show prior chargebacks or disputes related to age-restricted sales.
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
🔞 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.
💎 High average order value, so fraud and disputes cost more per event
A reserve on high-ticket orders hurts immediately because a single dispute or chargeback is material to your cash position. Your reserve size is typically sized to cover estimated future dispute exposure, so one large chargeback can push it upwards. Processors also review single-order fraud patterns more closely at high AOV, so provide evidence of your verification process—address matching, velocity checks, customer contact protocols—before the reserve discussion. Clean processing history over at least 90 days demonstrably reduces both reserve size and duration; that is negotiable leverage that most high-AOV merchants underuse.
📦 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 cigars and tobacco, these are the facts that move the decision:
Obtain and file your state tobacco dealer's license
This is the single highest-yield fix, and it is the one document that changes a specialist acquirer's assessment of your application from 'risky' to 'legitimate business'. Most tobacco merchants already have this paperwork because they sell in person or through other channels. If you do not have it, your state's revenue or health department can advise on requirements. An acquirer will ask for a copy certified within the last 12 months. Without it, you will not pass underwriting, regardless of your other documentation.
Implement mandatory age verification at checkout
Your checkout must prove the customer is of legal age before payment is taken. A simple checkbox is not sufficient — you need a documented process such as third-party age verification, ID number capture, or date-of-birth confirmation tied to a validation service. Document your method in writing and be ready to show the acquirer exactly how it works. This is the second-highest-leverage fix because it addresses the specific concern that drove you to restricted status in the first place.
Compile a complete processing history from all prior accounts
If you have processed tobacco sales anywhere else — even a small amount — get statements, chargeback reports and processor documentation from every account you have used. Specialist acquirers want to see that you have not been repeatedly declined or terminated for age-verification failures or fraud. A clean history on a prior account is a strong underwriting signal. If you have had accounts closed, be transparent about why and what you have fixed since then.
Write a clear product and business description for the underwriter
In your application narrative, explain what you sell, how long you have been selling it, what your average order value is, and whether you sell online only or also in a physical location. Tobacco merchants with established retail operations and clear business longevity are treated as lower risk. If you are new online but established offline, say so explicitly. The underwriter is trying to distinguish between a genuine business and a front, and boring operational detail is reassuring to them.
What underwriting will ask you for
- Current state tobacco dealer's license or equivalent state registration document
- Proof of federal excise tax registration and compliance
- Bank statements for the last 3–6 months showing tobacco-related revenue
- Written age-verification methodology describing your checkout controls
- Product list or catalog showing SKUs, descriptions and price points for your top 20 items by revenue
- Ownership and beneficial-ownership documentation for all principals
- Processing history from any previous payment processor, if applicable
Getting underwritten for cigars and tobacco
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite cigars and tobacco. 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 cigars and tobacco
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 tobacco store's catalog is dangerous to move by hand because age-verification and compliance metadata live in metafields and custom objects. Restricted-product flags, age-gate rules, state-specific visibility toggles and excise-tax calculations are all stored as reference or boolean metafields that a CSV export cannot carry. If those fields are copied naively, they keep pointing at the old store's data or are silently lost, leaving products visible to minors or lacking required tax data. On a regulated product category, that failure is not cosmetic — it is a compliance breach.
| What you own | How much of it | What breaks doing it by hand | What we do instead |
|---|---|---|---|
| Product images | 5,100images≈ 21 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 | 850descriptions≈ 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,550variants≈ 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 | 6,800metafields≈ 45 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,193records≈ 5 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 | 2,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 | 4,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 | 65discounts≈ 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 | 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 | 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?
You do not need a new legal entity to apply for specialist merchant processing. A new LLC or corporation will not reset your payment history or change an underwriter's view of your compliance posture. What matters is your state tobacco license, your excise documentation and your age-verification controls — those are tied to the business, not the corporate form. If you have been declined once, a new entity does not erase that decline from the processor's memory.
Frequently asked
Which payment gateway will actually take a cigar and tobacco store?
Several high-risk acquirers publicly advertise tobacco underwriting, and they route through gateways Shopify supports natively. Authorize.net on a high-risk merchant ID, PaymentCloud, Corepay and Easy Pay Direct all have tobacco experience. Specialist ISOs focused on nicotine and tobacco are also an option. The gateway is rarely the constraint — the merchant account is. What matters is whether the acquirer's underwriting team believes your age-verification controls and your compliance posture are genuine, not which payment button you use.
Why was I declined if I already have a state tobacco license?
A state license proves you are a legal business, but it does not prove you are a low-risk payment processor's problem. The acquirer is looking for three things: documented age verification at checkout, a clean processing history, and evidence that you understand and comply with the excise-tax obligations in your states. If your prior account was closed for chargebacks or disputes, or if your checkout is a simple clickthrough without age gating, the underwriter will decline you even if your license is current. Fix the verification and reapply with a complete compliance narrative.
Will my product data survive a store migration to a new processor?
Not automatically, and not the compliance-critical parts. Your product-level age gates, state restrictions, excise-tax flags and reserve-calculation rules live in metafields that Shopify's native CSV export cannot carry at all. If you move stores by hand using CSV, those data points are lost, and your new store will sell your restricted products without age verification. A proper migration tool that reads the Shopify GraphQL API can carry metafields forward, but CSV alone cannot. Test the migration on a staging store before going live.
What reserve should I expect, and for how long?
Specialist tobacco acquirers typically hold a rolling reserve of 5–10 per cent of your monthly volume, held for 90–180 days depending on your processing history and chargeback rate. Some acquirers release the reserve in tranches as your history improves; others hold it for the full term and release it all at once. Ask the acquirer explicitly how their reserve schedule works before you sign, because it directly affects your cash flow. A new account with no prior tobacco processing history is more likely to face the higher end of that range.
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 →