Appealing a Shopify Payments decision, and you sell nicotine pouches. 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 nicotine pouches
Shopify Payments is underwritten by Stripe, which lists nicotine products—including tobacco-free pouches—on its restricted businesses policy. The primary trigger is the product category itself: any pouch marketed as delivering nicotine is classified as a tobacco or nicotine product regardless of botanical origin. The secondary trigger is your business model. Subscription merchants are flagged more aggressively because recurring charges on age-restricted products create chargeback and fraud risk that makes processors nervous. A one-time sale can sometimes slip through; a subscription almost never does.
Rule out the easy fix first — then deal with the real one
There is no Shopify-documented route for nicotine pouches, so rule this out first. What merchants try is connecting a high-risk payment gateway and hoping the underwriting is simpler than Shopify's. It usually is not. You will still face a tobacco or nicotine merchant account application with the same underwriting questions: age verification proof, subscription billing documentation, shipping compliance in your target countries, and chargeback history. The difference is that Shopify Payments will decline you outright, while a high-risk acquirer will consider you—but that consideration is not an approval, and the gateway itself is not the bottleneck. The merchant account behind it is.
It only helps if all of these are true:
- You must prove age-gating technology is live on checkout and product pages.
- Your subscription terms must clearly state the customer's age requirement and cancellation rights.
- You must document shipping restrictions by country and your compliance checks.
- Your processor must be a high-risk acquirer; most mainstream gateways will not even quote you.
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
🔞 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.
🔁 Recurring billing is a large share of revenue
A disabled Shopify Payments account stops new subscriber signups and breaks billing on existing subscribers simultaneously—because stored payment methods are held by the processor and cannot move to a new gateway without customer consent. An appeal buys you time, but it also leaves your subscriber base decaying. The honest move: appeal once in writing with evidence, and start migrating to a new processor the same day. Do not wait for a decision before you contact a gateway that accepts your category. Weeks of silence will cost you more revenue than the appeal effort saves.
What you actually have to fix
Underwriters do not change their minds because you asked. They change them because the facts changed. For nicotine pouches, these are the facts that move the decision:
Implement age-gating on every product and at checkout
This is the single highest-yield fix. Every processor will ask for proof that you cannot sell to anyone under your target age—usually 18 or 21. Static text that says 'Must be 18+' is not enough. You need a live age gate: a checkbox the customer actively confirms, or better yet, a third-party age-verification service integrated into your checkout and attached to product pages. Document that service in screenshots and include the provider's name and verification method in your underwriting package.
Write clear subscription terms and obtain explicit consent
Subscription is a red flag by itself because of recurring-charge chargebacks. Write out your subscription terms in plain language: the frequency, price, cancellation mechanism and the customer's affirmative consent to being charged on that schedule. Many acquirers will ask for email evidence of customer opt-in or a recorded consent call for high-value subscriptions. Have this ready before you apply, not after.
Document your shipping and country compliance
Nicotine pouches face outright bans or heavy restriction in several countries and US territories. Build a shipping policy that lists every country you will and will not ship to, and explain why (legal ban, local customs restriction, or internal business decision). Then prove you enforce it: show how your store blocks checkout or requires additional verification for restricted regions. Acquirers will ask for this; having it ready shortens the underwriting cycle.
Gather your processing history or financial projections
If you have processed with another merchant account before—even if it was closed—bring the statements, chargeback reports and closure reason. Acquirers will check MATCH and see it anyway. If you are new, bring a realistic volume projection, your marketing spend plan and evidence of customer acquisition (email lists, social following, pre-launch signups). This is not about proving you will be huge; it is about showing you have thought through unit economics and compliance.
What underwriting will ask you for
- Proof of age-verification system (screenshots of your checkout and product-page gates)
- Subscription billing agreement and customer terms of service
- Product COA or specification sheet (nicotine content, origin, non-tobacco certification if applicable)
- Processing history from your previous merchant account or statement of volume projections
- Shipping policy showing country-by-country restrictions and how you enforce them
Getting underwritten for nicotine pouches
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite nicotine pouches. 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 nicotine pouches
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
Nicotine stores are dangerous to move by hand because subscription data lives partly in Shopify's subscription system and partly in metafields. Billing cycles, pause dates, customer consent records and dunning logic all exist in the subscription table, not as CSV; Shopify's CSV export cannot touch any of it. If you move by hand, you will copy the product and order history, but every active subscription becomes orphaned—the customer keeps paying the old store and never receives product, or the charges simply stop. For a category where recurring revenue is the model, a failed subscription migration is a financial crisis, not an inconvenience.
| What you own | How much of it | What breaks doing it by hand | What we do instead |
|---|---|---|---|
| Product images | 600images≈ 3 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 | 150descriptions≈ 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 | 450variants≈ 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 | 900metafields≈ 6 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 | 215records≈ 2 hrsredirects one at a time, plus a handle audit | By handany handle that changes becomes a dead URL with no redirect, and existing 301s are not in the product CSV at all. Years of accumulated ranking and backlinks end up pointing at pages that no longer resolve — the most expensive thing on this page to get wrong, and the slowest to notice | AutomatedSEO titles, meta descriptions and handles carried across, and every existing 301 recreated, so nothing that used to rank starts 404ing |
| Your custom theme | 1theme≈ 6 hrs2–10 hrs depending on how customised it is | By handa theme is not just its files. The settings, section content and block ordering are stored against the store, so a file copy gives you the layout and none of the content. Hardcoded asset URLs and tracking snippets also still point at the old store | Automatedyour live theme pulled and pushed as-is, then scanned for tracking snippets and hardcoded URLs that need re-pointing |
| Product videos | 8videos≈ 32 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 | 2,800customers≈ 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 | 22discounts≈ 1 hrsabout 1 hr via the discount CSV, or ~3 hrs rebuilt by hand | By handthe discount CSV covers basic codes, but automatic discounts, quantity breaks and combination rules are not in it and have to be reconstructed by hand. A subtly wrong rule is worse than a missing one, because nobody notices until it has been over-discounting for a fortnight | Automateddiscounts recreated through the API with their rules, usage limits and dates intact, including automatic and free-shipping types |
| Blogs & pages | 20articles & pages≈ 1 hrsrecreated one at a time, ~4 min each | By handno CSV route for either. Articles also have no SEO fields of their own — their title and description tags live in metafields — so a hand-rebuilt blog loses its SEO even when every word of the text is right | Automatedarticles and pages recreated with authors, tags and publish dates, their SEO written to the metafields Shopify actually stores it in, and inline image URLs rewritten |
| Apps & app data | 8apps≈ 8 hrsabout 1 hr per app to reinstall, reconfigure and re-test | By handmost app data lives in metafields on your products and customers, so reinstalling the app gets you an empty app: reviews gone, subscription plans gone, loyalty balances gone, bundles gone. Flows and automations have to be rebuilt by hand and re-tested, and anything with its own billing has to be re-subscribed | Automatedthe metafield data your apps rely on migrates with the products and customers it hangs off, so a reinstalled app finds its data waiting instead of an empty store |
See these numbers for YOUR store, free
The figures above are a typical store in your category. The demo scan connects read-only to yours and counts the real thing — every product, variant, image, customer, order and metafield — then tells you exactly what a migration would carry across. No card, and it never writes to your store.
▶ Run the free demo scanDoes this need a new company?
A new legal entity will not reset a MATCH listing, so opening a second company does not erase the decline. That said, you do not strictly need a new entity to move processors. If your current entity has never processed nicotine before, and your previous processor declined you for a different category entirely, a high-risk acquirer may treat that as a clean slate. But if your entity is already on MATCH for nicotine, a new company is a delay tactic, not a solution. The honest move is to fix the compliance gaps on the entity that exists.
Frequently asked
Can I keep my current store and just switch payment processors?
No. Shopify Payments cannot process nicotine products at all, so you cannot stay on the same Shopify store and solve this with a gateway swap. You must migrate to a new Shopify store with a high-risk merchant account and a supported gateway. The new store is where you run your real business going forward. The old store becomes read-only or is shut down once customers and data have moved.
Which payment gateway will actually accept me?
Authorize.net offers high-risk merchant accounts and will quote nicotine merchants, as will specialist high-risk ISOs and acquirers such as PaymentCloud, Corepay and Easy Pay Direct. But 'will quote' is not 'will approve'. Each has its own underwriting criteria: age-verification proof, chargeback history, country restrictions and subscription terms. Rather than cold-email a dozen providers, use the acquirer network on this page or a high-risk payment broker familiar with nicotine.
Will my subscription data survive a store migration?
Only if you migrate it correctly. Shopify's CSV export does not include active subscriptions, billing cycles, pause dates or customer consent records. You must use Shopify's subscription API or a migration partner with subscription support to carry that data over. If you move by hand, every active subscription will break—customers will either keep being charged to the old store or charges will stop entirely. For a subscription business, that is a crisis.
What reserve should I expect on a nicotine merchant account?
Most high-risk acquirers hold 10–20% of your monthly volume in a rolling reserve for 90–180 days. This is not a penalty; it is standard for any restricted category with chargeback or age-verification risk. That means if your monthly volume is £10,000, you might see £1,000–2,000 held back from each month's settlement, released gradually over three to six months. Plan your cash flow around this and confirm the reserve terms before signing the underwriting agreement.
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 →