Payouts on hold, and you sell ammunition. Migrate everything to a new Shopify store.
The message arrived in your dashboard: payouts are on hold. No deposits are going to your bank account. You have checked the balance and the money is there—it is just stuck. This is different from a payments deactivation and requires a different response. Shopify holds funds as a cushion against chargeback exposure, typically for up to 120 days from your last transaction, because that is roughly the cardholder dispute window. This is a temporary freeze, not a seizure. The money remains yours and is normally released when the hold period ends. But the real pressure is not the hold itself—it is what happens to your checkout and your cash flow while the hold is in place. Many merchants report that checkout still works during this time, which can feel like everything is fine. It is not. The stalled payouts create a working-capital crisis at the exact moment you need cash most. If you are in this position, you need to act now.
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 dashboard notice: "Payouts have been placed on hold" with no explanation of when they will be released
- Bank account shows no deposits, but dashboard balance keeps growing as orders come in
- Support replies: "Your funds are held pending resolution" with no specifics about what needs resolving
- Checkout continuing to work, which suggests the hold is temporary and not serious
- Cash reserves draining while the payout sits frozen and customers keep ordering
The payout hold itself has a deadline (eventually, funds are released). The cash-flow problem does not. If you cannot operate your business without the daily or weekly deposits you normally receive, this is an urgent problem whether the hold lasts 30 days or 120. The longer it runs, the more expensive it becomes.
Why it happened — specifically for ammunition
Stripe, which underwrites Shopify Payments, lists ammunition as a restricted business. The primary trigger is hazmat shipping liability — ammunition cannot move through standard postal channels and requires carrier compliance. The secondary trigger is fraud loss: bulk ammunition orders are high-value targets, and a chargeback on a $5,000 order costs the processor far more than a chargeback on a $50 order. Underwriters also see state-by-state ID verification as an operational burden they would need to monitor.
Rule out the easy fix first — then deal with the real one
Shopify does not document a route to process ammunition on its native payment system. What merchants typically try first is applying directly to Shopify Payments and hoping the restriction will lift on review — it will not. The honest alternative is that you must move to a specialist high-risk processor. Several payment providers and ISOs explicitly advertise ammunition and 2A-related commerce, and they already know the hazmat and state-ID compliance layer. Applying to one of those is permission to apply, not approval — they run their own underwriting on your order volume, your chargeback history and your shipping procedures.
It only helps if all of these are true:
- You must use a processor that publicly advertises ammunition or firearms-adjacent categories.
- Your shipping carrier must be equipped for hazmat and must accept ammunition under their terms.
- You must be able to document geo-blocking or order-level verification for any state that restricts direct-to-consumer ammunition sales.
- Your chargeback rate and fraud loss history will be reviewed in detail; a high rate will result in decline regardless of other factors.
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
Payouts held on weapons or weapon-adjacent goods reflect the state-by-state and federal legality maze that processors price as legislative risk, not just chargeback risk. A single sale to a prohibited jurisdiction or a misclassified product can trigger a hold that locks all payouts, even if most sales were legitimate. The money is yours, but the cash gap is real and your product catalog may need geo-blocking by state or country before any processor will resume. Before you approach anyone new, map your last 90 days of orders against shipping laws in each destination. If even a handful of sales violated jurisdiction rules, expect that to anchor every conversation.
💎 High average order value, so fraud and disputes cost more per event
A payout hold on high average order value sales means a single fraud or dispute event has material impact on your reserves and your solvency right now. The processor is protecting against chargeback liability that, for your order size, could exceed their reserve anyway. The working-capital gap is not theoretical — you may have shipped goods on credit or taken loans to fund inventory and now have no payout to cover it. The hold typically runs up to 120 days from your last transaction, but the real damage is the stalled checkout, not the hold itself. Before you approach a new processor, have clean transaction records and fulfillment proof for the last 90 days, and be honest about what triggered the hold.
📦 Thousands of SKUs, deep variant matrices, distributor feeds
A payout hold with thousands of SKUs is harder to diagnose and slower to resolve because the processor has to sample across your entire product matrix to understand the dispute pattern. A subset of your variants may have bad claims language, wrong categorization or mismatched descriptions across channels, and the processor cannot release payouts until the sample looks safe. The hold itself is temporary, but the real cost is the stalled checkout and the working-capital gap. Before you switch platforms, export your full product feed and audit it for consistency — mismatched descriptions across Shopify and external marketplaces, SKUs with unsubstantiated claims or wrong MCCs will follow you to any new processor. A hand-rebuild is impossible and not necessary; focus on cleaning the data that is already there.
What you actually have to fix
Underwriters do not change their minds because you asked. They change them because the facts changed. For ammunition, these are the facts that move the decision:
Map which states you legally ship to and block the rest at checkout.
Ammunition sales are prohibited or heavily restricted in several US states, and some states ban direct-to-consumer sale entirely. You must identify those jurisdictions, document your legal position on each, and enforce it in code. An underwriter will ask to see your geo-blocking logic and your evidence that you cannot accidentally fulfill an order to a prohibited state. This is the single highest-yield fix because it removes the largest compliance risk — that you unknowingly become liable for illegal shipments.
Confirm your carrier accepts ammunition and document the agreement.
Standard parcel carriers will not ship ammunition; you must use a hazmat-rated carrier that explicitly accepts it. Contact your current carrier and get written confirmation of either acceptance or rejection. If they accept, request and file their hazmat compliance requirements. If they reject, you need a new carrier before you apply. An underwriter will not process your application without proof of a compliant arrangement, because if your carrier terminates mid-processing, your business stops.
Gather your chargeback and fraud loss data for the past 12–24 months.
High-value ammunition orders attract fraud and chargebacks. Pull your full history: dispute counts, amounts lost, reason codes and whether they were won or lost. If your chargeback rate is elevated, you may not be approvable until it improves. Be honest about this figure — underwriters will cross-check it against your processor history, and misrepresenting it is grounds for immediate decline and blacklisting.
Prepare your order verification procedure for high-ticket sales.
Ammunition is a target for resale and fraud. Document how you verify customer identity and intent for orders above a certain threshold — for example, orders over $2,000 or orders containing more than a certain number of units. Show whether you require photo ID, signature on delivery, or secondary verification. Underwriters want to see that you have thought about fraud and have a repeatable process.
What underwriting will ask you for
- Proof of hazmat-compliant carrier agreement or signed terms showing ammunition acceptance
- State-by-state compliance map showing which states you ship to and which restrict DTC sales
- Chargeback and fraud loss history for the past 12–24 months
- High-ticket order procedure: how you handle orders above your typical AOV
- Product liability insurance or certificate of insurance covering ammunition sales
- Shipping procedure document showing how you verify customer age and location at checkout
- Processing history with previous acquirers, including any declines or terminations
Getting underwritten for ammunition
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite ammunition. 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 ammunition
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
- Find out why the hold was triggeredPayouts do not freeze for no reason. Check your recent account activity for unusual patterns: a spike in orders, a high chargeback rate, or transactions from new geographies. Look at your support tickets and emails for any hints Shopify has given you. Then contact Shopify support directly and ask for the specific reason. Be clear and factual. You will probably get a vague answer — many merchants do — but you need to know whether this is a precaution, a policy breach, or something you actually did. That answer determines your next move.
- Get a verified copy of your store out while you still have access — todayThis is the only step with a deadline you do not control. A payout hold can escalate to a payments suspension or account closure without warning. If that happens, admin access can go with it. Once the account is locked, the API closes — and without the API your catalog, order history, customers, and all stored metadata are unreachable. Not deleted; just inaccessible. Export your full store now: product catalog, orders, customer list, and any custom data your theme depends on. This is not a backup for paranoia. It is the step that separates a cash crisis from a dead business.
- Calculate your actual working-capital shortfallStop looking at the hold as a deadline and start looking at it as a cash problem. How many days of operating expenses can you cover without a payout? Rent, staff, inventory, shipping — add them up. Then work backwards: if your usual payout arrives weekly and payouts are now frozen, how long before you cannot pay your bills? This number — not the 120-day hold period — is what drives your next decision. If you can last 30 days, you wait. If you cannot last 7 days, you need a different payment method now.
- Apply for a third-party gateway while you keep Shopify PaymentsShopify allows multiple payment methods on one store. You can add Stripe, Square, or another gateway without removing Shopify Payments. This means new orders can flow through a different processor while you wait for the payout hold to release. It does not fix the hold, but it stops the checkout from becoming useless. Set it up as the primary method so new customers pay through the new gateway, then monitor both for fraud or blocks. Some gateways approve faster than others, and some are more tolerant of the categories Shopify flagged.
- Prepare to migrate if the hold becomes a suspensionA hold can become a deactivation. If Shopify sends a second notice saying payments are being switched off, treat it as urgent. At that point, Shopify Payments goes away and checkout stops unless you have a backup gateway. You will need to move your store to a new Shopify account, a different platform, or a new processor entirely. The longer you wait, the harder this is because your cash is even more depleted. Many merchants in this position cannot afford the migration on their own and report needing outside help — which is where a service that moves your full store, including SEO data and customer records, becomes a practical solution rather than a luxury.
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
Ammunition stores carry compliance metadata in metafields that a standard CSV export cannot touch. State-restriction flags, hazmat shipping codes, lot numbers and expiration dates are all stored as reference or file metafields tied to individual products or variants. A hand-migrated store will lose these silently — the products copy over, the metafield definitions fail to migrate, and your checkout no longer knows which states a product ships to. On a regulated high-AOV product, discovering this after you go live is a compliance failure, not a cosmetic bug.
| What you own | How much of it | What breaks doing it by hand | What we do instead |
|---|---|---|---|
| Product images | 15,000images≈ 63 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 | 2,500descriptions≈ 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 | 7,500variants≈ 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 | 20,000metafields≈ 133 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 | 2,683records≈ 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 | 15videos≈ 1 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 | 8,000customers≈ 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 | 12,000orders≈ 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 | 4menus≈ 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 |
| 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 | 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 will not reset your payment processing history. If you or anyone with significant ownership stake in your current business has a decline or chargeback history, that history follows you to a new company for five years under MATCH reporting. Moving to a new entity purely to avoid underwriting scrutiny is visible to acquirers and is treated as fraud. The sensible reason to form a new entity is genuine operational separation — different product line, different team, different market — but the underwriting will start from scratch only if you have no common ownership, officers or processing history.
Frequently asked
Which payment gateway will actually approve ammunition sales?
The gateway itself is rarely the bottleneck — providers like Authorize.net and PaymentCloud have high-risk merchant accounts and integrate with Shopify. The real decision is the merchant account behind the gateway, and that depends on your volume, your chargeback history and your carrier and geo-blocking setup. Rather than apply cold to a dozen processors, use a broker or ISO that specialises in 2A commerce — they already know which acquirers are currently underwriting ammunition and at what reserve.
What reserve should I expect?
Ammunition is high-risk, so reserves are standard. Acquirers commonly hold 10–20% of your monthly volume, released over 90–180 days. Some may hold longer if your order value is very high or your chargeback history is concerning. This is not punitive; it is risk management. Plan your cash flow around it — do not assume the money will be available for 60 days after you receive it.
Will my product data survive a migration to a new processor?
Your products, descriptions and images will copy, but your compliance metadata will not. State restrictions, lot numbers, hazmat codes and other metafields live in Shopify's metafield system, and Shopify's CSV export cannot read them. If you migrate by hand, those data will be lost and you will have to re-enter them manually — which is error-prone on a large catalog. A service that migrates using the API can carry them over if you have properly structured them beforehand.
If I move to a new processor and my current Shopify Payments account is terminated, can I apply again later?
Not for at least five years. Shopify Payments terminates go into the MATCH system, and Stripe (the underwriter) will decline you again if you reapply under the same ownership. Your best path forward is to stay with a specialist processor once you move. Shopify's own payment system is not designed for ammunition, and fighting it repeatedly costs time you do not have.
Why are my payouts frozen if I haven't broken any rules?
Shopify holds payouts against chargeback risk, and that screening is automatic. A high order volume, orders from unusual locations, a product category with higher dispute rates, or a sudden increase in sales can all trigger a hold even if every transaction is legitimate. You have done nothing wrong; the algorithm flagged a pattern. The hold is a precaution, not a penalty. Legitimate merchants are held regularly and the money is released on schedule.
How long will the hold actually last?
Up to 120 days from your last transaction, typically. But if Shopify suspects illegitimate commerce—not just unusual patterns, but actual fraud—the hold can extend longer. The hold period resets each time you get a new transaction, so if you are still taking orders, the 120 days starts counting from the most recent one. There is no way to know your exact release date without asking support, and support often cannot give a precise answer.
Can I speed up the hold or get an early release?
You can ask. An appeal works if you can explain what triggered the hold and show it has been resolved. Provide order details, customer feedback, or evidence that the spike in activity was legitimate. But Shopify does not publish a standard appeal process and most merchants report the response is vague or takes weeks. There is no guarantee an appeal will work, even with evidence.
What happens to my checkout while payouts are on hold?
Checkout typically continues working. Customers can still buy, orders keep coming in, and your inventory depletes normally. But money is not reaching your bank account, which creates a working-capital crisis. You are taking revenue without being able to use it. This is often worse than a checkout block because it creates the illusion that everything is fine while you bleed cash.
Do I need to switch payment processors to get my money unstuck?
Not to release the hold itself—Shopify will release the frozen balance on schedule regardless of what gateway you use. But if you cannot afford to wait, a backup gateway lets you process new orders through a different processor while the hold counts down. You can run Shopify Payments and a third-party gateway at the same time. A new gateway does not unlock the hold; it prevents new orders from becoming inaccessible if the hold escalates to a suspension.
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 →