Shopify Payments disabled, and you sell firearms. Migrate everything to a new Shopify store.
The email is short and it reads like a verdict: Shopify Payments has been deactivated, payouts stop, and support points you at the Terms of Service. Here is the part almost nobody tells you, and it is the only part that changes what you should do today. Your store has now been flagged. Shopify Payments is underwritten by Stripe, so your product category tripped a payment processor's policy — but the review happened against your account, and the account keeps that record. Bolt on a third-party gateway and you have changed who settles your money. You have not changed what Shopify knows about your store, and its terms allow it to act again at any time, on notice. Merchants report the same sequence constantly: payments off, a few more weeks of trading, then a second review that closes the store for good. So treat this as step one of two. Get a full copy of your store somewhere you control, now, while you can still log in — even if it is only a backup plan you never use.
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
- "Shopify Payments is no longer supported for your business type" — with no detail about which part of your business
- Payouts stopped, while orders that already went through keep needing to be fulfilled
- Checkout still working for days or weeks afterwards, which feels like a reprieve and is really a countdown
- Support declining to discuss the decision, and pointing at the Terms of Service
- A request for invoices, supplier agreements or fulfilment evidence that arrived shortly before the shutdown
- And the one nobody warns you about: your account now carries a risk-review record that a new gateway does not erase
The hold is the visible problem. The stall is the expensive one — every day without a working checkout burns the ad spend that produced the traffic anyway. But the risk nobody warns you about is the third one: your account has now been through a risk review, and it keeps that record. A new processor changes who settles your money. It does not change what Shopify knows about your store, and the terms let Shopify act again at any time on notice. Assume this is step one of two, and get a copy of everything out while you can still log in.
Why it happened — specifically for firearms
Stripe, the processor behind Shopify Payments, lists firearms and weapons as restricted with limited availability. The primary trigger is that you are selling a product category Stripe does not underwrite by default. The secondary trigger is the shipping model: if your checkout does not enforce FFL-to-FFL transfers or state-level geo-blocking, you fail the underwriting before it even reaches compliance review. Stripe's policy is that lawful retail is boardable only through specialists, and only if you can prove licensing and workflow controls.
Rule out the easy fix first — then deal with the real one
Rule this out first, because Shopify documents no route for firearms. What merchants try is applying to Shopify Payments anyway, citing their FFL license—and that fails because the restriction is structural to Stripe's risk model, not a licensing question. The path that sometimes works is to find a high-risk acquirer who specializes in 2A retail, apply with documented proof of your FFL, state resale licenses, and a shipping workflow that enforces dealer-to-dealer transfers. That application is permission to apply only; the acquirer runs their own underwriting on your catalog, your state compliance and your processing history. Most declines at that stage come from either inadequate proof or a shipping model that does not enforce FFL gates.
It only helps if all of these are true:
- You hold a current, verifiable FFL license in a US state.
- Your checkout or fulfillment system enforces FFL-to-FFL transfers or state geo-blocking.
- You can document that you do not ship to prohibited states or persons.
- Your product catalog does not include fully automatic weapons, which are federally prohibited for civilian retail.
- You have no prior payment processing declines or chargebacks tied to weapons or compliance.
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 sit on the processor's restricted list even where the product is entirely legal to sell, and the legality itself varies by state. Underwriters look for whether your catalog separates the freely-shippable accessories from the items that need a licensed intermediary, whether you geo-block the states that prohibit specific items, and whether your listings avoid the language that gets read as facilitating harm. Fitment-heavy catalogs also need the variant structure intact — which matters a great deal when the store has to move.
💎 High average order value, so fraud and disputes cost more per event
High order values change the arithmetic of every review. A single disputed order can put you over a threshold that a low-value store would take hundreds of chargebacks to reach, and reserves are sized against your exposure rather than your revenue — so expect a bigger one, held longer. Underwriters will want to see delivery evidence and signature confirmation for high-value shipments, and they will look closely at any sudden increase in average order value, because that pattern is also what fraud looks like.
📦 Thousands of SKUs, deep variant matrices, distributor feeds
A large catalog does not affect the underwriting decision much, but it dominates everything that happens afterwards. Thousands of SKUs with deep variant matrices, distributor-fed data and years of accumulated metafields are exactly what does not survive a hand-rebuild — and a store this size is where merchants discover, weeks in, that the CSV route silently dropped the fields their theme renders from. If a move is on the table, the size of your catalog is the single biggest factor in how it should be done.
What you actually have to fix
Underwriters do not change their minds because you asked. They change them because the facts changed. For firearms, these are the facts that move the decision:
Document your FFL licensing and state-level shipping controls.
This is the single highest-yield fix because it is the thing specialists cannot board without. Gather your current FFL license copy, any state resale permits, and a written or technical description of how your checkout or fulfillment enforces dealer-to-dealer transfers. If you are hand-shipping and relying on customer honesty, you will be declined. If you use an FFL-network platform (GunBroker model, for example), document that integration. Underwriters need to see the gate, not just hear that you respect it.
Audit your product descriptions for state-prohibited items.
Remove or geo-block any products that are prohibited in states where you currently ship or where your checkout does not block them. This includes fully automatic weapons (federally prohibited for civilian sale), short-barreled rifles where state law prohibits them, and any other weapons your state restricts. Create a state-by-state compliance grid showing which products you sell in which states, and which states you have completely blocked. Underwriters will cross-check this against your fulfillment data.
Remove any marketing language that flags age-gating failures.
If your product pages or checkout imply that minors can purchase (no age verification gate, no disclaimer language, or marketing that targets under-18 audiences), fix that before applying. Firearms have federal age limits: rifles and shotguns 18+, handguns 21+. Make sure your checkout enforces age verification (either manual review or a third-party age-gate service), and that your product pages clearly state the age requirement. Underwriters will scan for this instantly.
Compile your processing history and chargebacks to be transparent.
If you have been declined by Shopify Payments, Stripe, or any other processor, or if you have a history of chargebacks or disputes, gather those records now. Specialist acquirers run background checks on processing history, and declining to mention a prior decline will cause them to decline you again for misrepresentation. If your history is clean, state that plainly. If it is not, explain what happened and what you have fixed since then.
What underwriting will ask you for
- Copy of your current FFL license and any state resale or dealer permits.
- Proof of your shipping and transfer workflow—screenshots of your checkout, fulfillment instructions to customers, or integration with an FFL-network platform.
- Your product catalog with images, descriptions and any age-gate or compliance language.
- Bank statements for the last 3–6 months showing lawful business revenue.
- Processing history from any prior payment processor, including reason codes for any declines.
- State-by-state compliance checklist showing which states you ship to and which you block.
- Your business formation documents and UBO (Ultimate Beneficial Owner) verification.
Getting underwritten for firearms
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite firearms. 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
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
- Work out which layer actually said noThere are three, and they have completely different consequences. If Shopify Payments declined you, your store is still open and you need a different gateway. If the Shopify platform suspended you under the Acceptable Use Policy, no gateway on earth fixes that. And if a third-party gateway's acquiring bank dropped you, that is a third decision with its own appeal route. Read the notice for which entity is speaking before you spend a day fixing the wrong problem.
- Get a verified copy out while you still have access — todayThis is the step people skip, and it is the only one with a deadline you do not control. A payments deactivation is not the end of the process. It is the first thing that happened. Your account has now been through a risk review and it keeps that history — the flag does not leave when the gateway does. Bolting on a third-party processor changes who settles your money; it does not change what Shopify knows about your store, and Shopify's own terms let it act again at any time, on notice. Merchants report exactly that sequence constantly: payments off, trade on for a few weeks, then a second review that closes the store. And if the store closes, admin access can go with it. That is the part that turns a bad month into a dead business, because with no admin there is no API — and with no API your catalog, your order history, your consent timestamps and every metafield your theme renders from are simply gone. Not deleted; unreachable, which is the same thing. Shopify's own CSV export cannot carry metafields, metaobjects, orders or gift card codes, so "I'll just export it" is not the plan you think it is. Take a full, verified copy into a store you control now, while you can still log in. If you recover, you have lost nothing but the price of a migration. If you do not, you still have the business.
- Fix the thing that triggered itUnderwriters do not reverse a decision because you asked nicely; they reverse it because the facts changed. That usually means product labelling and claims, an age or geography gate you were not running, a clearer billing descriptor, published shipping and refund terms, or evidence of fulfilment for the orders that generated disputes. Unglamorous, and the step that decides whether the next processor keeps you — because whatever tripped the first review will trip the second one too.
- Get underwritten somewhere that wants your categoryHigh-risk acquiring is an entire industry that exists precisely for businesses Stripe declines. You apply as what you are, disclose the termination, and expect worse terms than a low-risk merchant gets — a rolling reserve, higher rates, a volume cap. On Shopify the practical route is a high-risk merchant account fronted by a gateway Shopify supports natively, which keeps checkout on your store rather than sending customers off-site.
- Decide whether you need a new entity — honestlySometimes you genuinely do: a new legal entity is the right answer for an acquisition, a partner split, a change of jurisdiction, or separating a high-risk product line so it can never take your main brand down with it. Sometimes it is being sold to you as a way to look like a different applicant — which is a completely different thing, and is fraud. The section below is blunt about which is which.
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 store's data is dangerous to move by hand because shipping and compliance metadata lives in metafields and custom product fields. Your FFL-gating rules, state-level restrictions, age-verification flags, and any caliber-to-state mapping are all either in metafields or in non-standard product fields that a CSV export cannot carry. If those are lost or silently point to the old store's system, you will ship products to blocked states or to underage customers, and the acquirer will terminate you immediately. The migration must preserve every compliance-linked metafield and every custom shipping rule.
| What you own | How much of it | What breaks doing it by hand | What we do instead |
|---|---|---|---|
| Product images | 6,400images≈ 27 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 | 800descriptions≈ 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 | 2,400variants≈ 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 | 4,800metafields≈ 32 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 | 932records≈ 3 hrsredirects one at a time, plus a handle audit | By handany handle that changes becomes a dead URL with no redirect, and existing 301s are not in the product CSV at all. Years of accumulated ranking and backlinks end up pointing at pages that no longer resolve — the most expensive thing on this page to get wrong, and the slowest to notice | AutomatedSEO titles, meta descriptions and handles carried across, and every existing 301 recreated, so nothing that used to rank starts 404ing |
| Your custom theme | 1theme≈ 6 hrs2–10 hrs depending on how customised it is | By handa theme is not just its files. The settings, section content and block ordering are stored against the store, so a file copy gives you the layout and none of the content. Hardcoded asset URLs and tracking snippets also still point at the old store | Automatedyour live theme pulled and pushed as-is, then scanned for tracking snippets and hardcoded URLs that need re-pointing |
| Customers | 2,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 | 4,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 | 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 | 12articles & pages≈ 48 minrecreated 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 firearms merchant does not need a new legal entity to process through a specialist acquirer. If you have been declined by Shopify Payments or Stripe, opening a new company will not reset that decision—both MATCH and the specialist's own underwriting follow the person, not just the business name. Your FFL is tied to your personal SSN or your business entity; a new shell company will not change that. Apply with your current structure and be transparent about your history.
Frequently asked
Why was I declined by Shopify Payments if I have a valid FFL?
Shopify Payments is underwritten by Stripe, and Stripe's policy treats firearms as restricted—not prohibited, but restricted with limited availability. That means Stripe does not board firearms merchants by default through Shopify. An FFL license proves you are legal to sell; it does not change Stripe's risk decision. Specialist acquirers do board FFL dealers, but they require proof of your license, your shipping workflow, and your compliance controls. Stripe's blanket restriction is structural, not a licensing gap.
Which payment gateway will actually work for my gun store?
Several high-risk acquirers publicly advertise firearms underwriting and will connect you to gateways Shopify supports natively—Authorize.net on a high-risk MID, or gateways from specialists like PaymentCloud and Easy Pay Direct. Which one approves you, at what rate and with what reserve, depends entirely on your FFL status, your processing history, and whether your shipping workflow enforces FFL-to-FFL transfers. Rather than cold-email each one, use the quote form on this page to describe your operation and get matched to active underwriters.
What happens to my product data if I move to a new payment processor?
Your product catalog, images and descriptions move cleanly. Your compliance metadata does not. Your FFL-gating rules, state-level geo-blocks, age-verification flags and any custom shipping logic are all stored in metafields or outside Shopify's standard product schema. A CSV export will not carry them, so they must be migrated by hand or through a custom script. If they are lost, your new store will ship to blocked states or to customers below the federal age limit, and your acquirer will terminate you. This is why a hand migration of a firearms store is almost always incomplete.
Will my reserve be huge?
Yes, typically. Firearms merchants commonly report rolling reserves of 10–20% held for 90–180 days. That is because chargebacks and disputes are common in this category (high AOV, high-value items, sometimes buyer's remorse or shipping disputes). Budget for that reserve from day one, because it will be in your contract and it will affect your cash flow. Some acquirers will lower the reserve if your processing history is clean and your volume is high; most will not negotiate until you have proven yourself.
Can I get Shopify Payments reinstated?
Occasionally, when the decision rested on a fact you can correct and evidence — a mislabelled product, a missing licence, an unclear descriptor, fulfilment records for disputed orders. If your product category is on the payment processor's prohibited list, no reviewer has the authority to grant an exception, and waiting for one costs you the selling window. Appeal once in writing, then start the alternative the same day.
How long does Shopify hold my money after Shopify Payments is disabled?
A standard hold against chargeback risk runs up to 120 days from the last transaction, because that is roughly how long a cardholder has to dispute one. It can run longer where Shopify suspects illegitimate commerce. The held balance is still yours and is normally released after the window; it is the loss of a working checkout, not the hold itself, that does the real financial damage.
Do I need a new Shopify store, or just a new payment gateway?
If only Shopify Payments was disabled, your store is fine — you need a third-party gateway whose acquiring bank accepts your category, and nothing has to move. You need a new store when the platform itself closed the old one, when you are separating a high-risk product line into its own entity, or when a new provider requires a clean install. Those are genuinely different situations and it is worth being sure which one you are in before you migrate anything.
Will opening a new company get me a new merchant account?
Not by itself, and this is the most important thing on this page. MATCH — the card networks' terminated-merchant file — lists the people behind a terminated business as well as the business, for five years, and every acquirer screens it. A new company with the same beneficial owner does not present as a new applicant. A new entity is the right answer for real structural reasons; it is not a way to look like someone else, and anyone selling it to you that way is selling you fraud.
Can you get my payments turned back on?
No, and nobody outside Shopify and its payment processor can. We are a migration service: if you need to move to a new store built around a gateway that accepts you, we move everything into it — catalog, customers with their consent states, full order history, metafields, theme, redirects — and prove nothing was lost by re-running the entire migration a second time.
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 →