Finding a high-risk payment gateway, and you sell ammunition. Migrate everything to a new Shopify store.
You have been looking at lists of payment gateways that work with Shopify. Stripe, Square, PayPal, Adyen — they all have checkboxes next to them saying 'high-risk' or 'supports adult' or 'accepts CBD'. Here is what those lists do not say. The gateway is the technical plumbing. It connects your checkout to a payment processor. Shopify supports dozens of them natively, and more through apps. But the gateway itself does not underwrite you. Behind every gateway sits a merchant account — a MID, a relationship with an acquiring bank or payment processor. That is where the actual application lives. That is where a human or an algorithm decides whether to accept your business type, your geography, your volume, your history. A gateway that 'supports high-risk' merchants does not mean it will approve you. It means it accepts applications from people in your category. The approval is separate, specific, and yours alone. Merchants commonly spend weeks comparing gateways and hours on the actual underwriting — and then get declined by the merchant account on day one.
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
- Gateway comparison lists showing 20 options, each marked 'high-risk friendly', with no mention of MID approval odds
- Shopify's app store showing third-party gateways as a simple install, with no warning about the separate merchant account application
- A message that a gateway 'accepts high-risk merchants', interpreted as approval, actually meaning only that they take applications
- Assumption that if Shopify integrates a gateway, it will approve a new high-risk merchant — not true
- Discovery three weeks into setup that the gateway's parent processor has declined the merchant account application
The merchant account decision is the actual deadline. You can prepare the technical setup while applications are pending, but nothing clears until underwriting says yes. Some processors publish estimated timelines; most do not. Time in underwriting is time your store makes no money.
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
A gateway that accepts weapon-adjacent merchants is processing the technical transaction only. The merchant account underwriting will focus on your catalog-level geo-blocking, state-by-state legality checks, and proof that you cannot sell into jurisdictions where your products are prohibited. Because legality is fragmented by geography, acquirers price this as an ongoing compliance risk, not a one-time underwriting decision. You will face higher rates and likely a mandatory reserve sized against potential regulatory or chargeback exposure. Shopify's third-party gateway fee adds to your cost. Before you approach any processor, audit your catalog to confirm every SKU is blocked in territories where it is illegal. A gateway list cannot account for this; only your controls can.
💎 High average order value, so fraud and disputes cost more per event
A single dispute or fraud event becomes a material loss at high average order value, so underwriters will price reserves and rate penalties accordingly. The merchant account application will demand evidence of your fraud detection, address verification, CVV checking, and order review process. Shopify's third-party gateway fee applies to every transaction, which is material when your average order is large. Most high-risk acquirers will hold a mandatory reserve—often 5–15 per cent of rolling volume or a fixed dollar amount—as protection against a spike in chargebacks or fraud disputes. Honesty about your chargeback history matters more than optimism. A gateway list shows who processes the category; it does not show who will approve you or what reserve they will demand.
📦 Thousands of SKUs, deep variant matrices, distributor feeds
A large catalog with thousands of SKUs and variant matrices means you cannot hand-rebuild if you move gateways. The merchant account underwriter will want evidence that your system can reliably avoid selling prohibited items into prohibited jurisdictions—which matters most for weapons or age-restricted goods, but also for any category with geography-specific restrictions. Shopify's CSV export cannot carry videos, theme, metafields, discounts, redirects or orders, so a hand-migration is impossible anyway. When you approach a new acquirer, they will ask how you manage compliance at scale across your entire product range. A gateway that accepts your category means nothing if you cannot prove your SKU-level restrictions actually work. Plan the full migration—data structure, theme, image quality, SEO redirects—before you commit to a new processor. Underwriters want to see that you have already solved the operational problem, not that you are learning as you go.
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
- Separate the gateway from the merchant account in your mindThe Shopify integration list shows what can be plugged in technically. The processor's application is what actually evaluates you. Installing a gateway in Shopify does not skip the merchant account step. It is the setup you can do in parallel. Write down the processor's name — the company that will actually underwrite you — separately from the gateway name. That distinction will save you weeks of confusion. When you get declined, you will know whether to blame the gateway (which is rare) or the underwriting criteria (which is the reason 99 times out of 100).
- Research the processor's actual criteria, not the gateway's marketingThe gateway's website will say 'we support high-risk merchants'. The processor's underwriting criteria — the thing that matters — lives in their application form, their policies, or a conversation with their underwriting team. Find it before you apply. Call them. Ask what business types they actually underwrite, what volume they need to see, whether they want reserves, what your rate will be. Cheaper gateways often cost more once you factor in reserves, higher rates, and transaction fees. Shopify also charges an additional third-party-gateway transaction fee on top of the processor's rate — tiered by your plan. That fee exists. Budget for it.
- Prepare your application materials while applications are pendingWhile the merchant account is being underwritten, you are waiting. Use that time to collect what processors will ask for: business registration, tax ID, processing history, bank statements, identity verification. Different processors have different checklists. Some will ask for personal guarantees. Some will want to know about past declined accounts. If you have been through a payment processor decline before, have that story ready and honest. Many processors now ask about MATCH history — the card networks' list of terminated merchants — and the answer matters more than the story. If you are on it, disclose it. Lying will disqualify you faster than the truth.
- Apply to multiple processors in parallel, not sequentiallyDo not pick one gateway, apply, get declined, then pick another. Research and apply to three to five processors whose criteria match your business type, in the same week if possible. Each application goes into the processor's system, and a decline does not flag you across all of them. But time between applications is time your store makes no money. Applications take days to weeks to process, so start the stack now rather than one at a time. Keep notes on each processor's criteria, rate, timeline, and reserve requirement so you can compare approved offers.
- Plan for worse terms than Shopify Payments, and budget the cost inIf you move to a third-party gateway, expect higher transaction rates, volume caps, rolling reserves, or setup fees. These are not bugs — they are how high-risk underwriting works. The processor is taking on more chargeback risk or regulatory scrutiny, so the pricing reflects that. Shopify Payments was a flat rate with no reserve. Your new processor will likely have both a rate and a reserve — money held back against chargebacks, sometimes 10 to 25 percent of monthly volume. That is working capital you do not have. Factor it into your business plan. If you cannot operate with a reserve, that processor is not a fit, and you move to the next application.
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.
What is the difference between a payment gateway and a merchant account?
The gateway is the software bridge connecting your Shopify checkout to a payment processor — it handles the technical flow of card data. The merchant account is your commercial relationship with the processor, and it is where underwriting happens. You can have the gateway installed in Shopify and still not be approved for the merchant account. The gateway is necessary but not sufficient.
If Shopify integrates a third-party gateway, will it approve me?
No. Shopify's integration of a gateway means only that the technical connection is possible. The merchant account approval comes from the processor that owns the gateway, using their own underwriting criteria. Some of those processors are more liberal with high-risk categories than others, but none of them approve everyone. Integration and approval are separate decisions.
Will I have to pay Shopify a fee on top of the processor's rate?
Yes. Shopify charges an additional third-party-gateway transaction fee on top of what the processor charges. This fee is tiered by your plan. It is a real cost and should be factored into your rate comparison when you are deciding which processor to apply to. The processor's advertised rate is not your total rate.
Can I appeal if a processor declines my merchant account application?
You cannot appeal to force approval, but you can reapply later if your circumstances change meaningfully — higher volume, longer business history, reserves in place, or a shift in your business type toward lower-risk activity. Some merchants reapply after six months to a year. Most processors will consider a fresh application if your profile is different. Lying on the reapplication will disqualify you entirely.
If I get declined by one gateway processor, will other processors know about it?
Each processor screens applications against the card networks' MATCH file — the list of terminated merchants — but they do not automatically see declines from other processors. A decline itself is not instantly shared across the industry. However, multiple hard applications in a short time can raise flags for some processors, and if you are on MATCH, every processor will see it. Apply thoughtfully to a few good fits rather than scattering applications everywhere. If you have been declined before, disclose it in the new application.
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 →