Rolling reserve imposed, and you sell firearms accessories. 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 firearms accessories
Shopify Payments is underwritten by Stripe, and Stripe's policy on firearms and firearms parts is categorical: the business is restricted, and within that restriction certain items—magazines above state capacity limits, components that function as receivers, and parts marketed for assembly—live in a prohibited subcategory. The secondary trigger is guilt by association. A processor reviewing your store sees magazines, optics and holsters together. They do not separate the low-risk items from the high-risk ones; they see a firearms merchant and apply the blanket policy, so your compliant optics get caught by the same decline as your restricted magazines.
Rule out the easy fix first — then deal with the real one
Shopify does not document a route for this category. There is no attestation, no third-party integration and no declared path. What merchants try first is applying directly to Stripe or Shopify with a letter explaining that most of their catalog is legal and shippable. This fails because Stripe's policy is not a review process—it is a category exclusion. An individual appeal rarely changes it. Your alternative is moving to an acquirer that underwrites firearms accessories as a vertical: they run the compliance separately and accept case-by-case, so your store is judged on what you actually sell, not on category proximity. This requires moving payment gateways and, usually, payment processors entirely.
It only helps if all of these are true:
- No documented Shopify route exists; you must change processors.
- An alternative processor's underwriting team must approve your product list before you apply.
- Your store must geo-block any item prohibited in the customer's shipping state.
- You must carry insurance and licenses where your jurisdiction requires them for the items you sell.
- Magazine capacity limits and receiver components must be removed or fully compliant with state law.
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
🎯 Weapons or weapon-adjacent, with state-by-state legality
A reserve on weapons or weapon-adjacent goods reflects state-by-state legality risk, not just chargeback rate. Processors price legislative risk alongside transaction risk, so your reserve duration and size depend partly on whether your category faces active legal change. The reserve is negotiable downwards over time with clean processing history, and that genuinely matters: a merchant with two years of zero disputes and no compliance flags can often get it reduced significantly. Document your geo-blocking logic, your compliance checks at order time, and your relationship with any distributor or regulatory body in your category.
📦 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.
💎 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.
What you actually have to fix
Underwriters do not change their minds because you asked. They change them because the facts changed. For firearms accessories, these are the facts that move the decision:
Map and geo-block every restricted SKU by state.
This is the single move that makes most firearms accessory stores fundable. Magazines above state capacity limits, certain receiver blanks and binary triggers are prohibited in specific states. You must identify every restricted item, look up the laws in your top 20 shipping states, and then configure Shopify to block checkout for those postcodes. A processor reviewing your store will ask for proof—screenshots of your checkout rule or a technical report showing which postcodes see which products. This is not optional; it is the foundation of your compliance.
Audit every product description for assembly and manufacturing language.
Parts sold as 'components to complete your build' or 'lower receiver blanks' trigger prohibited status even if the item itself is legal. A processor reads 'assemble' and sees you as selling a way around dealer licensing. Rewrite descriptions to be functionally accurate but never suggest assembly, manufacturing or circumventing requirements. 'Precision-machined component' is defensible; 'everything you need to finish your lower' is not. Check your email campaigns and social media too; a single post advertising 'build your own' can sink an underwriting application.
Gather proof of insurance and licensure.
Your underwriting file must include commercial general liability insurance naming firearms product risk, and copies of any federal firearms licenses (FFL), business licenses or state permits you hold. If you do not hold the licenses you should hold—if you are selling components that require dealer licensing but you do not have one—state that plainly and remove those SKUs. An underwriter will find out. It is better to disclose it yourself and prove you have complied than to let them discover it in a chargeback dispute eighteen months from now.
Document your distributor feeds and dropship terms.
Firearms accessory merchants often work with distributors and dropshippers. Pull your contracts and confirm they allow retail resale and that they specify your compliance obligations—particularly around magazines and restricted components. Some distributors will not ship certain items to certain states; you must know this and map it into your geo-blocking. List your top 3–5 suppliers and their restrictions in your underwriting submission. Transparency here signals you are running the category seriously, not as a side venture.
What underwriting will ask you for
- Product catalog with full SKU descriptions, including whether each item requires a license or permit in your key shipping states
- Magazine inventory list with state-by-state capacity limits and geo-blocking proof for each SKU
- Proof of insurance covering product liability for firearms accessories
- Certificate of occupancy or business lease showing your retail or warehouse location
- Shipping and handling policy clearly stating which items are not shipped to certain states
- Bank statements for the last 12 months showing transaction volume and frequency
- Copies of all advertising, email and social media campaigns mentioning firearms, weapons or calibers
Getting underwritten for firearms accessories
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite firearms accessories. 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 firearms accessories
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 firearms accessories store's data is dangerous to move because fitment metadata lives in custom metafields. Compatibility data—which optics fit which rail systems, which holsters fit which firearms, which magazines are compliant in which states—is stored as reference fields, lookup fields or text metafields that a CSV export cannot carry. Shopify's standard export also cannot carry metafield data at all. If you move by hand or naive export, every product page renders but the fitment filters and state-compliance logic silently break, so a customer selects a holster for the wrong firearm and you process a return and a chargeback. On a high-AOV category, that is not trivial.
| What you own | How much of it | What breaks doing it by hand | What we do instead |
|---|---|---|---|
| Product images | 7,200images≈ 30 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 | 1,200descriptions≈ 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 | 9,600variants≈ 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 | 14,400metafields≈ 96 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,643records≈ 6 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 | 45videos≈ 3 hrsre-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,500customers≈ 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,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 | 95discounts≈ 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 | 103articles & pages≈ 7 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 does not help you here. A firearms accessories merchant who has been declined by Stripe carries that history as a person and as a business, and a processor running standard MATCH checks will see it regardless of whether you form a new LLC. If your original store's account was terminated for selling restricted items, a new company with the same person controlling it signals restructuring to avoid compliance, which underwriters treat as higher risk, not lower. The move is fixing the catalog and the claims, then applying to a different processor under your honest business history.
Frequently asked
Which payment gateway will take a firearms accessories store?
The gateway is not the constraint—the merchant account behind it is. Several high-risk acquirers publicly underwrite firearms accessories, and they can front them through Authorize.net, Stripe-alikes and bespoke integrations. What will take you depends on your specific catalog mix, whether you sell magazines and components, your volume and your processing history. Rather than cold-email a dozen ISOs, use the underwriting request form on this page and let brokers who specialize in 2A commerce bid for your business.
What reserve should I expect to carry?
Most firearms accessories merchants report a 5–10% rolling reserve held for 90–180 days. This means if you process £100,000 in a month, £5,000–£10,000 sits in your processor's account and is released in tranches. Some processors tie it to chargeback rates or customer complaints, so if your first 90 days are clean, they may reduce it. Budget for cash flow around this; it is not a penalty, it is standard risk management in high-AOV categories with regulatory complexity.
Will my fitment data and geo-blocking survive a store migration?
No, not through Shopify's standard export. Fitment rules, state-compliance logic and custom metafields are invisible to CSV round-trips. If you migrate to a new Shopify store without a specialized tool, every product copies but the filtering and blocking rules do not, so customers can order incompatible items or prohibited SKUs. Our migration service rebuilds this metadata by interrogating your original store's API and the Shopify metafield layer, then re-applies it in the new store. Standard exports will lose it entirely.
Do I need a new legal entity to apply to a different processor?
No. A new LLC does not reset your payment history or your MATCH listing; a processor running standard checks will see you as the controller of both entities. If your original Shopify Payments account was declined for selling restricted items, applying again with a new company does not solve the problem—it signals you are trying to avoid compliance scrutiny. The fix is changing your catalog and your claims, then applying to a processor that underwrites 2A commerce case-by-case, which they will under your honest business history.
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 →