Account under review, and you sell self-defense products. Migrate everything to a new Shopify store.
The email arrived without warning: your Shopify Payments account is under review. Checkouts still work. Money still lands. But the language is formal and it asks for documents you may not have ready — bank statements, tax returns, proof of product source, clarity on your business structure. The clock is invisible and no one tells you how long it will take. Here is what changes what you do. This is the moment you still have influence. A review is not a decision; it is an open question. The processor is asking because something triggered a flag — a sudden jump in volume or order value, a rise in chargebacks, documents that did not match, or simply the product category you chose. Your job is to answer the exact question asked, with evidence, and nothing else. Do not volunteer new information or try to rewrite your story. And critically: prepare a copy of your store right now, while you still have full access. If the review clears, you never need it. If it does not, you will have lost the only window where you could have saved it.
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
- "We are reviewing your account to ensure it meets our requirements — please provide documents by [date]"
- Bank statements, tax returns, government ID, or proof of business registration — the list depends on what triggered the review
- Checkouts processing normally while the background review runs, creating false confidence that nothing is wrong
- "Your account remains under review" — weeks or months later, with no clear next step or timeline
- Support responses that repeat the policy without explaining what specifically needs to be fixed
The real deadline is invisible: the date Shopify's or the processor's underwriter makes a final decision. You cannot know when that is, so the clock that matters is the one you control — getting a full backup of your store today, while you have admin access. A review that goes wrong becomes a suspension, and a suspension can become an account closure. Once access is gone, your data is unreachable.
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
Your account is under review because a single SKU triggered a category flag or because volume changed sharply. The reviewer wants to see your geo-blocking posture—which products are available in which jurisdictions, and whether your catalog matches what you are actually shipping. Pull your product pages and filter settings; show that restricted items are blocked in states or countries where they cannot legally ship. If you have a distributor feed, check that the source data does not override your blocks. Answer the specific question about that product or shipment pattern. Do not volunteer that you sell anything else restricted. In parallel, start a copy of your catalog on a gateway that specializes in your category—preparation now means you can move fast if the review outcome is not what you need.
🔞 Requires age verification, and shipping is regulated in its own right
The review probably started with a shipping flag or a missed age-gate somewhere. Processors care about two separate things: your verification method at checkout, and carrier compliance on the label. Check your Shopify settings—does age verification actually run before payment, or after? Are you using a carrier that handles your category in the state where the order shipped? If the review asks about a specific order, pull the shipping label, the verification screenshot, and the carrier's rules for that destination. Answer narrowly about that transaction. While you respond, get a second store live on a gateway that openly takes age-restricted merchants—you do not want to wait for the all-clear if the review goes wrong.
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
- Read the request and answer only that questionDo not assume you know what triggered the review. Read the email carefully and identify the exact documents or clarifications they asked for. If they asked for bank statements showing business revenue, send bank statements — not tax returns, not personal documents, not a general business overview. If they asked about your supplier, name the supplier and provide a wholesale agreement or invoice — not a marketing story about your brand. Do not volunteer information they did not ask for. Every piece of paper you add becomes another thing they can scrutinize, and underwriters look for inconsistencies. Stick to the question.
- Get a verified copy of your store — today, while you have accessThis is the step people skip because the review feels temporary and checkouts are still open. It is not temporary, and access can vanish without notice. A negative review decision is usually followed by an account suspension or closure. Once that happens, admin access can be revoked immediately, and you lose the ability to export anything — catalog, orders, customer data, SEO metadata, theme files, discounts, redirects, metafields. Shopify's own CSV export cannot carry metafields, orders, gift card codes, videos, themes, menus, discounts or redirects. That is why a backup taken during the review, while you still have full control, is the only insurance that works. You will almost certainly not need it. But if you do, it is the difference between a bad month and a dead business.
- Gather any supporting documents they did not ask for but might needWhile you are responding to the stated request, identify supporting evidence you can provide without volunteering it — documents that backstop your answer to their question. If they ask about volume and you have a marketing invoice showing a paid campaign, or a supplier invoice showing you bought stock in bulk to meet demand, keep those nearby. Do not send them unless they ask, or unless your first response does not clear the review and you are invited to provide more. Let them lead on scope. Over-documenting looks like you are hiding something.
- Respond before the deadline, using the communication channel they specifiedRead the email again for the exact submission method and deadline. Send your response through that channel, not through support or a different email address. If they asked you to upload documents via your Shopify admin, do that — it leaves a timestamped record. If they gave you an email address or support ticket, use that. Include a clear note stating what you are submitting and why: "Per your review request of [date], I am providing [documents] which show [specific fact you are answering]." Do not oversell; be factual and brief. Save a copy of everything you send, and the timestamp.
- Prepare for a second gateway before you hear backA review can take weeks or months to resolve, and you cannot know the outcome in advance. Do not wait for a clearing decision to act on your backup plan. Research payment gateways that publicly advertise your product category and accept merchants with histories similar to yours. Stripe, Square, Wise, 2Checkout and others operate alongside or instead of Shopify Payments for many merchants — but approval is not guaranteed, and each has its own underwriting. The time to gather your account information and test integrations is now, while your store is fully functional and you are not under time pressure. If the review clears, you delete the backup and move on. If it does not, you have already removed the panic from the migration decision.
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.
How long does a Shopify Payments review actually take?
There is no published timeline. Merchants commonly report decisions within two to four weeks, but some reviews remain open for months with no communication. The processor does not announce when a decision has been made; you find out either when you receive a follow-up email asking for more information, or when your account status changes without notice. Checking your account settings regularly for status changes is safer than waiting for an email.
What happens to my money during the review?
Payouts typically continue during an active review. Money from orders you process lands in your bank account on your normal schedule. The risk is not immediate loss; it is the outcome of the review. If the review goes against you, that is when payouts stop. The balance may then be held against potential chargebacks or disputes for weeks or months depending on the reason for the suspension.
Will they tell me why they are reviewing my account?
The first email usually says why — it mentions a document request, a dispute threshold, a volume change, or your product category. If it is vague, reply asking for clarity on exactly what the underwriter is concerned about. Be factual and non-defensive: "I want to ensure I address your concern — can you clarify whether this is about my supplier documentation, my transaction volume, or something else?" Sometimes they will detail it; sometimes they will not. Either way, answer what they asked for.
If I cannot find the documents they asked for, what should I do?
Tell them. Do not fabricate or send a substitute. If they asked for a bank statement and your bank account is new, or if you do not have incorporation papers because you operate as a sole trader, say so in your response. Explain what you do have instead, and why. For example: "I do not have formal incorporation papers as I operate as a sole proprietor — my government-issued ID and the business registration attached show my authority to operate." Underwriters understand that not every business has every document type. What they cannot forgive is documents that appear forged or misdated.
Can I appeal if they reject my account?
A review is not the same as an appeal. If your account is rejected after this review, you can ask why — and if the rejection was based on incomplete or outdated information, you can submit a formal appeal. But you cannot appeal a policy. If your product category is on the processor's restricted list, appealing your story will not change the category restriction; it means moving to a processor that accepts it. If the category is legal in your jurisdiction but restricted by the processor, you need a different gateway. A new Shopify store with a different gateway, or a migration to a new platform, is then the real option — not another appeal.
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 →