Selling self-defense products on Shopify. Payments is the hard part.
Self-defense products are state and country-restricted at the payment layer. Even legal sales require geo-blocking and age verification before processing will consider you.
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.
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 self-defense store's data is dangerous to move by hand for one reason: the compliance metadata lives in metafields. Jurisdictional restrictions, age-gate requirements, product legality notes and shipping-rule references are stored as custom fields that a CSV export cannot carry — so if you copy naively, you lose the rules that prevent illegal sales. On a restricted product, silent data loss is a regulatory liability, not a cosmetic problem.
| What you own | How much of it | What breaks doing it by hand | What we do instead |
|---|---|---|---|
| Product images | 1,680images≈ 7 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 | 280descriptions≈ 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 | 840variants≈ 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 | 2,240metafields≈ 15 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 | 380records≈ 2 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 |
| Customers | 1,200customers≈ 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 | 2,800orders≈ 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 | 15discounts≈ 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 | 20articles & pages≈ 1 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
Those are typical figures for this category. The read-only scan counts what is actually in your store, so you know the real scale before you decide anything. No card, and it works even if your storefront is already offline.
▶ Run the free demo scanWhy it happened — specifically for self-defense products
Stripe, which underwrites Shopify Payments, explicitly restricts stun guns and pepper spray under its "other weapons" policy. The primary trigger is the product category itself — these items are inherently flagged regardless of legality where you operate. The secondary trigger is jurisdiction: legality is state-specific in the US and these items are prohibited outright in much of Europe, which means a processor sees immediate compliance risk. A merchant selling into multiple jurisdictions without proving geo-blocking and age gates looks reckless to an underwriter.
Rule out the easy fix first — then deal with the real one
There is no documented Shopify platform route for self-defense products. What merchants try first is connecting a high-risk processor through a third-party payment app, assuming Shopify's MCC coding will handle the restriction. It does not. Shopify Payments will decline you on policy alone, before any app integration. Your only path is to leave Shopify Payments entirely and apply to an acquirer that explicitly underwrite weapons or restricted goods. That means a high-risk MID, a higher reserve, and application to a provider outside Shopify's native network — it is not a Shopify decision at all, and you are applying cold to a processor who knows they are taking on volatility.
It only helps if all of these are true:
- You must apply to a processor outside Shopify's native payment ecosystem.
- Your store must geo-block or disable checkout in jurisdictions where the product is illegal.
- Age verification must be enforced at checkout, not as a post-purchase manual step.
- You must document your compliance posture in the application — blocking alone is not enough.
- The processor will underwrite your terms of service and product descriptions separately.
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 you actually have to fix
Underwriters do not change their minds because you asked. They change them because the facts changed. For self-defense products, these are the facts that move the decision:
Build geo-blocking and age verification into checkout immediately.
This is the single highest-yield fix. A processor will decline you on policy, then reconsider if you prove you cannot accidentally sell into a prohibited jurisdiction or to someone under 18. Shopify does not provide native geo-blocking, so you will need a third-party app that checks IP location and enforces age gates before payment is requested. Document exactly which app you use and how it blocks: a screenshot of the blocked checkout is what an underwriter will ask for.
Write a state-by-state compliance map and publish it.
Create a simple document listing which US states you will and will not ship to, and the reason — legality of the product in that state. Include a note on international restrictions, especially Europe where many self-defense items are banned outright. This becomes part of your application and proves you understand the landscape, not just the revenue. Add it to your terms of service so there is a trail.
Remove any language suggesting the product is for self-defense against people.
Reviewers will read your product descriptions, blog and marketing looking for claims that imply the product is a weapon. Neutral language is legal in most places where these items are sold, but language that emphasises harm or self-defence in combat reads as inflammatory to a payment processor. Use technical specs, not tactical framing. Avoid comparisons to weapons and avoid testimonials about confrontations.
Verify your processing history is clean.
If you have been declined by a processor in the past year, the new acquirer will find out via MATCH. Be upfront about it in your application — explain what you have changed (geo-blocking, age gates, terms of service) and why you are reapplying now. Silence on a prior decline is what kills a second application.
What underwriting will ask you for
- Proof of geo-blocking and age-verification implementation on your store.
- State-by-state legality map showing where you ship and what you block.
- Copy of your terms of service covering age restrictions and jurisdiction disclaimers.
- Business license or seller permit for jurisdictions where you operate.
- Processing history from any prior payment processor, successful or declined.
- Product liability insurance, if available in your category.
- Compliance manual or procedures document showing how you prevent underage or out-of-jurisdiction sales.
Getting underwritten for self-defense products
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite self-defense products. 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 self-defense products
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.
New company, new merchant account — the honest version
A new legal entity will not help you here. A decline on category policy is not a reflection of your business structure — it is a reflection of the product you sell and the jurisdictions you cannot safely serve. If you have been declined by a processor, that decline is filed against you as a person in MATCH for five years, and forming a new company does not erase it. The only fix is to demonstrate genuine compliance posture to a processor who accepts the category at all.
What a MATCH listing actually is
- A listing lasts five years from the date it is added, then ages off automatically. There is no performance-based early release.
- It lists the principals — name, tax ID, address — as well as the business, which is exactly why a new company with the same owners is not a fresh start.
- Only the acquirer that listed you can remove it, and only in two situations: the listing was made in error, or the reason code was PCI non-compliance and you have since become compliant.
- Reason codes are specific and they matter: excessive chargebacks reads very differently to an underwriter than laundering or illegal transactions.
- It is not a card-network ban. High-risk acquirers knowingly board MATCH-listed merchants — at worse rates, with larger reserves, and with volume caps.
- You are entitled to ask the terminating acquirer whether you were listed and under which code. Do that before you apply anywhere else, because you will be asked.
What a new merchant account requires
The entity
Formation documents, EIN or company number, and a business bank account in the company's name with a voided cheque or statement.
The people
Government ID and personal details for every beneficial owner. Underwriting is done on the humans as well as the company — which is why a new company with the same owners does not present as a new applicant.
The history
Three to six months of processing statements if you have any, plus bank statements. A prior termination is disclosed here. Concealing it is the fraud, not the termination.
The website
A live, compliant storefront: clear billing descriptor, contact details, terms, refund and shipping policies, SSL, working checkout, and no claims that contradict your category.
The product
Supplier agreements, certificates of analysis for anything ingestible, licences for anything regulated, and evidence of how you fulfil.
The numbers
Expected monthly volume, average order value and your chargeback history. Understating volume to get approved is a fast route to a frozen account.
A MATCH screen
Run against both the business and its principals. This is the step that decides the application, and there is no way around it — only through it, by disclosing and finding an acquirer who underwrites anyway.
If you do need a new entity, these are the routes people actually use
Costs and timelines below are indicative and go out of date — treat them as a starting point, not a quote.
Wyoming is the default for an ecommerce LLC: ~$100 to file, ~$60/yr to maintain, no state income tax and strong owner privacy. Delaware is the investor standard and costs $300/yr in LLC franchise tax for governing law most DTC stores will never rely on. If you are not raising money, Wyoming is almost always the right answer.
Move everything for a fixed price
One-time packages — no per-record metering, no quotes. The migration order form unlocks the moment you pay, and the whole migration re-runs a second time before any cutover.
How the migration runs
- Book & pay — fixed price, secure Stripe checkout. The order form unlocks immediately after payment.
- Submit your stores — domains and details in the order form; then provide revocable API tokens in your customer area (we never ask for your Shopify password).
- We migrate everything — your live store keeps selling throughout; it is only ever read from.
- Verified twice — the entire migration re-runs and must change nothing; you get the count-matched verification report before any cutover.
See exactly what would move — before you spend anything
The demo scan connects read-only to your current store and counts every product, variant, image, customer, order and metafield in it, then tells you what a migration would carry across. It never writes to your store, and it works even if your storefront is already offline.
▶ Run the free demo scanIf it has already happened
Whatever Shopify has actually done — disabled the gateway, opened a review, frozen your payouts, closed the store — the recovery differs. Find the one that matches your notice:
Shopify Payments Disabled for a Self-Defense Store? How to Recover
Shopify Payments disabled — what it means specifically for self-defense products.
Shopify Payments Account Under Review for a Self-Defense Store? How…
Account under review — what it means specifically for self-defense products.
Shopify Payments Not Available for a Self-Defense Store? How to…
Application rejected — what it means specifically for self-defense products.
High Chargeback Rate Warning for a Self-Defense Store? How to Recover
High chargeback rate — what it means specifically for self-defense products.
High-Risk Payment Gateway for Shopify for a Self-Defense Store? How…
Finding a high-risk payment gateway — what it means specifically for self-defense products.
Migrate a Shopify Store to a New Account for a Self-Defense Store?…
Migrating to a new Shopify store — what it means specifically for self-defense products.
New Company for a New Merchant Account for a Self-Defense Store? How…
New company, new merchant account — what it means specifically for self-defense products.
Shopify Payouts on Hold for a Self-Defense Store? How to Recover
Payouts on hold — what it means specifically for self-defense products.
Shopify Payments Prohibited Business for a Self-Defense Store? How…
Prohibited business type — what it means specifically for self-defense products.
Shopify Payments Terminated for a Self-Defense Store? How to Recover
Shopify Payments terminated — what it means specifically for self-defense products.
Shopify Store Suspended for a Self-Defense Store? How to Recover
Shopify store suspended — what it means specifically for self-defense products.
Shopify Payments Rolling Reserve for a Self-Defense Store? How to…
Rolling reserve imposed — what it means specifically for self-defense products.
How to Reactivate Shopify Payments for a Self-Defense Store? How to…
Appealing a Shopify Payments decision — what it means specifically for self-defense products.
Frequently asked
Will forming a new company let me reapply to Shopify Payments?
No. Shopify Payments is underwritten by Stripe, and Stripe's policy on self-defence products is categorical — it is not about your business structure, it is about the product. A new entity does not change the product you sell. Your MATCH record follows you personally for five years, so a new company will not erase a prior decline either.
Which payment gateways actually accept self-defense products?
Several high-risk acquirers publicly advertise this category, but which one will take you depends entirely on your geo-blocking setup, your processing history and your volume. Authorize.net on a high-risk merchant ID is one option; others specialise in 2A or restricted-goods categories. Rather than cold-email a dozen, use the quote form on this page and let us connect you.
What happens to my product data if I move stores?
Your compliance metadata — jurisdictional blocks, age-gate rules, legality notes — live in Shopify metafields. A standard CSV export cannot carry metafields at all, so if you move by hand, those rules vanish. The new store renders without them, and you silently lose the barriers that prevent illegal sales. That is why automated migration matters here.
How much reserve should I expect with a self-defense processor?
Processors in this category typically hold 5–10% of your monthly turnover in rolling reserve for 90–180 days. That is higher than mainstream payments, and it reflects the volatility and compliance risk. Ask any potential processor for their reserve policy upfront — it varies widely and affects your cash flow.
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.