Appealing a Shopify Payments decision, and you sell cigars and tobacco. 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 cigars and tobacco
Stripe's policy treats tobacco as a restricted business, which means Shopify Payments cannot process it without a specialist underwriter. The primary trigger is the category itself — cigars and pipe tobacco sit on Stripe's restricted list, and a merchant flagged as tobacco will be declined by the default processor. The secondary trigger is undocumented age verification: if your checkout does not prove the customer is of legal age, even a licensed merchant will be declined on the grounds of insufficient controls.
Rule out the easy fix first — then deal with the real one
Shopify does not document a route for tobacco, and the reason is straightforward: there is no single pathway that works everywhere. What merchants typically try first is applying directly to Shopify Payments, which fails because Stripe's underwriting team will see the MCC before any other detail. The honest move is to skip that application and go straight to a specialist acquirer who underwrites tobacco accounts on purpose. They exist, they know what paperwork to expect, and they are faster than trying to convince a generalist processor that your case is an exception.
It only helps if all of these are true:
- Your business must hold a state tobacco license and be registered to collect excise tax.
- You must have documented, compliant age verification at checkout — not just a checkbox.
- Your store cannot display or sell to jurisdictions where tobacco sales are prohibited or restricted.
- You must keep current copies of all required state and federal filings.
- Your merchant processing history cannot show prior chargebacks or disputes related to age-restricted sales.
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.
💎 High average order value, so fraud and disputes cost more per event
High average order value means a single fraud or chargeback event can trigger holds or account review, and Shopify Payments applies reserve policy and dispute thresholds that do not always distinguish between isolated incidents and patterns. An appeal works if the decision rested on a specific disputed order you can prove with fulfilment evidence, shipping tracking and communication records. It fails if the review was based on your category's general chargeback profile or perceived fraud risk. Check whether the decision names a specific order or a pattern. If it names one, appeal with evidence. If it is categorical risk, prepare to migrate.
📦 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 cigars and tobacco, these are the facts that move the decision:
Obtain and file your state tobacco dealer's license
This is the single highest-yield fix, and it is the one document that changes a specialist acquirer's assessment of your application from 'risky' to 'legitimate business'. Most tobacco merchants already have this paperwork because they sell in person or through other channels. If you do not have it, your state's revenue or health department can advise on requirements. An acquirer will ask for a copy certified within the last 12 months. Without it, you will not pass underwriting, regardless of your other documentation.
Implement mandatory age verification at checkout
Your checkout must prove the customer is of legal age before payment is taken. A simple checkbox is not sufficient — you need a documented process such as third-party age verification, ID number capture, or date-of-birth confirmation tied to a validation service. Document your method in writing and be ready to show the acquirer exactly how it works. This is the second-highest-leverage fix because it addresses the specific concern that drove you to restricted status in the first place.
Compile a complete processing history from all prior accounts
If you have processed tobacco sales anywhere else — even a small amount — get statements, chargeback reports and processor documentation from every account you have used. Specialist acquirers want to see that you have not been repeatedly declined or terminated for age-verification failures or fraud. A clean history on a prior account is a strong underwriting signal. If you have had accounts closed, be transparent about why and what you have fixed since then.
Write a clear product and business description for the underwriter
In your application narrative, explain what you sell, how long you have been selling it, what your average order value is, and whether you sell online only or also in a physical location. Tobacco merchants with established retail operations and clear business longevity are treated as lower risk. If you are new online but established offline, say so explicitly. The underwriter is trying to distinguish between a genuine business and a front, and boring operational detail is reassuring to them.
What underwriting will ask you for
- Current state tobacco dealer's license or equivalent state registration document
- Proof of federal excise tax registration and compliance
- Bank statements for the last 3–6 months showing tobacco-related revenue
- Written age-verification methodology describing your checkout controls
- Product list or catalog showing SKUs, descriptions and price points for your top 20 items by revenue
- Ownership and beneficial-ownership documentation for all principals
- Processing history from any previous payment processor, if applicable
Getting underwritten for cigars and tobacco
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite cigars and tobacco. 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 cigars and tobacco
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
A tobacco store's catalog is dangerous to move by hand because age-verification and compliance metadata live in metafields and custom objects. Restricted-product flags, age-gate rules, state-specific visibility toggles and excise-tax calculations are all stored as reference or boolean metafields that a CSV export cannot carry. If those fields are copied naively, they keep pointing at the old store's data or are silently lost, leaving products visible to minors or lacking required tax data. On a regulated product category, that failure is not cosmetic — it is a compliance breach.
| What you own | How much of it | What breaks doing it by hand | What we do instead |
|---|---|---|---|
| Product images | 5,100images≈ 21 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 | 850descriptions≈ 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,550variants≈ 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 | 6,800metafields≈ 45 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,193records≈ 5 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 | 2,400customers≈ 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,100orders≈ 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 | 65discounts≈ 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 | 63articles & pages≈ 4 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 | 12apps≈ 12 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?
You do not need a new legal entity to apply for specialist merchant processing. A new LLC or corporation will not reset your payment history or change an underwriter's view of your compliance posture. What matters is your state tobacco license, your excise documentation and your age-verification controls — those are tied to the business, not the corporate form. If you have been declined once, a new entity does not erase that decline from the processor's memory.
Frequently asked
Which payment gateway will actually take a cigar and tobacco store?
Several high-risk acquirers publicly advertise tobacco underwriting, and they route through gateways Shopify supports natively. Authorize.net on a high-risk merchant ID, PaymentCloud, Corepay and Easy Pay Direct all have tobacco experience. Specialist ISOs focused on nicotine and tobacco are also an option. The gateway is rarely the constraint — the merchant account is. What matters is whether the acquirer's underwriting team believes your age-verification controls and your compliance posture are genuine, not which payment button you use.
Why was I declined if I already have a state tobacco license?
A state license proves you are a legal business, but it does not prove you are a low-risk payment processor's problem. The acquirer is looking for three things: documented age verification at checkout, a clean processing history, and evidence that you understand and comply with the excise-tax obligations in your states. If your prior account was closed for chargebacks or disputes, or if your checkout is a simple clickthrough without age gating, the underwriter will decline you even if your license is current. Fix the verification and reapply with a complete compliance narrative.
Will my product data survive a store migration to a new processor?
Not automatically, and not the compliance-critical parts. Your product-level age gates, state restrictions, excise-tax flags and reserve-calculation rules live in metafields that Shopify's native CSV export cannot carry at all. If you move stores by hand using CSV, those data points are lost, and your new store will sell your restricted products without age verification. A proper migration tool that reads the Shopify GraphQL API can carry metafields forward, but CSV alone cannot. Test the migration on a staging store before going live.
What reserve should I expect, and for how long?
Specialist tobacco acquirers typically hold a rolling reserve of 5–10 per cent of your monthly volume, held for 90–180 days depending on your processing history and chargeback rate. Some acquirers release the reserve in tranches as your history improves; others hold it for the full term and release it all at once. Ask the acquirer explicitly how their reserve schedule works before you sign, because it directly affects your cash flow. A new account with no prior tobacco processing history is more likely to face the higher end of that range.
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 →