Rolling reserve imposed, and you sell nicotine pouches. 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 nicotine pouches
Shopify Payments is underwritten by Stripe, which lists nicotine products—including tobacco-free pouches—on its restricted businesses policy. The primary trigger is the product category itself: any pouch marketed as delivering nicotine is classified as a tobacco or nicotine product regardless of botanical origin. The secondary trigger is your business model. Subscription merchants are flagged more aggressively because recurring charges on age-restricted products create chargeback and fraud risk that makes processors nervous. A one-time sale can sometimes slip through; a subscription almost never does.
Rule out the easy fix first — then deal with the real one
There is no Shopify-documented route for nicotine pouches, so rule this out first. What merchants try is connecting a high-risk payment gateway and hoping the underwriting is simpler than Shopify's. It usually is not. You will still face a tobacco or nicotine merchant account application with the same underwriting questions: age verification proof, subscription billing documentation, shipping compliance in your target countries, and chargeback history. The difference is that Shopify Payments will decline you outright, while a high-risk acquirer will consider you—but that consideration is not an approval, and the gateway itself is not the bottleneck. The merchant account behind it is.
It only helps if all of these are true:
- You must prove age-gating technology is live on checkout and product pages.
- Your subscription terms must clearly state the customer's age requirement and cancellation rights.
- You must document shipping restrictions by country and your compliance checks.
- Your processor must be a high-risk acquirer; most mainstream gateways will not even quote you.
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.
🔁 Recurring billing is a large share of revenue
A reserve starves a subscription business in two ways. New recurring orders are slower to settle, and cash flow from the existing subscriber base becomes uncertain. Your reserves are calculated on forward-looking billing: if a processor estimates you will bill 10,000 subscribers next month, they reserve against the disputes that history suggests will come. The reserve duration is the same pain: if it runs 120 or 180 days, your cash from the same billing cycle does not return for months. Prove clean chargeback behaviour over the longest period the processor will review; even small improvements in dispute rate accelerate reserve negotiation.
What you actually have to fix
Underwriters do not change their minds because you asked. They change them because the facts changed. For nicotine pouches, these are the facts that move the decision:
Implement age-gating on every product and at checkout
This is the single highest-yield fix. Every processor will ask for proof that you cannot sell to anyone under your target age—usually 18 or 21. Static text that says 'Must be 18+' is not enough. You need a live age gate: a checkbox the customer actively confirms, or better yet, a third-party age-verification service integrated into your checkout and attached to product pages. Document that service in screenshots and include the provider's name and verification method in your underwriting package.
Write clear subscription terms and obtain explicit consent
Subscription is a red flag by itself because of recurring-charge chargebacks. Write out your subscription terms in plain language: the frequency, price, cancellation mechanism and the customer's affirmative consent to being charged on that schedule. Many acquirers will ask for email evidence of customer opt-in or a recorded consent call for high-value subscriptions. Have this ready before you apply, not after.
Document your shipping and country compliance
Nicotine pouches face outright bans or heavy restriction in several countries and US territories. Build a shipping policy that lists every country you will and will not ship to, and explain why (legal ban, local customs restriction, or internal business decision). Then prove you enforce it: show how your store blocks checkout or requires additional verification for restricted regions. Acquirers will ask for this; having it ready shortens the underwriting cycle.
Gather your processing history or financial projections
If you have processed with another merchant account before—even if it was closed—bring the statements, chargeback reports and closure reason. Acquirers will check MATCH and see it anyway. If you are new, bring a realistic volume projection, your marketing spend plan and evidence of customer acquisition (email lists, social following, pre-launch signups). This is not about proving you will be huge; it is about showing you have thought through unit economics and compliance.
What underwriting will ask you for
- Proof of age-verification system (screenshots of your checkout and product-page gates)
- Subscription billing agreement and customer terms of service
- Product COA or specification sheet (nicotine content, origin, non-tobacco certification if applicable)
- Processing history from your previous merchant account or statement of volume projections
- Shipping policy showing country-by-country restrictions and how you enforce them
Getting underwritten for nicotine pouches
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite nicotine pouches. 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 nicotine pouches
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
Nicotine stores are dangerous to move by hand because subscription data lives partly in Shopify's subscription system and partly in metafields. Billing cycles, pause dates, customer consent records and dunning logic all exist in the subscription table, not as CSV; Shopify's CSV export cannot touch any of it. If you move by hand, you will copy the product and order history, but every active subscription becomes orphaned—the customer keeps paying the old store and never receives product, or the charges simply stop. For a category where recurring revenue is the model, a failed subscription migration is a financial crisis, not an inconvenience.
| What you own | How much of it | What breaks doing it by hand | What we do instead |
|---|---|---|---|
| Product images | 600images≈ 3 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 | 150descriptions≈ 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 | 450variants≈ 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 | 900metafields≈ 6 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 | 215records≈ 2 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 | 8videos≈ 32 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,800customers≈ 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,500orders≈ 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 | 22discounts≈ 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 | 20articles & pages≈ 1 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 | 8apps≈ 8 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 reset a MATCH listing, so opening a second company does not erase the decline. That said, you do not strictly need a new entity to move processors. If your current entity has never processed nicotine before, and your previous processor declined you for a different category entirely, a high-risk acquirer may treat that as a clean slate. But if your entity is already on MATCH for nicotine, a new company is a delay tactic, not a solution. The honest move is to fix the compliance gaps on the entity that exists.
Frequently asked
Can I keep my current store and just switch payment processors?
No. Shopify Payments cannot process nicotine products at all, so you cannot stay on the same Shopify store and solve this with a gateway swap. You must migrate to a new Shopify store with a high-risk merchant account and a supported gateway. The new store is where you run your real business going forward. The old store becomes read-only or is shut down once customers and data have moved.
Which payment gateway will actually accept me?
Authorize.net offers high-risk merchant accounts and will quote nicotine merchants, as will specialist high-risk ISOs and acquirers such as PaymentCloud, Corepay and Easy Pay Direct. But 'will quote' is not 'will approve'. Each has its own underwriting criteria: age-verification proof, chargeback history, country restrictions and subscription terms. Rather than cold-email a dozen providers, use the acquirer network on this page or a high-risk payment broker familiar with nicotine.
Will my subscription data survive a store migration?
Only if you migrate it correctly. Shopify's CSV export does not include active subscriptions, billing cycles, pause dates or customer consent records. You must use Shopify's subscription API or a migration partner with subscription support to carry that data over. If you move by hand, every active subscription will break—customers will either keep being charged to the old store or charges will stop entirely. For a subscription business, that is a crisis.
What reserve should I expect on a nicotine merchant account?
Most high-risk acquirers hold 10–20% of your monthly volume in a rolling reserve for 90–180 days. This is not a penalty; it is standard for any restricted category with chargeback or age-verification risk. That means if your monthly volume is £10,000, you might see £1,000–2,000 held back from each month's settlement, released gradually over three to six months. Plan your cash flow around this and confirm the reserve terms before signing the underwriting agreement.
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 →