Account under review, and you sell ammunition. Migrate everything to a new Shopify store.
The email arrived without warning: your Shopify Payments account is under review. Checkouts still work. Money still lands. But the language is formal and it asks for documents you may not have ready — bank statements, tax returns, proof of product source, clarity on your business structure. The clock is invisible and no one tells you how long it will take. Here is what changes what you do. This is the moment you still have influence. A review is not a decision; it is an open question. The processor is asking because something triggered a flag — a sudden jump in volume or order value, a rise in chargebacks, documents that did not match, or simply the product category you chose. Your job is to answer the exact question asked, with evidence, and nothing else. Do not volunteer new information or try to rewrite your story. And critically: prepare a copy of your store right now, while you still have full access. If the review clears, you never need it. If it does not, you will have lost the only window where you could have saved it.
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
- "We are reviewing your account to ensure it meets our requirements — please provide documents by [date]"
- Bank statements, tax returns, government ID, or proof of business registration — the list depends on what triggered the review
- Checkouts processing normally while the background review runs, creating false confidence that nothing is wrong
- "Your account remains under review" — weeks or months later, with no clear next step or timeline
- Support responses that repeat the policy without explaining what specifically needs to be fixed
The real deadline is invisible: the date Shopify's or the processor's underwriter makes a final decision. You cannot know when that is, so the clock that matters is the one you control — getting a full backup of your store today, while you have admin access. A review that goes wrong becomes a suspension, and a suspension can become an account closure. Once access is gone, your data is unreachable.
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
Your account is under review because a single SKU triggered a category flag or because volume changed sharply. The reviewer wants to see your geo-blocking posture—which products are available in which jurisdictions, and whether your catalog matches what you are actually shipping. Pull your product pages and filter settings; show that restricted items are blocked in states or countries where they cannot legally ship. If you have a distributor feed, check that the source data does not override your blocks. Answer the specific question about that product or shipment pattern. Do not volunteer that you sell anything else restricted. In parallel, start a copy of your catalog on a gateway that specializes in your category—preparation now means you can move fast if the review outcome is not what you need.
💎 High average order value, so fraud and disputes cost more per event
A single dispute or fraud event at your order size is enough to trigger a review, and the processor is now sizing reserves against your entire account exposure. The reviewer wants evidence that you know who your customer is and that the transaction was legitimate—identity, shipping address match, any authentication you ran. Pull the flagged order: invoice, shipping confirmation, customer communication, proof of delivery. Answer about that specific transaction. Do not volunteer that you have other high-value orders or high-value customer segments. While the review runs, prepare a copy of your store on a gateway comfortable with your AOV and category—you are still in the window where you have negotiating room, and building silently does not weaken your position. If the review outcome requires a move, you will already be ready.
📦 Thousands of SKUs, deep variant matrices, distributor feeds
A volume spike or a category flag triggered the review, and now you need to answer about your product range and sourcing. The reviewer wants to understand your distributor feeds and variant matrix—which products are auto-updated, which are manual, where compliance happens. You cannot hand-rebuild thousands of SKUs, so explain your control: how do you prevent a feed from pushing restricted items into unrestricted geographies, how do you audit claims language across variants, where does the review happen. Answer narrowly about the flagged product or category. While the review runs, start a copy of your full catalog on a gateway that accepts your category and can handle distributor feeds—do not try to simplify or prune the catalog yet. A prepared copy with all your variants and feeds means you can move the whole operation if needed, rather than rebuilding from scratch during an emergency.
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
- Read the request and answer only that questionDo not assume you know what triggered the review. Read the email carefully and identify the exact documents or clarifications they asked for. If they asked for bank statements showing business revenue, send bank statements — not tax returns, not personal documents, not a general business overview. If they asked about your supplier, name the supplier and provide a wholesale agreement or invoice — not a marketing story about your brand. Do not volunteer information they did not ask for. Every piece of paper you add becomes another thing they can scrutinize, and underwriters look for inconsistencies. Stick to the question.
- Get a verified copy of your store — today, while you have accessThis is the step people skip because the review feels temporary and checkouts are still open. It is not temporary, and access can vanish without notice. A negative review decision is usually followed by an account suspension or closure. Once that happens, admin access can be revoked immediately, and you lose the ability to export anything — catalog, orders, customer data, SEO metadata, theme files, discounts, redirects, metafields. Shopify's own CSV export cannot carry metafields, orders, gift card codes, videos, themes, menus, discounts or redirects. That is why a backup taken during the review, while you still have full control, is the only insurance that works. You will almost certainly not need it. But if you do, it is the difference between a bad month and a dead business.
- Gather any supporting documents they did not ask for but might needWhile you are responding to the stated request, identify supporting evidence you can provide without volunteering it — documents that backstop your answer to their question. If they ask about volume and you have a marketing invoice showing a paid campaign, or a supplier invoice showing you bought stock in bulk to meet demand, keep those nearby. Do not send them unless they ask, or unless your first response does not clear the review and you are invited to provide more. Let them lead on scope. Over-documenting looks like you are hiding something.
- Respond before the deadline, using the communication channel they specifiedRead the email again for the exact submission method and deadline. Send your response through that channel, not through support or a different email address. If they asked you to upload documents via your Shopify admin, do that — it leaves a timestamped record. If they gave you an email address or support ticket, use that. Include a clear note stating what you are submitting and why: "Per your review request of [date], I am providing [documents] which show [specific fact you are answering]." Do not oversell; be factual and brief. Save a copy of everything you send, and the timestamp.
- Prepare for a second gateway before you hear backA review can take weeks or months to resolve, and you cannot know the outcome in advance. Do not wait for a clearing decision to act on your backup plan. Research payment gateways that publicly advertise your product category and accept merchants with histories similar to yours. Stripe, Square, Wise, 2Checkout and others operate alongside or instead of Shopify Payments for many merchants — but approval is not guaranteed, and each has its own underwriting. The time to gather your account information and test integrations is now, while your store is fully functional and you are not under time pressure. If the review clears, you delete the backup and move on. If it does not, you have already removed the panic from the migration decision.
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.
How long does a Shopify Payments review actually take?
There is no published timeline. Merchants commonly report decisions within two to four weeks, but some reviews remain open for months with no communication. The processor does not announce when a decision has been made; you find out either when you receive a follow-up email asking for more information, or when your account status changes without notice. Checking your account settings regularly for status changes is safer than waiting for an email.
What happens to my money during the review?
Payouts typically continue during an active review. Money from orders you process lands in your bank account on your normal schedule. The risk is not immediate loss; it is the outcome of the review. If the review goes against you, that is when payouts stop. The balance may then be held against potential chargebacks or disputes for weeks or months depending on the reason for the suspension.
Will they tell me why they are reviewing my account?
The first email usually says why — it mentions a document request, a dispute threshold, a volume change, or your product category. If it is vague, reply asking for clarity on exactly what the underwriter is concerned about. Be factual and non-defensive: "I want to ensure I address your concern — can you clarify whether this is about my supplier documentation, my transaction volume, or something else?" Sometimes they will detail it; sometimes they will not. Either way, answer what they asked for.
If I cannot find the documents they asked for, what should I do?
Tell them. Do not fabricate or send a substitute. If they asked for a bank statement and your bank account is new, or if you do not have incorporation papers because you operate as a sole trader, say so in your response. Explain what you do have instead, and why. For example: "I do not have formal incorporation papers as I operate as a sole proprietor — my government-issued ID and the business registration attached show my authority to operate." Underwriters understand that not every business has every document type. What they cannot forgive is documents that appear forged or misdated.
Can I appeal if they reject my account?
A review is not the same as an appeal. If your account is rejected after this review, you can ask why — and if the rejection was based on incomplete or outdated information, you can submit a formal appeal. But you cannot appeal a policy. If your product category is on the processor's restricted list, appealing your story will not change the category restriction; it means moving to a processor that accepts it. If the category is legal in your jurisdiction but restricted by the processor, you need a different gateway. A new Shopify store with a different gateway, or a migration to a new platform, is then the real option — not another appeal.
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 →