Shopify Payments terminated, and you sell firearms. Migrate everything to a new Shopify store.
The termination notice is shorter and colder than a deactivation: your Shopify Payments account has been permanently closed. You cannot reapply, cannot appeal, and cannot switch to a different Shopify Payments underwriter because there is only one — Stripe. What makes termination distinct from a deactivation is that you may now be reported to MATCH, the card networks' Terminated Merchant File. This is not automatic, and you will not be told it has happened. MATCH lists the people behind the business as well as the business itself, for five years, and every payment processor screens it when you apply. A deactivated account is a warning. A MATCH listing is a record. Most merchants do not know which has occurred, and that confusion drives the first ruinous mistake: opening a new company and expecting a clean slate. It does not work that way. The move here is not to hide — it is to understand what actually happened, what you can and cannot fix, and which gateways will underwrite your real business model.
Move all of it into a new store, from $247
One-time packages, no per-record metering, no quotes. The order form unlocks the moment you pay, counts are matched against your old store, and the entire migration then runs a second time — the second pass has to create nothing.
What you are looking at
- "Your account has been permanently terminated and may not be reactivated" — with no pathway to appeal or re-apply
- Checkout still functioning for days or weeks, creating the false impression the termination is not real
- A sudden payout freeze with unclear hold periods, sometimes stated vaguely as "under review"
- No statement of whether the termination includes a MATCH report — you are left guessing
- Support responses that repeat the policy without engaging your actual circumstances
Both clocks matter because they move at different speeds and create different pressure. The checkout clock is psychological — it feels like you have time, which is the danger. The payout clock is the real one. Money already collected sits frozen, and every day that passes while you are still using that shop is a day you are not building elsewhere. Act on the assumption that checkout access could end suddenly, not that you have weeks.
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
State-by-state legality and catalog-level geo-blocking are not optional for weapons or weapon-adjacent goods—they are the compliance posture itself. Shopify Payments termination for this category usually follows a policy review, not a chargeback spike. A replacement processor will demand proof that your product catalog is already filtered by state and country law. You cannot migrate to a standard gateway and add blocking later; the blocking must be demonstrated before onboarding. The new processor's underwriting will focus on your technical controls and your ability to stay current as state law changes. That level of sophistication is not available from every acquirer.
💎 High average order value, so fraud and disputes cost more per event
When a high-value business loses Shopify Payments, the termination reason often traces to a single large dispute or fraud event that triggered a policy review. Your reserves and chargeback ratios are sized against exposure, and losing processing access while managing that exposure is a genuine cash crisis. A new processor will require proof of fraud controls, dispute resolution history, and possibly higher reserve percentages or rolling reserves. Do not assume the new underwriting will be faster because your business is higher-value; underwriters price larger transaction values more carefully, not less. Your migration plan must account for a potential funding gap while reserves are re-negotiated.
📦 Thousands of SKUs, deep variant matrices, distributor feeds
Shopify Payments termination with thousands of SKUs and variant matrices is a migration crisis because a hand-rebuild is impossible. Your product data, SEO metadata, images, and variant relationships must move intact or you rebuild from scratch, losing search rankings and customer trust. Shopify's own CSV export cannot carry metafields, videos, themes, menus, discounts or redirects—the detailed structure is inaccessible through standard tools. The new processor you choose must support an API-driven data migration, not manual import. A Shopify-to-Shopify migration service can move your entire catalog and re-run the migration twice to compare counts, but hand-verification at scale is infeasible. Catalog integrity is not negotiable; build your processor decision around who can support it.
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
- Establish whether you are on MATCH before you actYou need to know what actually happened, because the next three steps depend on it. A Shopify Payments termination does not automatically trigger a MATCH report — Stripe may terminate an account without reporting it to the card networks. The only way to find out is to check the MATCH database yourself. You can query MATCH through third-party screening services or by applying for a merchant account with a new processor and asking them to run a check. If you are listed, you are listed for five years from the termination date and every acquirer you apply to will see it. If you are not listed, the termination is local to Shopify and Stripe, and your options are much broader. This step takes a few days and it determines everything that follows.
- Get a verified copy of your store while you have access — todayThis is the step with a deadline you do not control. A termination means checkout will eventually close and admin access may follow. Once that happens, there is no API, and without an API your catalog, orders, customer list, consent records and every piece of metadata your theme references are unreachable. Not deleted — just gone from your control. Shopify's own CSV export cannot carry metafields, metaobjects, orders, gift card codes, videos, themes, menus, discounts or redirects, which means a simple download is incomplete. You need a third-party migration tool to pull a true copy, or a developer to script the API before the access ends. If you own gift card codes, know now that they cannot be read through any Shopify API by anyone — you can only re-issue them. Start this today, not after checkout closes.
- Decide whether to appeal or move onIf you are not on MATCH, an appeal is worth exploring, because the termination may reverse and you get your Shopify Payments account back. The appeal goes to Stripe through Shopify support, and Stripe's answer is final. If you are on MATCH, the appeal is not the move — the move is migration, because no other processor will take you while you are listed. Waiting out the five years is passive and it leaves your money frozen. Moving to a new entity is the move people suggest, and it is the move that fails: MATCH follows the people, not the company. A new business with the same beneficial owner does not present as a new applicant to any processor screening MATCH. That is not a legal opinion — it is how the system works. The right reason to form a new entity is structural — a genuine operational separation — never to evade a record.
- If you are not on MATCH, migrate to a gateway that accepts your categoryNot all payment processors screen the same way, and some will underwrite a business that Stripe will not. Gateways that publicly advertise support for higher-risk categories include Wise, Stripe Connect partners in your category, and alternative processors specializing in your industry. Never assume acceptance — apply truthfully, with your full transaction history, and let the underwriter decide. Build your new store on the new processor's infrastructure before you lose access to your Shopify export. You are moving your entire operation: catalog, images, descriptions, SEO metadata, theme, products, variants, metafields, videos, customers, orders, menus, redirects and discounts. A complete migration takes time, and you do not have much of it. This is where we come in: a fixed-price migration service that pulls your store into a new platform, re-runs the full export a second time, and compares counts to catch what moved and what did not. Nothing is ever lost in a migration — but some things are commonly missed, and we are the tool that finds them.
- If you are on MATCH, build your new business on a processor outside the card network screening loopMATCH is screened by every acquirer licensed to take cards. If you are listed, traditional payment processors — including Stripe, Shopify Payments, Square and most banks — will decline you. Your options narrow to two: processors that do not screen MATCH (typically crypto or alternative rails), or waiting out the five-year listing period. If you choose the latter, that five years starts from your termination date, not from today. In the meantime, your money is frozen and your business is paused. If you have been terminated unfairly or as a result of a category misidentification, consider legal counsel — the card networks do take appeals, and some merchants have won reversals. That is contested ground and worth exploring with a lawyer, not a migration service. Our role is to move your store when you have a destination. If you do not have one yet, that is the conversation to have first.
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.
Why can't I just open a new company and reapply to Shopify Payments?
Because MATCH does not list only the company — it lists the people behind it for five years. If you are the beneficial owner of the terminated account, every processor screens you personally, and a new company with your name on it presents the same way. A new entity is the right move for structural business reasons, but it is not a way to look like a different applicant. Anyone selling it to you that way is selling fraud, and it will not work.
How do I know if I'm on MATCH?
Shopify will not tell you. You can query the MATCH database through third-party screening services, or apply to a new processor and ask them to run a check when they decline you. If you are listed, every detail of your termination is there. If you are not listed, the termination is contained to Shopify and Stripe, and you have clearer options for migration.
Can I appeal my termination to Shopify Payments?
The appeal goes to Stripe, Shopify's underwriter, and it succeeds only if you can show a factual error — a misidentified category, a misread of your transaction history, or similar. If Stripe terminated you because your business model itself does not fit their underwriting, no appeal changes that. Stripe publishes no timeline for review and the answer is final.
What happens to my money when Shopify Payments is terminated?
It freezes pending resolution of the underwriting review. There is no published hold period — it can be weeks or indefinite. If you are also on MATCH, the freeze can last years. Once the review closes, you either get access restored and a payout scheduled, or you forfeit the balance. Check your termination notice for the specific details of your hold.
Can you turn my Shopify Payments back on?
No processor can. We are a migration service — we move your store and its data into a new shop built on a gateway that will accept you. We cannot turn Shopify Payments back on and we cannot help you evade MATCH. What we do is extract your complete store — catalog, orders, customers, metadata — before access closes, and rebuild it somewhere you can actually sell. That is only the move if you have a destination processor that will underwrite you truthfully.
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 →