High chargeback rate, and you sell firearms accessories. Migrate everything to a new Shopify store.
The warning comes from your processor, not your customers: your chargeback or dispute rate has climbed above their threshold, and they are putting your account under review. This is not a suspension yet. It is a formal notice that you have entered a monitoring programme run by the card networks themselves—Visa and Mastercard track dispute rates at every merchant, and when the rate hits a certain point, the networks impose fines on the acquiring bank, not on you directly, but the bank passes that cost down. The acquirer acts before the threshold bites because the alternative is to hemorrhage money on your account. But here is what almost nobody explains: a high chargeback rate is almost never a processor problem or a Shopify problem. It is a real pattern in your orders. Customers are not recognizing the charge, or they ordered something that did not arrive, or the description on their bank statement is so unclear they assume fraud. Until you fix what actually happened in those orders, you will carry this pattern to the next processor. So the move is not to hunt for a more lenient gateway. It is to find and fix what your customers are disputing.
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 is enrolled in a card network dispute-monitoring programme" — with a rate percentage but no clear explanation of what changed
- A notice of financial penalties per dispute, or a mandatory reserve holding back a percentage of payouts
- Support refusing to process refunds for customers who have already filed chargebacks, citing policy
- A timeline: "Reduce your dispute rate to X% within 90 days or your account will be escalated"
- Email language citing your billing descriptor, delivery confirmation or customer communication as a risk factor
The clock that matters is the one the card networks set: roughly 0.9%–1.5% of transactions. Once your rate hits that, the networks themselves penalize the acquiring bank per dispute, which forces fast action. You cannot negotiate a network threshold, so the real deadline is proof that you have fixed the underlying problem—clear billing, trackable delivery, and responsive support before customers dispute.
Why it happened — specifically for firearms accessories
Shopify Payments is underwritten by Stripe, and Stripe's policy on firearms and firearms parts is categorical: the business is restricted, and within that restriction certain items—magazines above state capacity limits, components that function as receivers, and parts marketed for assembly—live in a prohibited subcategory. The secondary trigger is guilt by association. A processor reviewing your store sees magazines, optics and holsters together. They do not separate the low-risk items from the high-risk ones; they see a firearms merchant and apply the blanket policy, so your compliant optics get caught by the same decline as your restricted magazines.
Rule out the easy fix first — then deal with the real one
Shopify does not document a route for this category. There is no attestation, no third-party integration and no declared path. What merchants try first is applying directly to Stripe or Shopify with a letter explaining that most of their catalog is legal and shippable. This fails because Stripe's policy is not a review process—it is a category exclusion. An individual appeal rarely changes it. Your alternative is moving to an acquirer that underwrites firearms accessories as a vertical: they run the compliance separately and accept case-by-case, so your store is judged on what you actually sell, not on category proximity. This requires moving payment gateways and, usually, payment processors entirely.
It only helps if all of these are true:
- No documented Shopify route exists; you must change processors.
- An alternative processor's underwriting team must approve your product list before you apply.
- Your store must geo-block any item prohibited in the customer's shipping state.
- You must carry insurance and licenses where your jurisdiction requires them for the items you sell.
- Magazine capacity limits and receiver components must be removed or fully compliant with state law.
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
Weapon-adjacent businesses face heightened scrutiny on disputes because processors already price legislative risk into your account. A high chargeback rate accelerates that risk calculation: the card networks' dispute-monitoring programmes trigger at roughly 0.9%–1.5% of transactions, and once enrolled you pay per-dispute penalties on top of your base rate. You cannot fix this by switching gateways alone if the root cause is real customer dissatisfaction or delivery failure. Billing descriptor clarity and delivery confirmation are your foundation. After that, responsive customer support before disputes network is essential—handle refund requests and shipping concerns immediately, not after a chargeback appears. The dispute rate will follow you unless you actually fix the underlying cause.
📦 Thousands of SKUs, deep variant matrices, distributor feeds
A high chargeback rate across thousands of SKUs is almost impossible to debug because you cannot isolate which products or variants are generating disputes. The card networks' dispute-monitoring programmes trigger at roughly 0.9%–1.5% of transactions, and once enrolled you pay per-dispute penalties. Your scale works against you: rebuilding your catalog in a new system is expensive and time-consuming, so you cannot afford to migrate twice. Start with the basics: billing descriptor clarity, delivery confirmation, responsive support. Then segment your dispute data by category, variant, and fulfillment type to find the pattern. Deploy dispute-deflection tooling immediately. A catalog migration is not the fix—understanding which part of your offering is driving the rate is. Only then should you move gateways.
💎 High average order value, so fraud and disputes cost more per event
For high-value orders, a single chargeback is material to your reserves and profitability. When your chargeback rate climbs, the card networks' dispute-monitoring programmes kick in at roughly 0.9%–1.5% of transactions—meaning penalties accumulate fast on expensive orders. Your processor will act before the rate feels catastrophic to you, because network penalties are their risk too. A clear billing descriptor is your cheapest defence: if the cardholder recognizes the charge, disputes drop. Delivery confirmation is non-negotiable for high-value items. Responsive support before disputes network—handling questions, shipping concerns, refund requests immediately—stops chargebacks dead. Dispute-deflection tooling and these three basics are what keep you in business when order values are large.
What you actually have to fix
Underwriters do not change their minds because you asked. They change them because the facts changed. For firearms accessories, these are the facts that move the decision:
Map and geo-block every restricted SKU by state.
This is the single move that makes most firearms accessory stores fundable. Magazines above state capacity limits, certain receiver blanks and binary triggers are prohibited in specific states. You must identify every restricted item, look up the laws in your top 20 shipping states, and then configure Shopify to block checkout for those postcodes. A processor reviewing your store will ask for proof—screenshots of your checkout rule or a technical report showing which postcodes see which products. This is not optional; it is the foundation of your compliance.
Audit every product description for assembly and manufacturing language.
Parts sold as 'components to complete your build' or 'lower receiver blanks' trigger prohibited status even if the item itself is legal. A processor reads 'assemble' and sees you as selling a way around dealer licensing. Rewrite descriptions to be functionally accurate but never suggest assembly, manufacturing or circumventing requirements. 'Precision-machined component' is defensible; 'everything you need to finish your lower' is not. Check your email campaigns and social media too; a single post advertising 'build your own' can sink an underwriting application.
Gather proof of insurance and licensure.
Your underwriting file must include commercial general liability insurance naming firearms product risk, and copies of any federal firearms licenses (FFL), business licenses or state permits you hold. If you do not hold the licenses you should hold—if you are selling components that require dealer licensing but you do not have one—state that plainly and remove those SKUs. An underwriter will find out. It is better to disclose it yourself and prove you have complied than to let them discover it in a chargeback dispute eighteen months from now.
Document your distributor feeds and dropship terms.
Firearms accessory merchants often work with distributors and dropshippers. Pull your contracts and confirm they allow retail resale and that they specify your compliance obligations—particularly around magazines and restricted components. Some distributors will not ship certain items to certain states; you must know this and map it into your geo-blocking. List your top 3–5 suppliers and their restrictions in your underwriting submission. Transparency here signals you are running the category seriously, not as a side venture.
What underwriting will ask you for
- Product catalog with full SKU descriptions, including whether each item requires a license or permit in your key shipping states
- Magazine inventory list with state-by-state capacity limits and geo-blocking proof for each SKU
- Proof of insurance covering product liability for firearms accessories
- Certificate of occupancy or business lease showing your retail or warehouse location
- Shipping and handling policy clearly stating which items are not shipped to certain states
- Bank statements for the last 12 months showing transaction volume and frequency
- Copies of all advertising, email and social media campaigns mentioning firearms, weapons or calibers
Getting underwritten for firearms accessories
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite firearms accessories. 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 accessories
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
- Audit every recent chargeback and dispute reasonPull the last 30–90 days of disputes from your processor's dashboard and sort them by reason code. Customers are telling you what went wrong with their language: unrecognized charge, item not received, item significantly not as described, unauthorized transaction. This is not guesswork—it is the pattern. Do not assume the reasons are distributed evenly. One root cause often drives most of them. A billing descriptor that does not match your store name, for example, will spike unrecognized-charge disputes across all customers. Delivery confirmation gaps will create a cluster of not-received disputes. Once you have mapped the pattern, you know what to fix.
- Get a verified copy of your store while you still have access — todayA high-chargeback review does not always end in suspension, but the risk is real. If your account closes, you lose admin access and with it every way to extract your catalog, orders, customer history and theme data. You cannot get your gift card codes back through any API—if the store closes, the codes are locked away and the only option is re-issuing. Shopify's own CSV export cannot carry metafields, metaobjects, orders, videos, themes, menus, discounts or redirects. Migration to a new store and processor requires all of that. Create a full backup now: a migration service can move your complete store—catalog, images, SEO, theme, customer data, order history, and configuration—to a new build running a gateway that will underwrite you, then verify the counts match before going live. That backup is worthless if you wait.
- Fix your billing descriptor immediatelyThe billing descriptor is the text that appears on a customer's bank statement when they charge from you. It must be your actual business name or a widely known trading name, short enough to fit on a statement line (typically 20–30 characters). If it says something cryptic, generic or unrelated to what your customer ordered, they will assume fraud and file a chargeback before contacting you. Check your processor's dashboard for what descriptor is actually running. If it is unclear, vague or does not match your business, change it today. This alone often drops dispute rates measurably because you have made every transaction recognizable.
- Add tracking and delivery confirmation to every orderA significant portion of chargebacks claim the item never arrived. Whether or not that is true, trackable shipment with signature or proof of delivery removes the customer's incentive to dispute. If you ship physical goods, every parcel needs tracking in your fulfillment. If you use a carrier or fulfillment partner, verify their system sends tracking automatically. For digital goods or services, document delivery in your system immediately at point of sale—a link, a download, a confirmation email with a timestamp. The processor needs to see that you can prove delivery, and the customer needs to see proof that discourages them from filing a dispute after they receive the goods.
- Set up responsive customer support before they disputeA customer who gets a quick refund never files a chargeback. A customer ignored for a week will dispute instead. Set up a support channel—email, chat, help desk—and monitor it actively. When a customer contacts you with a problem, resolve it within 24 hours if you can, and always respond within that window. Train support to offer refunds generously on genuine problems before the customer has to go to their bank. This is cheaper than dispute fees and processor penalties. Once a dispute is filed with a card network, you cannot reverse it through support—you can only fight it with evidence. Prevention is the only move that actually works.
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 accessories store's data is dangerous to move because fitment metadata lives in custom metafields. Compatibility data—which optics fit which rail systems, which holsters fit which firearms, which magazines are compliant in which states—is stored as reference fields, lookup fields or text metafields that a CSV export cannot carry. Shopify's standard export also cannot carry metafield data at all. If you move by hand or naive export, every product page renders but the fitment filters and state-compliance logic silently break, so a customer selects a holster for the wrong firearm and you process a return and a chargeback. On a high-AOV category, that is not trivial.
| What you own | How much of it | What breaks doing it by hand | What we do instead |
|---|---|---|---|
| Product images | 7,200images≈ 30 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 | 1,200descriptions≈ 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 | 9,600variants≈ 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 | 14,400metafields≈ 96 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 | 1,643records≈ 6 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 |
| Product videos | 45videos≈ 3 hrsre-upload and re-attach, ~4 min each | By handthe product CSV does not carry video or 3D media, so every one is a manual re-upload. They also cannot be pulled straight from a remote URL — the bytes have to be downloaded and staged first, and a wrong content type lands the file as a generic attachment that media-restricted fields then reject | Automatedvideo bytes downloaded, staged through a proper upload target, re-attached to the right product, and verified as processed rather than silently failed |
| Customers | 4,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 | 8,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 | 95discounts≈ 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 | 103articles & pages≈ 7 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 does not help you here. A firearms accessories merchant who has been declined by Stripe carries that history as a person and as a business, and a processor running standard MATCH checks will see it regardless of whether you form a new LLC. If your original store's account was terminated for selling restricted items, a new company with the same person controlling it signals restructuring to avoid compliance, which underwriters treat as higher risk, not lower. The move is fixing the catalog and the claims, then applying to a different processor under your honest business history.
Frequently asked
Which payment gateway will take a firearms accessories store?
The gateway is not the constraint—the merchant account behind it is. Several high-risk acquirers publicly underwrite firearms accessories, and they can front them through Authorize.net, Stripe-alikes and bespoke integrations. What will take you depends on your specific catalog mix, whether you sell magazines and components, your volume and your processing history. Rather than cold-email a dozen ISOs, use the underwriting request form on this page and let brokers who specialize in 2A commerce bid for your business.
What reserve should I expect to carry?
Most firearms accessories merchants report a 5–10% rolling reserve held for 90–180 days. This means if you process £100,000 in a month, £5,000–£10,000 sits in your processor's account and is released in tranches. Some processors tie it to chargeback rates or customer complaints, so if your first 90 days are clean, they may reduce it. Budget for cash flow around this; it is not a penalty, it is standard risk management in high-AOV categories with regulatory complexity.
Will my fitment data and geo-blocking survive a store migration?
No, not through Shopify's standard export. Fitment rules, state-compliance logic and custom metafields are invisible to CSV round-trips. If you migrate to a new Shopify store without a specialized tool, every product copies but the filtering and blocking rules do not, so customers can order incompatible items or prohibited SKUs. Our migration service rebuilds this metadata by interrogating your original store's API and the Shopify metafield layer, then re-applies it in the new store. Standard exports will lose it entirely.
Do I need a new legal entity to apply to a different processor?
No. A new LLC does not reset your payment history or your MATCH listing; a processor running standard checks will see you as the controller of both entities. If your original Shopify Payments account was declined for selling restricted items, applying again with a new company does not solve the problem—it signals you are trying to avoid compliance scrutiny. The fix is changing your catalog and your claims, then applying to a processor that underwrites 2A commerce case-by-case, which they will under your honest business history.
What is a chargeback threshold and why does my processor care?
The card networks—Visa and Mastercard—monitor chargeback and dispute rates at every merchant account. When a merchant's rate climbs to roughly 0.9%–1.5% of transactions, the networks impose financial penalties on the acquiring bank per dispute. Your processor acts before that threshold because the alternative is losing money on your account. The threshold is not negotiable and it applies to every merchant. Once you are flagged, the only way out is to prove your rate has fallen.
Can I appeal my account being put in a dispute-monitoring programme?
No. The card networks' thresholds are automatic and non-discretionary. There is no appeal process because the programme is not a judgment—it is a network rule that triggers when a rate hits a set point. What you can do is demonstrate that you have fixed the root cause of the disputes. The processor needs to see your rate fall below the threshold within the given timeline, typically 60–90 days. That is the only way out.
Will moving to a different processor solve this problem?
Not unless you fix what caused the disputes in the first place. A high chargeback rate reflects a real pattern in your orders—unclear billing, missing delivery confirmation, poor customer communication, or genuinely unmet expectations. Every processor screens for high-risk merchants, and if you carry the same dispute pattern to a new acquirer, you will be flagged again. The processor is not the problem. The fix is the root cause: clear billing, trackable delivery, and responsive support.
How do I actually lower my chargeback rate?
Start by mapping the reasons behind your recent disputes—unrecognized charge, item not received, not as described. One or two reasons usually dominate. Then fix that specific problem: a clearer billing descriptor, delivery confirmation on every order, or faster customer support that resolves issues before they become disputes. The fixes are operational, not financial or technical. A customer who recognizes the charge, receives the goods with proof, or gets a quick refund does not dispute. Prevention is far more effective than fighting disputes after they are filed.
Can you turn my payments back on if I get flagged?
We cannot turn payments back on—only your processor and the card networks control that. What we can do is move your complete store to a new build running a different gateway that may have different underwriting criteria and will accept your category. We migrate your catalog, images, SEO data, theme, customer records, order history, metafields, and configuration, then verify the counts match. But the actual fix—the one that keeps you from being flagged again—is addressing what caused the disputes: clear billing, trackable delivery, and genuinely responsive support before customers dispute.
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 →