Prohibited business type, and you sell firearms accessories. Migrate everything to a new Shopify store.
You applied for Shopify Payments and got a rejection that said your business type is not supported. You then searched Shopify's help centre for the prohibited list and found nothing, because Shopify does not publish one. Here is why that matters, and what to do. Shopify Payments is underwritten by a payment processor — Stripe, PayPal or Adyen, depending on your country. Shopify's own terms defer to the processor's underwriting rules. That means the restriction you hit is not Shopify's rule. It is the processor's rule, and it lives in a document you need to find and read. The operative document is your processor's restricted-businesses list. That list is not a vague policy. It is a specific set of business types, and if you can prove you do not belong in it, or that you belong in a carve-out, you have a move. If you do belong in it, a third-party gateway — one with a different acquiring bank — may accept you. Find out which one you hit first.
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
- "Your business type is not currently supported" — with no link to which list that came from
- Shopify help articles about Stripe's restricted list, but no link to Stripe's actual list — and Stripe's list changes
- Confusion about whether this is a Shopify decision or a processor decision
- Assumption that switching to another Shopify theme or store will reset it
- Search results for "Shopify prohibited business" returning other merchants' stories, not policy
Time matters here, but not for the reason you think. The decision is final unless you have new facts. A processor will not reconsider on the same evidence. But if you can submit a real carve-out — a specific merchant code, a subcategory exception, a proof of age or licence — the window to reapply stays open only as long as your business looks the same to their automated screening. The move is to find which processor will take you, and that is urgent because the longer you operate without a payment gateway, the harder it becomes to get one.
Why it happened — specifically for firearms accessories
Shopify Payments is underwritten by Stripe, and Stripe's policy on firearms and firearms parts is categorical: the business is restricted, and within that restriction certain items—magazines above state capacity limits, components that function as receivers, and parts marketed for assembly—live in a prohibited subcategory. The secondary trigger is guilt by association. A processor reviewing your store sees magazines, optics and holsters together. They do not separate the low-risk items from the high-risk ones; they see a firearms merchant and apply the blanket policy, so your compliant optics get caught by the same decline as your restricted magazines.
Rule out the easy fix first — then deal with the real one
Shopify does not document a route for this category. There is no attestation, no third-party integration and no declared path. What merchants try first is applying directly to Stripe or Shopify with a letter explaining that most of their catalog is legal and shippable. This fails because Stripe's policy is not a review process—it is a category exclusion. An individual appeal rarely changes it. Your alternative is moving to an acquirer that underwrites firearms accessories as a vertical: they run the compliance separately and accept case-by-case, so your store is judged on what you actually sell, not on category proximity. This requires moving payment gateways and, usually, payment processors entirely.
It only helps if all of these are true:
- No documented Shopify route exists; you must change processors.
- An alternative processor's underwriting team must approve your product list before you apply.
- Your store must geo-block any item prohibited in the customer's shipping state.
- You must carry insurance and licenses where your jurisdiction requires them for the items you sell.
- Magazine capacity limits and receiver components must be removed or fully compliant with state law.
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
Shopify Payments does not have its own prohibited list — it delegates to the processor for your country (Stripe, PayPal or Adyen). So the operative document is that processor's restricted list. For anything weapon-adjacent, legality is state-by-state and country-by-country, and processors price that complexity heavily. Catalog-level geo-blocking is the compliance posture: you must prevent customers in certain jurisdictions from seeing or buying certain products. That is not a checkbox in your payment settings — it is a catalog rebuild. Before you approach a new processor, map which products are legal where you actually ship. That geography then shapes how you rebuild your store.
📦 Thousands of SKUs, deep variant matrices, distributor feeds
Shopify Payments does not publish its own prohibited list — it delegates to your country's processor (Stripe, PayPal or Adyen). If that processor prohibits your category, you cannot simply re-list the same products on a new store. You may need to remove, relabel or geo-block thousands of SKUs. With deep variant matrices and distributor feeds, a hand-rebuild is impossible. Before you approach a new processor, confirm they accept your category and understand what catalog changes they might require. Then cost the rebuild: extraction, filtering, relabelling, re-upload to a new store, and a second run to verify counts. That work is separate from payment processing, but it is not optional. Shopify's CSV export cannot carry variants, metafields, videos or discounts — you will need third-party tools to move the full catalog intact.
💎 High average order value, so fraud and disputes cost more per event
When average order value is high, a single fraud or chargeback event is material to your reserves and your underwriting profile. Shopify Payments does not publish its own prohibited list — it delegates to the processor (Stripe, PayPal or Adyen). That processor is pricing your risk, not just your category. If you are marked as prohibited, it is often because your dispute rate or fraud rate signalled risk, not because your product type is forbidden. Before approaching anyone new, pull your Stripe dashboard data: your dispute rate, chargeback rate, and average dispute amount. That evidence tells an underwriter whether the issue is category or performance. If it is performance, fix it. If it is category, you need a processor who accepts that category at that risk level.
What you actually have to fix
Underwriters do not change their minds because you asked. They change them because the facts changed. For firearms accessories, these are the facts that move the decision:
Map and geo-block every restricted SKU by state.
This is the single move that makes most firearms accessory stores fundable. Magazines above state capacity limits, certain receiver blanks and binary triggers are prohibited in specific states. You must identify every restricted item, look up the laws in your top 20 shipping states, and then configure Shopify to block checkout for those postcodes. A processor reviewing your store will ask for proof—screenshots of your checkout rule or a technical report showing which postcodes see which products. This is not optional; it is the foundation of your compliance.
Audit every product description for assembly and manufacturing language.
Parts sold as 'components to complete your build' or 'lower receiver blanks' trigger prohibited status even if the item itself is legal. A processor reads 'assemble' and sees you as selling a way around dealer licensing. Rewrite descriptions to be functionally accurate but never suggest assembly, manufacturing or circumventing requirements. 'Precision-machined component' is defensible; 'everything you need to finish your lower' is not. Check your email campaigns and social media too; a single post advertising 'build your own' can sink an underwriting application.
Gather proof of insurance and licensure.
Your underwriting file must include commercial general liability insurance naming firearms product risk, and copies of any federal firearms licenses (FFL), business licenses or state permits you hold. If you do not hold the licenses you should hold—if you are selling components that require dealer licensing but you do not have one—state that plainly and remove those SKUs. An underwriter will find out. It is better to disclose it yourself and prove you have complied than to let them discover it in a chargeback dispute eighteen months from now.
Document your distributor feeds and dropship terms.
Firearms accessory merchants often work with distributors and dropshippers. Pull your contracts and confirm they allow retail resale and that they specify your compliance obligations—particularly around magazines and restricted components. Some distributors will not ship certain items to certain states; you must know this and map it into your geo-blocking. List your top 3–5 suppliers and their restrictions in your underwriting submission. Transparency here signals you are running the category seriously, not as a side venture.
What underwriting will ask you for
- Product catalog with full SKU descriptions, including whether each item requires a license or permit in your key shipping states
- Magazine inventory list with state-by-state capacity limits and geo-blocking proof for each SKU
- Proof of insurance covering product liability for firearms accessories
- Certificate of occupancy or business lease showing your retail or warehouse location
- Shipping and handling policy clearly stating which items are not shipped to certain states
- Bank statements for the last 12 months showing transaction volume and frequency
- Copies of all advertising, email and social media campaigns mentioning firearms, weapons or calibers
Getting underwritten for firearms accessories
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite firearms accessories. 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 firearms accessories
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 your processor and read its actual restricted listFirst: confirm whether you are in Shopify Payments or applying now. If you are in a Shopify store already, your processor is in your admin under Settings → Payment providers. If you are applying, your processor is determined by your country — see shopify.com/legal/processor-list. Once you have the name, find the processor's restricted-businesses document. For Stripe, this is at stripe.com/docs/connect/restricted-businesses. Do not rely on secondhand descriptions or forum posts. Read the actual list. Your business type may be listed with a carve-out you did not know existed.
- Check whether you meet a documented exceptionRestricted lists often include carve-outs. A category like "adult" may permit age-gating and ID verification. A category like "financial services" may permit licensed brokers but not unlicensed advisors. A category like "gambling" may permit lottery retailers but not online betting. Find the line that describes your business and read every word after it. If there is a condition you can meet — a specific merchant code, a government licence, a regulatory exemption — note it. This is the only path to reapplication on the same processor.
- Reapply with documentation of the exceptionIf you found an exception that applies to you, gather the documentation it requires: a licence, a registration, a certification, a merchant code, proof of age-gating, or whatever the list specifies. Submit a new application to the same processor with that documentation attached and a short note saying: "I believe I meet the exception at [the exact line]. My documentation is attached." Include the reference to the specific exception in the list itself. Do not argue that the rule is unfair. Do not submit a general appeal. The processor's automated screening will reject you again unless you are answering a specific carve-out.
- Get a verified copy of your store — before applying elsewhereIf the processor will not move, you will move to a different gateway. This is the moment to export a full backup of your store, before anything else changes. You need your catalog, your customers, your order history, your SEO metadata, your theme settings, your discount codes — everything. Shopify's CSV export cannot carry metafields, orders, gift card codes, videos, menus, discounts or redirects. That is the strongest reason to move to a new store built around a processor that will accept you: a fresh build with a proper migration handles the things CSV cannot. Get the backup now, while you have access and the store is still live.
- Move to a new store with a processor that accepts your businessOnce you know which processor rejected you, and whether you can appeal it, find a payment gateway that accepts your category. This means a different processor, which usually means a new Shopify store built around that gateway. A migration service can move your catalog, images, SEO data, theme, customers, orders and other data into the new store, then run the migration twice and compare counts to check nothing was lost. The move costs money and time, but it is the legitimate path from a misfit processor to a fit one. You are not hiding anything; you are disclosing your category truthfully to a processor who will accept it.
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
A firearms accessories store's data is dangerous to move because fitment metadata lives in custom metafields. Compatibility data—which optics fit which rail systems, which holsters fit which firearms, which magazines are compliant in which states—is stored as reference fields, lookup fields or text metafields that a CSV export cannot carry. Shopify's standard export also cannot carry metafield data at all. If you move by hand or naive export, every product page renders but the fitment filters and state-compliance logic silently break, so a customer selects a holster for the wrong firearm and you process a return and a chargeback. On a high-AOV category, that is not trivial.
| What you own | How much of it | What breaks doing it by hand | What we do instead |
|---|---|---|---|
| Product images | 7,200images≈ 30 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 | 1,200descriptions≈ 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 | 9,600variants≈ 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 | 14,400metafields≈ 96 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 | 1,643records≈ 6 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 | 45videos≈ 3 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 | 4,500customers≈ 2 hrsCSV import, then cleaning up the rows that fail | By handthe importer works, but marketing consent is the exposure: the CSV carries the current opt-in state and NOT the timestamp or source behind it. Re-opting someone in is a compliance breach, dropping them burns list revenue you paid for, and you cannot prove which happened afterwards. Default-address designation is also lost | Automatedcustomers upserted by email with every address, the default-address designation, and email and SMS consent states and timestamps preserved exactly as they were |
| Order history | 8,200orders≈ 8 hrsa paid third-party importer, plus a day of mapping and reconciliation | By handShopify's own CSV importer cannot create orders at all, so the hours here assume you buy a third-party importer — key them in by hand instead and 9,400 orders is closer to 390 hours, which is why nobody does that and why order history is simply abandoned in most DIY moves. Then support cannot answer a warranty claim, repeat-purchase segments are empty, and every returning-customer flow starts from zero. Getting the mapping wrong duplicates orders or re-dates them to today, and both are worse than not importing at all | Automatedfull order history recreated through the API with line items, properties, customers re-associated, original dates and tracking numbers intact |
| Navigation menus | 3menus≈ 1 hrsabout an hour to rebuild and relink them all by hand | By handmenu items store resource IDs, not paths, so nothing about them is portable — every link has to be re-pointed at the equivalent collection, page or product on the new store | Automatedmenus rebuilt with their nesting, and every item re-pointed at the equivalent object on the new store |
| Discount codes | 95discounts≈ 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 | 103articles & pages≈ 7 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 | 8apps≈ 8 hrsabout 1 hr per app to reinstall, reconfigure and re-test | By handmost app data lives in metafields on your products and customers, so reinstalling the app gets you an empty app: reviews gone, subscription plans gone, loyalty balances gone, bundles gone. Flows and automations have to be rebuilt by hand and re-tested, and anything with its own billing has to be re-subscribed | Automatedthe metafield data your apps rely on migrates with the products and customers it hangs off, so a reinstalled app finds its data waiting instead of an empty store |
See these numbers for YOUR store, free
The figures above are a typical store in your category. The demo scan connects read-only to yours and counts the real thing — every product, variant, image, customer, order and metafield — then tells you exactly what a migration would carry across. No card, and it never writes to your store.
▶ Run the free demo scanDoes this need a new company?
A new legal entity does not help you here. A firearms accessories merchant who has been declined by Stripe carries that history as a person and as a business, and a processor running standard MATCH checks will see it regardless of whether you form a new LLC. If your original store's account was terminated for selling restricted items, a new company with the same person controlling it signals restructuring to avoid compliance, which underwriters treat as higher risk, not lower. The move is fixing the catalog and the claims, then applying to a different processor under your honest business history.
Frequently asked
Which payment gateway will take a firearms accessories store?
The gateway is not the constraint—the merchant account behind it is. Several high-risk acquirers publicly underwrite firearms accessories, and they can front them through Authorize.net, Stripe-alikes and bespoke integrations. What will take you depends on your specific catalog mix, whether you sell magazines and components, your volume and your processing history. Rather than cold-email a dozen ISOs, use the underwriting request form on this page and let brokers who specialize in 2A commerce bid for your business.
What reserve should I expect to carry?
Most firearms accessories merchants report a 5–10% rolling reserve held for 90–180 days. This means if you process £100,000 in a month, £5,000–£10,000 sits in your processor's account and is released in tranches. Some processors tie it to chargeback rates or customer complaints, so if your first 90 days are clean, they may reduce it. Budget for cash flow around this; it is not a penalty, it is standard risk management in high-AOV categories with regulatory complexity.
Will my fitment data and geo-blocking survive a store migration?
No, not through Shopify's standard export. Fitment rules, state-compliance logic and custom metafields are invisible to CSV round-trips. If you migrate to a new Shopify store without a specialized tool, every product copies but the filtering and blocking rules do not, so customers can order incompatible items or prohibited SKUs. Our migration service rebuilds this metadata by interrogating your original store's API and the Shopify metafield layer, then re-applies it in the new store. Standard exports will lose it entirely.
Do I need a new legal entity to apply to a different processor?
No. A new LLC does not reset your payment history or your MATCH listing; a processor running standard checks will see you as the controller of both entities. If your original Shopify Payments account was declined for selling restricted items, applying again with a new company does not solve the problem—it signals you are trying to avoid compliance scrutiny. The fix is changing your catalog and your claims, then applying to a processor that underwrites 2A commerce case-by-case, which they will under your honest business history.
Is there a Shopify Payments prohibited business list I can check?
No. Shopify Payments does not publish a list of prohibited business types. The payment processor for your country publishes one instead. Shopify's terms say the processor decides which categories are supported. If you were rejected, you need the processor's actual list, not Shopify's. You can find your processor at shopify.com/legal/processor-list, then search that processor's website for "restricted businesses".
Why did I get rejected if my business is legal?
Legal status and payment processor underwriting are different things. A processor may restrict a category for compliance, fraud, or chargebacks — not because it is illegal, but because the processor's risk profile does not cover it. Adult services, gambling, CBD, debt settlement and firearms are commonly restricted even where they are legal. The processor makes the call, and legality is not the only factor.
Can I reapply to the same processor?
Only if you have new facts. A processor will not reconsider on identical information. But if the restricted list includes a carve-out for your business — a specific merchant code, a licence requirement, an age-gating requirement — and you can document that you meet it, you can reapply with that evidence. Read the actual list line by line. Many merchants miss the exceptions because they are buried in small text.
What if I open a new store or company?
A new store on the same processor will be screened against the same criteria you just failed. A new company does not change your screening category. The processor is evaluating your business type and category, not your legal entity name. If Stripe rejected your business type as an individual, Stripe will reject it again when you apply as a limited company. The category itself is the issue, not your legal structure.
Can you turn Shopify Payments back on or move me to a different processor?
No. We cannot persuade a processor to accept your category or change their underwriting decision. What we do is help you move your entire store — catalog, customers, orders, SEO data, theme, everything — to a new store built around a processor that will accept your business type. We move the data, you provide the processor. The move is fixed price from £247, and we run the migration twice to compare counts against what was lost.
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 →