Application rejected, and you sell ammunition. Migrate everything to a new Shopify store.
The email came back fast: your Shopify Payments application has been declined. No reason given, or a one-line reason that doesn't quite fit. You have no payouts held, no suspension notice, no terminated-merchant file record — just a gateway that won't activate. This is the cleanest version of a payments crisis, and it's worth understanding why. Shopify Payments is underwritten by Stripe, and Stripe screens applications against the product category you declared, the countries you ship to, and the completeness of your business profile. Rejection at application stage means the review happened before any money moved. You can stay on this Shopify store, keep your domain, keep your design, and simply activate a different payment gateway instead. No migration needed. No data loss. The store is fine; the first gateway you tried wasn't the fit.
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
- "Shopify Payments is not available for your business type" — with no detail on which part of your business triggered it
- "Your application does not meet our underwriting requirements" — rejection with no explanation of what failed
- Application status stuck on "Pending" for weeks, then declined without a decision document
- Request to reapply immediately rejected, suggesting a category-level block rather than a profile issue
- A business profile that looks complete to you, but Stripe's questions were answered incompletely or ambiguously
The only clock that matters is your launch timeline. You have no external deadline. Take time to choose the right gateway for your category and geography, because switching gateways mid-launch is friction you don't want. Activation is fast; selection is the real work.
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
Weapon-adjacent categories face country and state-by-state legal fragmentation. A processor rejects an application because they cannot write a compliance policy that covers all jurisdictions simultaneously—it is risk pricing, not a ban. You need geo-blocking at catalog level, so customers in restricted regions cannot see or buy restricted items. Before reapplying, map your product list against federal law and the laws of your target states. Then lock down your Shopify store to block checkout in jurisdictions where your products are illegal. Provide that blocking strategy in your reapplication. The gateway will want proof of intent before they take you.
💎 High average order value, so fraud and disputes cost more per event
High average order value makes fraud and chargeback exposure material to the processor's loss reserves. Your application was rejected because fraud controls and verification steps were not explicit in your business profile. At your price point, a single breach-of-warranty or 'not as described' dispute can exceed their tolerance. Before reapplying, document your fraud controls: address verification, signature on delivery, customer communication trails, and a dispute-response process. Show exactly how you will verify customer identity and intent. Processors price high-AOV risk individually; the rejection is not categorical, it is about demonstrating that you have sized your operations to the exposure.
📦 Thousands of SKUs, deep variant matrices, distributor feeds
A rejection with thousands of SKUs often points to incomplete or malformed product data—missing descriptions, variant matrices that don't resolve, or images not attached. Processors screen catalog data not to judge your products but to understand your operations and spot high-risk items hiding in the tail. Before reapplying, run an export audit: do all products have descriptions, categories, and images? Are your variant rules consistent? Do images match claims? A cleaned catalog is faster to underwrite and harder to dispute. If you are pulling from a distributor feed, validate that feed against Shopify's import schema before you reapply. The rejection is usually about data shape, not category risk.
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
- Check your business profile for gapsLog into your Shopify admin and review the business information Stripe saw: your legal business name, tax ID, business address, product category, and description of what you sell. Read it as a stranger. Is the category accurate? Some categories are harder to underwrite than others — if you sell general merchandise but wrote "beauty products", Stripe screens you against beauty-specific rules. Is every required field actually filled in? Partially-completed profiles often get rejected because underwriting is automated. If something is wrong, fix it — then you can either reapply to Shopify Payments or move forward with a different gateway.
- Research which gateways accept your category and countryYou don't have time to wait for a reapplication. Other gateways underwrite the same categories that Shopify Payments rejected, and some don't. The gateways that publicly advertise support for your product category are the ones to approach. Search for your category plus "payment gateway" or "payment processor", and look for gateways that list your country as supported and your category as acceptable. Check their integration with Shopify: most major gateways offer a public Shopify app. You're looking for one that will activate before your launch date.
- Activate the new gateway on your Shopify storeOnce you have selected a gateway that accepts your category, install its Shopify app or follow its setup instructions. No data migration needed. Your catalog, your design, your customers list, your orders — everything stays on your Shopify store. You're only swapping which processor settles your money. The new gateway typically activates within hours of setup. Test a transaction in sandbox mode, then switch to live. You can delete Shopify Payments from your payment methods as soon as the new gateway is active.
- Rebuild your checkout for the new gateway's requirementsSome gateways have stricter data collection than others. Check whether your new gateway requires address verification, CVV, or three-D Secure. If your checkout was set up for minimal friction, adding these fields might drop your conversion rate slightly — but an active checkout beats a perfect one that doesn't work. You can always soften friction later. Set up the new gateway's webhook and monitoring now, so you know immediately if transactions start failing. Test again with a real transaction.
- Keep Shopify Payments as a backup option, or don'tIf you want to reapply to Shopify Payments in three to six months, you can. Your store will remember the rejection, but there's no rule against trying again after you've fixed your profile or grown your order history. Some gateways have higher fees than Shopify Payments — if you plan to go back, set a reminder for the reapplication and make sure your business profile is locked in. More likely: you'll find a gateway that works, your sales will grow, and you'll never think about Shopify Payments again. Either way, you're selling now instead of waiting.
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 did Shopify Payments reject me if I filled in every field?
Stripe uses automated underwriting that screens your product category against its policy. Some categories carry higher chargeback or fraud risk, and Stripe declines applications in those categories even if your profile is perfect. Others are harder to underwrite if your business description is vague. Stripe does not publish the exact reason for individual rejections. If your category is on its public restricted list, rejection is policy. If your category is general, the problem was likely profile clarity — describe exactly what you sell, not categories.
Can I reapply to Shopify Payments right now?
Technically yes, but reapplying with an identical profile will likely be rejected again. Shopify (via Stripe) publishes no SLA for reapplication review. If you believe your first application had incomplete information, fix your profile first, then try again. If your product category is what triggered the decline, reapplication will not help unless you've genuinely changed what you sell. In the meantime, activating a different gateway lets you start taking payments immediately.
Will switching to a different payment gateway lose my customer data or orders?
No. Switching payment gateways does not touch your store, your catalog, your customers, your order history or anything else in Shopify. You are only changing which processor settles your money. All your Shopify data stays exactly where it is. The new gateway integrates with your checkout, and new orders go through it instead of Shopify Payments. Old orders stay in your Shopify admin. No migration, no data loss.
What if every gateway rejects me?
This is rare at application stage (as opposed to after trading). If multiple gateways decline you, the issue is usually your product category being on most processors' restricted lists, or incomplete business information that raises flags across the board. Read their rejection emails for hints. Complete your business profile fully and honestly. If your category is genuinely restricted (adult content, certain financial services, high-risk gambling), mainstream gateways won't work — you would need a high-risk processor, which is slower to activate and more expensive.
Can you reactivate Shopify Payments for me after I switch gateways?
No. We can't turn Shopify Payments back on, and Stripe's decision is not reversible by Shopify support. What we do is move your store to a new Shopify store built around a gateway that will accept you — migrating your catalog, descriptions, images, customers, orders, themes and more. But for an application rejection with no funds held, you don't need a migration. Activating a different gateway on your current store is faster, cheaper and keeps everything you've built. Migrate only if you later face a termination and need to move to a new Shopify account entirely.
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 →