Appealing a Shopify Payments decision, and you sell self-defense products. Migrate everything to a new Shopify store.
The decision came down by email, and the temptation is to write back immediately. Stop. Before you draft anything, you need to know what you are actually appealing — because Shopify Payments decisions split into two different categories, and only one of them can be reversed. If the decision turned on a fact — a mislabelled product, an unclear payment descriptor, a missing licence, or disputes you can now prove were fulfilled — then evidence can change the outcome. If the decision turned on your product category itself, then no reviewer has authority to except you from the processor's policy, and the appeal will fail no matter what you write. The difference matters because merchants who appeal the second kind waste weeks waiting for silence while their store runs on checkout alone, unable to plan around the real timeline. So diagnose first. Write second. Start plan B on the same day you appeal, not after.
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
- Email saying Shopify Payments cannot support your business, with no detail on which fact or category triggered the review
- Checkout still working for days or weeks after Payments deactivated, creating false hope that the problem might reverse itself
- Support responses repeating the same brief reason without elaborating on what specifically was found
- Requests to provide evidence met with 'appeal to Stripe' — passing the merchant to Shopify's processor without direct contact
- Radio silence lasting weeks after submitting an appeal, with no published timeline for a response
The checkout clock is a trap. It creates the impression you have time to appeal while payouts are actually frozen. The real deadline is the one Shopify does not advertise — when it decides whether to review your store a second time and close the whole account. That usually comes weeks in, which is why plan B must start immediately, not after the appeal fails.
Why 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 this means for a business like yours
🎯 Weapons or weapon-adjacent, with state-by-state legality
Weapons and weapon-adjacent goods live under state and country legality that is not uniform, and Shopify Payments prices that legislative complexity as unmanageable. An appeal based on 'it's legal where I ship' usually fails because the processor avoids the jurisdiction-by-jurisdiction audit. Your appeal succeeds only if you can show catalog-level geo-blocking that prevents sales to prohibited states or countries and auditable proof it works. If you do not have that blocking in place, the appeal will take weeks and likely fail anyway. Build the geo-blocking first, then appeal with evidence of it.
🔞 Requires age verification, and shipping is regulated in its own right
Age-restricted merchants appeal on verification infrastructure and shipping compliance—proof that your carrier screening, ID checks and adult signature enforcement actually work. Shopify Payments reviews both the product policy and whether you can operationally stop underage sales. An appeal works if you can show those systems are in place and auditable. It fails if the processor doubts you can hold the line across all states and carrier networks, or if verification is simply not built into your store yet. That takes weeks to design and test. Appeal if you have compliance; build it while you wait.
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.
The recovery playbook
- Identify whether the decision turned on a fact or a categoryRead the email carefully. It will say something like 'cannot support' or 'incompatible with our policies'. The next step depends on which it is. If the decision mentioned a specific product, descriptor, licence, or type of dispute, then it may be a fact problem — and facts can change. If it mentioned your business type, industry, or product category as the reason, then no reviewer has authority to except you. Calling Shopify support at this stage usually produces the same email language again, so focus on diagnosis first.
- Gather the evidence for one written appeal — and do it todayThis is the step with a deadline you do not control. Do not wait for the appeal result. Do not assume checkout will keep working while you appeal. Collect the specific evidence that addresses the decision: corrected product screenshots, updated payment descriptors, licence documents, fulfilment records, customer consent, delivery proof. File them all in one place so you can reference them in writing. Set a deadline for the appeal to arrive with Shopify within 48 hours — not because speed guarantees anything, but because waiting is a sunk cost that keeps you from building plan B.
- Appeal once in writing, with only the evidence that counters the decisionWrite directly to the email address that notified you. Be specific: 'You cited [reason]. Here is the evidence that [corrected fact].' Attach or link the documents. Do not argue that the decision is unfair, do not ask for another review, do not promise future compliance. Processors see hundreds of these, and generic appeals are routed as low-priority. You are simply putting the fact on record. If the decision was based on a category prohibition rather than a fact, say so in your diagnostic email to yourself and move on.
- Start plan B the same day: migrate to an accepting gatewayDo not treat the appeal as your plan. Treat it as something you put in motion and then ignore while building what actually survives. A new store on a different payment processor — built into a fresh Shopify domain or migrated into one — with a provider that underwrites your category is the real recovery. The migration takes days, costs a fixed price, and runs in parallel to your appeal. Many merchants never hear back from the appeal. Those who moved the same week have zero downtime in the one business metric that matters: can they take payment.
- If the appeal succeeds, shut down the new store or keep it running dual-processorSuccess is rare and usually takes weeks. If it comes, you will be notified that Shopify Payments is re-enabled. At that point you have a choice: move back to Payments and deactivate the other gateway, keep both running, or stay on the new processor. Dual processing costs more but insures against a second deactivation. Many merchants who have been through this once choose to stay dual, or to stay with the accepting gateway entirely, because the reputational cost of promising customers they can take payment and then freezing is higher than the processing fee difference. That is a business call you make once you are not in crisis mode.
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
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 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.
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.
Can Shopify Payments be turned back on if I appeal?
Only if the decision was based on a fact — a mislabelled product, unclear descriptor, missing licence, or disputed orders you can now prove were fulfilled. If the decision turned on your category being on the processor's prohibited list, then no reviewer has authority to make an exception, and the appeal will not change it. The decision tells you which it is if you read it carefully.
How long does an appeal take?
There is no published SLA. Merchants commonly report anywhere from a few weeks to no response at all. Some receive a yes or no answer; others receive the same generic reason again without elaboration. The lack of transparency is why you should not wait for the result before building a backup plan. Filing the appeal and then moving to a different processor in parallel is the only timeline you control.
What evidence actually works in an appeal?
Evidence that addresses the specific decision, not the general principle. If you were rejected for mislabelled product names, show the corrected listings. If for unclear payment descriptors, show what the new descriptor is. If for missing licences, provide the document. If for disputed orders, provide proof of fulfilment — tracking, delivery signature, or customer communication proving the goods were as described. Generic promises to comply do not work because the processor's decision was based on documented risk, not intent.
What if Shopify Payments is re-enabled but then disabled again?
This pattern is common. Merchants report being re-enabled, trading for a few weeks, and then receiving a second deactivation notice. If this happens to you, the underlying decision was likely not actually overturned — it was suspended pending more observation. This is why having a backup payment processor in place before the first appeal is worth the setup cost. You are no longer betting the business on a single gateway.
If I move to a different processor, do I have to close my Shopify store?
No. Your store stays live. You simply connect a different gateway for payments — Stripe, Square, PayPal, Braintree, or another processor that underwrites your category. The store itself, your catalog, your customers, and your orders are unaffected. If your new processor later deactivates you as well, migration to a third processor is the same move again. The goal is to find a gateway whose underwriting actually fits your business model and stick with it.
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 →