Rolling reserve imposed, and you sell airsoft and airguns. 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 airsoft and airguns
Stripe, which underwrites Shopify Payments, places airsoft and replica firearms on its restricted-businesses list. The primary trigger is appearance: reviewers classify by how realistic the replica looks, not by legality in your jurisdiction. A two-tone airsoft rifle that is legal to sell may still be flagged as a weapon. The secondary trigger is age controls—if your store does not visibly gate age-restricted products or track buyer age at checkout, you signal to a reviewer that minors can buy without friction, which moves you from restricted to high-risk decline.
Rule out the easy fix first — then deal with the real one
Shopify does not document a specific route for airsoft and replica firearms, which means you cannot apply through the platform attestation model. What most merchants try first is connecting a high-risk processor directly to Shopify through Authorize.net on a high-risk merchant ID, or using a standalone gateway like PaymentCloud or Soar Payments. That usually works—these providers do underwrite airsoft—but it requires you to demonstrate age controls at the product and checkout level, realistic product photography that shows the orange tip or two-tone marking clearly, and clean chargeback history. If your prior processing account was closed for disputes, that fact travels with you and a new acquirer will see it during underwriting.
It only helps if all of these are true:
- Your store must gate age-restricted products behind a verified-age wall at checkout.
- Product photos and descriptions must show safety markings clearly—orange tips, two-tone finish, or any legal marking.
- Chargeback rate must be under the processor's threshold, typically 1% or lower.
- You must be able to provide processing history and any prior account closures to the new acquirer.
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.
🔞 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.
📦 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 airsoft and airguns, these are the facts that move the decision:
Build a visible age gate into every restricted product.
This is the single highest-yield fix. Your store must ask for and verify age before a customer can add a replica firearm to their cart or view the product. A checkbox that says 'I am 18' is not enough; underwriters want to see either a third-party age-verification API or a manual review step at checkout. Make it visible in your store settings and screenshots—acquirers will ask for proof that it exists and is enforced. This alone often moves a merchant from decline to approvable.
Photograph every replica with its safety marking in clear focus.
Your product images must show the orange tip, two-tone finish, or whatever legal marking your jurisdiction requires. Do not crop it out or assume customers know it is there. Reviewers judge by appearance first, so a high-resolution shot of the marking is evidence that you are selling a legal toy, not a weapon. Retake photos if needed. This takes a day and it changes how an underwriter reads your entire catalog.
Gather and disclose your full processing history.
If a prior payment account was closed, the new acquirer will find out anyway—usually during underwriting, when they run a MATCH check. Disclose it yourself in your application instead. Explain what happened: was it chargebacks, a policy violation, or a processor decision? Be honest. Many airsoft merchants have been through a processor switch; acquirers know this. What they will not forgive is discovering an undisclosed closure during review, which looks like you are hiding something.
Audit product claims for weapon language.
Review every product title, description, and tag for language that frames the item as a weapon rather than a sport tool. Avoid 'realistic replica firearm' or 'looks identical to real gun'—use 'airsoft rifle' or 'replica training tool' instead. Search your product text for words like 'authentic', 'military-grade', 'combat', or 'tactical' used in ways that emphasize realism over legality. Reword them to focus on sport, collection, or training. This is tedious but it reframes your entire store's tone.
What underwriting will ask you for
- Product safety certification or test report showing legal compliance for your jurisdiction.
- Age-gating screenshot or technical proof of age verification at checkout.
- Processing history from your prior account, including chargeback and dispute records.
- Product photography showing orange tips, two-tone markings or legal safety identifiers.
- Terms of service and product descriptions showing clear age-restriction language.
- Bank statements covering the last three to six months.
- Business license and proof of physical address.
Getting underwritten for airsoft and airguns
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite airsoft and airguns. 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 airsoft and airguns
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
Airsoft stores live on inventory because stock turns fast and buyers search by model, brand and specification. When you move stores by hand, variant data breaks: a rifle with five color options, three barrel lengths and two magazine types is a 30-variant tree, and if you copy descriptions naively the variants diverge—some get the full spec list, others get stripped. On a catalog-heavy store, that is hundreds of bad pages. Metafield data like legal-compliance notes, FPS ratings or import certifications also vanish in a CSV round-trip, leaving you with product pages that no longer prove legality to a customer or an underwriter.
| What you own | How much of it | What breaks doing it by hand | What we do instead |
|---|---|---|---|
| Product images | 6,400images≈ 27 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 | 800descriptions≈ 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 | 4,800variants≈ 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 | 4,000metafields≈ 27 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 | 950records≈ 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 | 3,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,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 | 35discounts≈ 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 |
| Gift card balances | 180gift cardsno manual routecannot be moved by anyone | By handthis is the one thing on this page that truly cannot be moved by anyone. Gift card codes are unreadable through EVERY Shopify API, by design — no tool, ours included, can copy them. Those balances are real money you owe real customers, and abandoning the old store does not abandon the liability: the customers still turn up expecting you to honour it | Automatedwe re-issue each card with an identical balance, customer and expiry date, and hand you the new codes as a CSV with customer email copy ready to send — the only honest way to move them |
| Blogs & pages | 30articles & pages≈ 2 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 | 10apps≈ 10 hrsabout 1 hr per app to reinstall, reconfigure and re-test | By handmost app data lives in metafields on your products and customers, so reinstalling the app gets you an empty app: reviews gone, subscription plans gone, loyalty balances gone, bundles gone. Flows and automations have to be rebuilt by hand and re-tested, and anything with its own billing has to be re-subscribed | Automatedthe metafield data your apps rely on migrates with the products and customers it hangs off, so a reinstalled app finds its data waiting instead of an empty store |
See these numbers for YOUR store, free
The figures above are a typical store in your category. The demo scan connects read-only to yours and counts the real thing — every product, variant, image, customer, order and metafield — then tells you exactly what a migration would carry across. No card, and it never writes to your store.
▶ Run the free demo scanDoes this need a new company?
A new legal entity does not reset your MATCH listing, which is a five-year history of the person running the business, not the company. If your prior account closed, opening a new company will not erase that record—an acquirer will find it. Moving to a new entity can make sense for tax or liability reasons, but it is not a way around payment processing history. Be honest about who owns the new entity and why you changed it.
Frequently asked
Will moving to a new Shopify store fix my payment processing decline?
No. Your MATCH record follows you for five years, and it tracks the person running the business, not the store. If Shopify Payments declined you, a new store does not reset that history. What can change is your processor—you can switch from Shopify's built-in Stripe underwriting to a high-risk acquirer that specializes in airsoft. That move requires a new gateway, but it is separate from your store. The store move itself is useful only if your new gateway requires a different platform or structure.
Which gateway will take an airsoft store?
Several high-risk acquirers publicly advertise airsoft, including Authorize.net on a high-risk merchant ID, PaymentCloud, Soar Payments, and Easy Pay Direct. They underwrite differently—some focus on chargeback history, others on product compliance and age controls. Rather than cold-email each one, get quotes from all of them at once using a broker or a form submission. The gateway that works for you depends on your volume, your prior processing record and how clean your age-gating is. Price and reserve vary widely.
What happens to my product data when I move to a new store?
Your images, titles, descriptions and basic product structure can move, but metafield data—legal compliance notes, performance specs, import certifications—cannot be carried in a CSV export. That means custom fields that prove your products are legal replicas, not weapons, will be silently lost unless you move them programmatically or re-enter them by hand. On an 800-product airsoft catalog, that is weeks of work. A migration service that uses the Shopify API can carry metafields and move your data intact.
Do I need a new business entity to get approved for payment processing?
No. A new legal entity does not erase your MATCH record or reset your payment history. If your prior account was closed for disputes or policy violations, that fact stays on file under your name for five years. Some merchants form a new company for tax or liability reasons, but they should not expect it to help with payment processing approval. Be transparent about ownership and why you changed structures—that honesty matters more to an underwriter than a fresh company name.
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 →