Appealing a Shopify Payments decision, and you sell airsoft and airguns. Migrate everything to a new Shopify store.
The decision came down by email, and the temptation is to write back immediately. Stop. Before you draft anything, you need to know what you are actually appealing — because Shopify Payments decisions split into two different categories, and only one of them can be reversed. If the decision turned on a fact — a mislabelled product, an unclear payment descriptor, a missing licence, or disputes you can now prove were fulfilled — then evidence can change the outcome. If the decision turned on your product category itself, then no reviewer has authority to except you from the processor's policy, and the appeal will fail no matter what you write. The difference matters because merchants who appeal the second kind waste weeks waiting for silence while their store runs on checkout alone, unable to plan around the real timeline. So diagnose first. Write second. Start plan B on the same day you appeal, not after.
Move all of it into a new store, from $247
One-time packages, no per-record metering, no quotes. The order form unlocks the moment you pay, counts are matched against your old store, and the entire migration then runs a second time — the second pass has to create nothing.
What you are looking at
- Email saying Shopify Payments cannot support your business, with no detail on which fact or category triggered the review
- Checkout still working for days or weeks after Payments deactivated, creating false hope that the problem might reverse itself
- Support responses repeating the same brief reason without elaborating on what specifically was found
- Requests to provide evidence met with 'appeal to Stripe' — passing the merchant to Shopify's processor without direct contact
- Radio silence lasting weeks after submitting an appeal, with no published timeline for a response
The checkout clock is a trap. It creates the impression you have time to appeal while payouts are actually frozen. The real deadline is the one Shopify does not advertise — when it decides whether to review your store a second time and close the whole account. That usually comes weeks in, which is why plan B must start immediately, not after the appeal fails.
Why it happened — specifically for airsoft and airguns
Stripe, which underwrites Shopify Payments, places airsoft and replica firearms on its restricted-businesses list. The primary trigger is appearance: reviewers classify by how realistic the replica looks, not by legality in your jurisdiction. A two-tone airsoft rifle that is legal to sell may still be flagged as a weapon. The secondary trigger is age controls—if your store does not visibly gate age-restricted products or track buyer age at checkout, you signal to a reviewer that minors can buy without friction, which moves you from restricted to high-risk decline.
Rule out the easy fix first — then deal with the real one
Shopify does not document a specific route for airsoft and replica firearms, which means you cannot apply through the platform attestation model. What most merchants try first is connecting a high-risk processor directly to Shopify through Authorize.net on a high-risk merchant ID, or using a standalone gateway like PaymentCloud or Soar Payments. That usually works—these providers do underwrite airsoft—but it requires you to demonstrate age controls at the product and checkout level, realistic product photography that shows the orange tip or two-tone marking clearly, and clean chargeback history. If your prior processing account was closed for disputes, that fact travels with you and a new acquirer will see it during underwriting.
It only helps if all of these are true:
- Your store must gate age-restricted products behind a verified-age wall at checkout.
- Product photos and descriptions must show safety markings clearly—orange tips, two-tone finish, or any legal marking.
- Chargeback rate must be under the processor's threshold, typically 1% or lower.
- You must be able to provide processing history and any prior account closures to the new acquirer.
If any one of them does not hold, you are where everyone else on this page is: you need a store built around a gateway that will actually accept you — and everything you have built has to move into it without losing the catalog, the customers, the order history or the rankings.
What this means for a business like yours
🎯 Weapons or weapon-adjacent, with state-by-state legality
Weapons and weapon-adjacent goods live under state and country legality that is not uniform, and Shopify Payments prices that legislative complexity as unmanageable. An appeal based on 'it's legal where I ship' usually fails because the processor avoids the jurisdiction-by-jurisdiction audit. Your appeal succeeds only if you can show catalog-level geo-blocking that prevents sales to prohibited states or countries and auditable proof it works. If you do not have that blocking in place, the appeal will take weeks and likely fail anyway. Build the geo-blocking first, then appeal with evidence of it.
🔞 Requires age verification, and shipping is regulated in its own right
Age-restricted merchants appeal on verification infrastructure and shipping compliance—proof that your carrier screening, ID checks and adult signature enforcement actually work. Shopify Payments reviews both the product policy and whether you can operationally stop underage sales. An appeal works if you can show those systems are in place and auditable. It fails if the processor doubts you can hold the line across all states and carrier networks, or if verification is simply not built into your store yet. That takes weeks to design and test. Appeal if you have compliance; build it while you wait.
📦 Thousands of SKUs, deep variant matrices, distributor feeds
Thousands of SKUs across deep variant matrices make a hand-rebuild impractical, so migrating to a new processor must be automated. An appeal buys time only if that time lets you plan the technical migration properly. A successful appeal on product claims or compliance means nothing if you cannot execute the re-work at scale. Before you appeal, confirm you can migrate your catalog programmatically—via API, CSV with metafield support, or a migration service—and verify the target processor accepts your category. If the appeal fails and you have no migration path, the delay cost you more than it gained. Plan the infrastructure move before you submit the appeal.
What you actually have to fix
Underwriters do not change their minds because you asked. They change them because the facts changed. For airsoft and airguns, these are the facts that move the decision:
Build a visible age gate into every restricted product.
This is the single highest-yield fix. Your store must ask for and verify age before a customer can add a replica firearm to their cart or view the product. A checkbox that says 'I am 18' is not enough; underwriters want to see either a third-party age-verification API or a manual review step at checkout. Make it visible in your store settings and screenshots—acquirers will ask for proof that it exists and is enforced. This alone often moves a merchant from decline to approvable.
Photograph every replica with its safety marking in clear focus.
Your product images must show the orange tip, two-tone finish, or whatever legal marking your jurisdiction requires. Do not crop it out or assume customers know it is there. Reviewers judge by appearance first, so a high-resolution shot of the marking is evidence that you are selling a legal toy, not a weapon. Retake photos if needed. This takes a day and it changes how an underwriter reads your entire catalog.
Gather and disclose your full processing history.
If a prior payment account was closed, the new acquirer will find out anyway—usually during underwriting, when they run a MATCH check. Disclose it yourself in your application instead. Explain what happened: was it chargebacks, a policy violation, or a processor decision? Be honest. Many airsoft merchants have been through a processor switch; acquirers know this. What they will not forgive is discovering an undisclosed closure during review, which looks like you are hiding something.
Audit product claims for weapon language.
Review every product title, description, and tag for language that frames the item as a weapon rather than a sport tool. Avoid 'realistic replica firearm' or 'looks identical to real gun'—use 'airsoft rifle' or 'replica training tool' instead. Search your product text for words like 'authentic', 'military-grade', 'combat', or 'tactical' used in ways that emphasize realism over legality. Reword them to focus on sport, collection, or training. This is tedious but it reframes your entire store's tone.
What underwriting will ask you for
- Product safety certification or test report showing legal compliance for your jurisdiction.
- Age-gating screenshot or technical proof of age verification at checkout.
- Processing history from your prior account, including chargeback and dispute records.
- Product photography showing orange tips, two-tone markings or legal safety identifiers.
- Terms of service and product descriptions showing clear age-restriction language.
- Bank statements covering the last three to six months.
- Business license and proof of physical address.
Getting underwritten for airsoft and airguns
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite airsoft and airguns. 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 airsoft and airguns
Six taps and three details. We put it in front of the high-risk acquirers that actually underwrite your category and come back with what they will offer you — rate, reserve and settlement terms — so you are comparing real numbers instead of cold-emailing brokers for a fortnight.
The recovery playbook
- Identify whether the decision turned on a fact or a categoryRead the email carefully. It will say something like 'cannot support' or 'incompatible with our policies'. The next step depends on which it is. If the decision mentioned a specific product, descriptor, licence, or type of dispute, then it may be a fact problem — and facts can change. If it mentioned your business type, industry, or product category as the reason, then no reviewer has authority to except you. Calling Shopify support at this stage usually produces the same email language again, so focus on diagnosis first.
- Gather the evidence for one written appeal — and do it todayThis is the step with a deadline you do not control. Do not wait for the appeal result. Do not assume checkout will keep working while you appeal. Collect the specific evidence that addresses the decision: corrected product screenshots, updated payment descriptors, licence documents, fulfilment records, customer consent, delivery proof. File them all in one place so you can reference them in writing. Set a deadline for the appeal to arrive with Shopify within 48 hours — not because speed guarantees anything, but because waiting is a sunk cost that keeps you from building plan B.
- Appeal once in writing, with only the evidence that counters the decisionWrite directly to the email address that notified you. Be specific: 'You cited [reason]. Here is the evidence that [corrected fact].' Attach or link the documents. Do not argue that the decision is unfair, do not ask for another review, do not promise future compliance. Processors see hundreds of these, and generic appeals are routed as low-priority. You are simply putting the fact on record. If the decision was based on a category prohibition rather than a fact, say so in your diagnostic email to yourself and move on.
- Start plan B the same day: migrate to an accepting gatewayDo not treat the appeal as your plan. Treat it as something you put in motion and then ignore while building what actually survives. A new store on a different payment processor — built into a fresh Shopify domain or migrated into one — with a provider that underwrites your category is the real recovery. The migration takes days, costs a fixed price, and runs in parallel to your appeal. Many merchants never hear back from the appeal. Those who moved the same week have zero downtime in the one business metric that matters: can they take payment.
- If the appeal succeeds, shut down the new store or keep it running dual-processorSuccess is rare and usually takes weeks. If it comes, you will be notified that Shopify Payments is re-enabled. At that point you have a choice: move back to Payments and deactivate the other gateway, keep both running, or stay on the new processor. Dual processing costs more but insures against a second deactivation. Many merchants who have been through this once choose to stay dual, or to stay with the accepting gateway entirely, because the reputational cost of promising customers they can take payment and then freezing is higher than the processing fee difference. That is a business call you make once you are not in crisis mode.
And then there is the part that actually loses businesses
If you do need a new store, the payments problem turns out to be the easy half. This is what is sitting in your current store right now, and what happens to each piece when someone tries to move it by hand:
Why this category in particular
Airsoft stores live on inventory because stock turns fast and buyers search by model, brand and specification. When you move stores by hand, variant data breaks: a rifle with five color options, three barrel lengths and two magazine types is a 30-variant tree, and if you copy descriptions naively the variants diverge—some get the full spec list, others get stripped. On a catalog-heavy store, that is hundreds of bad pages. Metafield data like legal-compliance notes, FPS ratings or import certifications also vanish in a CSV round-trip, leaving you with product pages that no longer prove legality to a customer or an underwriter.
| 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 | 4,800variants≈ 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,000metafields≈ 27 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 | 950records≈ 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 |
| Product videos | 12videos≈ 48 minre-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 | 3,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 | 8,500orders≈ 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 | 35discounts≈ 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 |
| Gift card balances | 180gift cardsno manual routecannot be moved by anyone | By handthis is the one thing on this page that truly cannot be moved by anyone. Gift card codes are unreadable through EVERY Shopify API, by design — no tool, ours included, can copy them. Those balances are real money you owe real customers, and abandoning the old store does not abandon the liability: the customers still turn up expecting you to honour it | Automatedwe re-issue each card with an identical balance, customer and expiry date, and hand you the new codes as a CSV with customer email copy ready to send — the only honest way to move them |
| Blogs & pages | 30articles & pages≈ 2 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 | 10apps≈ 10 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 reset your MATCH listing, which is a five-year history of the person running the business, not the company. If your prior account closed, opening a new company will not erase that record—an acquirer will find it. Moving to a new entity can make sense for tax or liability reasons, but it is not a way around payment processing history. Be honest about who owns the new entity and why you changed it.
Frequently asked
Will moving to a new Shopify store fix my payment processing decline?
No. Your MATCH record follows you for five years, and it tracks the person running the business, not the store. If Shopify Payments declined you, a new store does not reset that history. What can change is your processor—you can switch from Shopify's built-in Stripe underwriting to a high-risk acquirer that specializes in airsoft. That move requires a new gateway, but it is separate from your store. The store move itself is useful only if your new gateway requires a different platform or structure.
Which gateway will take an airsoft store?
Several high-risk acquirers publicly advertise airsoft, including Authorize.net on a high-risk merchant ID, PaymentCloud, Soar Payments, and Easy Pay Direct. They underwrite differently—some focus on chargeback history, others on product compliance and age controls. Rather than cold-email each one, get quotes from all of them at once using a broker or a form submission. The gateway that works for you depends on your volume, your prior processing record and how clean your age-gating is. Price and reserve vary widely.
What happens to my product data when I move to a new store?
Your images, titles, descriptions and basic product structure can move, but metafield data—legal compliance notes, performance specs, import certifications—cannot be carried in a CSV export. That means custom fields that prove your products are legal replicas, not weapons, will be silently lost unless you move them programmatically or re-enter them by hand. On an 800-product airsoft catalog, that is weeks of work. A migration service that uses the Shopify API can carry metafields and move your data intact.
Do I need a new business entity to get approved for payment processing?
No. A new legal entity does not erase your MATCH record or reset your payment history. If your prior account was closed for disputes or policy violations, that fact stays on file under your name for five years. Some merchants form a new company for tax or liability reasons, but they should not expect it to help with payment processing approval. Be transparent about ownership and why you changed structures—that honesty matters more to an underwriter than a fresh company name.
Can Shopify Payments be turned back on if I appeal?
Only if the decision was based on a fact — a mislabelled product, unclear descriptor, missing licence, or disputed orders you can now prove were fulfilled. If the decision turned on your category being on the processor's prohibited list, then no reviewer has authority to make an exception, and the appeal will not change it. The decision tells you which it is if you read it carefully.
How long does an appeal take?
There is no published SLA. Merchants commonly report anywhere from a few weeks to no response at all. Some receive a yes or no answer; others receive the same generic reason again without elaboration. The lack of transparency is why you should not wait for the result before building a backup plan. Filing the appeal and then moving to a different processor in parallel is the only timeline you control.
What evidence actually works in an appeal?
Evidence that addresses the specific decision, not the general principle. If you were rejected for mislabelled product names, show the corrected listings. If for unclear payment descriptors, show what the new descriptor is. If for missing licences, provide the document. If for disputed orders, provide proof of fulfilment — tracking, delivery signature, or customer communication proving the goods were as described. Generic promises to comply do not work because the processor's decision was based on documented risk, not intent.
What if Shopify Payments is re-enabled but then disabled again?
This pattern is common. Merchants report being re-enabled, trading for a few weeks, and then receiving a second deactivation notice. If this happens to you, the underlying decision was likely not actually overturned — it was suspended pending more observation. This is why having a backup payment processor in place before the first appeal is worth the setup cost. You are no longer betting the business on a single gateway.
If I move to a different processor, do I have to close my Shopify store?
No. Your store stays live. You simply connect a different gateway for payments — Stripe, Square, PayPal, Braintree, or another processor that underwrites your category. The store itself, your catalog, your customers, and your orders are unaffected. If your new processor later deactivates you as well, migration to a third processor is the same move again. The goal is to find a gateway whose underwriting actually fits your business model and stick with it.
Move everything, verified twice, from $247
Pick a package and the migration order form unlocks immediately. Your existing store is only ever read from — we never write to it, so nothing you still have can be made worse. How the migration runs, step by step →