Payouts on hold, and you sell alcohol. Migrate everything to a new Shopify store.
The message arrived in your dashboard: payouts are on hold. No deposits are going to your bank account. You have checked the balance and the money is there—it is just stuck. This is different from a payments deactivation and requires a different response. Shopify holds funds as a cushion against chargeback exposure, typically for up to 120 days from your last transaction, because that is roughly the cardholder dispute window. This is a temporary freeze, not a seizure. The money remains yours and is normally released when the hold period ends. But the real pressure is not the hold itself—it is what happens to your checkout and your cash flow while the hold is in place. Many merchants report that checkout still works during this time, which can feel like everything is fine. It is not. The stalled payouts create a working-capital crisis at the exact moment you need cash most. If you are in this position, you need to act now.
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
- A dashboard notice: "Payouts have been placed on hold" with no explanation of when they will be released
- Bank account shows no deposits, but dashboard balance keeps growing as orders come in
- Support replies: "Your funds are held pending resolution" with no specifics about what needs resolving
- Checkout continuing to work, which suggests the hold is temporary and not serious
- Cash reserves draining while the payout sits frozen and customers keep ordering
The payout hold itself has a deadline (eventually, funds are released). The cash-flow problem does not. If you cannot operate your business without the daily or weekly deposits you normally receive, this is an urgent problem whether the hold lasts 30 days or 120. The longer it runs, the more expensive it becomes.
Why it happened — specifically for alcohol
Stripe, which underwrites Shopify Payments, restricts alcohol in Canada and prohibits it outright in India and Thailand. In the US, the primary trigger is three-tier distribution law: most states require off-premise alcohol (wine, spirits, beer) to move through a distributor, not direct-to-consumer. An underwriter will decline you if you cannot prove you are licensed and compliant in each state you ship to. The secondary trigger is age verification and adult-signature delivery — if your checkout does not enforce age gates and your carrier does not require a signature from someone 21 or older, you fail the compliance bar before processing ever starts.
Rule out the easy fix first — then deal with the real one
Shopify documents no official route for alcohol, which means there is no permission-to-apply step. What merchants try first is Shopify Payments, which declines most alcohol outright. The next move is to find a high-risk acquirer willing to underwrite the category — Authorize.net on a high-risk MID, PaymentCloud, Soar Payments and Easy Pay Direct are the ones who publicly advertise it. Each one will ask you to prove state licensing, proof of three-tier compliance where applicable, and your age-verification system. That underwriting is the real gate, not the gateway choice. Because there is no platform route, you must apply directly to an acquirer and often work with a payment facilitator or broker who specializes in alcohol to navigate the compliance burden.
It only helps if all of these are true:
- You must hold a valid alcohol license in each state you ship to
- Your checkout must enforce age verification at the point of sale
- Your shipping carrier must require adult signature on delivery
- You must document three-tier distributor compliance or exemption per state
- You cannot process sales to prohibited jurisdictions like India or Thailand
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
A payout hold on age-restricted goods often reflects carrier or fulfillment volatility, not just chargeback risk. Your processor sees shipment rejections, signature mismatches or state registration gaps as fraud signals. The money is yours and will release, but the working-capital gap is immediate — you cannot restock while payouts freeze. Before you switch, confirm that your fulfillment is actually recording age verification at the point of sale and that your carrier documentation matches your sales records. If you have shipped to restricted states or used a carrier that rejected deliveries, that log will follow you. A new processor will ask for it anyway.
🔁 Recurring billing is a large share of revenue
A payout hold is catastrophic for subscription revenue because it freezes two things at once: new orders stop, and existing subscribers' payment methods held by the processor also stop billing. The revenue you thought was predictable decays every day the hold persists. Unlike a single transaction you can dispute, subscription chargeback patterns take weeks to investigate because the processor is examining multiple billing cycles and customer complaints. The hold itself releases after roughly 120 days from your last transaction, but by then you have already lost months of recurring revenue and may have lost subscribers to churn. Deal with the subscription book urgently — restarting means rebuilding your stored payment methods or asking thousands of customers to re-enter cards.
📦 Thousands of SKUs, deep variant matrices, distributor feeds
A payout hold with thousands of SKUs is harder to diagnose and slower to resolve because the processor has to sample across your entire product matrix to understand the dispute pattern. A subset of your variants may have bad claims language, wrong categorization or mismatched descriptions across channels, and the processor cannot release payouts until the sample looks safe. The hold itself is temporary, but the real cost is the stalled checkout and the working-capital gap. Before you switch platforms, export your full product feed and audit it for consistency — mismatched descriptions across Shopify and external marketplaces, SKUs with unsubstantiated claims or wrong MCCs will follow you to any new processor. A hand-rebuild is impossible and not necessary; focus on cleaning the data that is already there.
What you actually have to fix
Underwriters do not change their minds because you asked. They change them because the facts changed. For alcohol, these are the facts that move the decision:
Document your three-tier compliance state by state
This is the single highest-yield fix. Most alcohol merchants either do not know the three-tier rule applies to them or have not documented compliance for the states they ship to. You need a written policy per state — either proof that you ship through a licensed distributor (which satisfies three-tier), or proof that your state exempts direct shipment for your product category. Some states allow wine-only DTC; others allow beer; others prohibit all DTC alcohol. An underwriter will ask for this documentation first, and if you cannot produce it, they will decline without reviewing anything else.
Enforce age verification at checkout and on payment
Your checkout must gate the purchase to age 21+ before payment is even offered. This cannot be a simple checkbox — it must be a real age gate with birth-date entry or ID verification. At the payment gateway level, many acquirers require the merchant category code to be filed as 5921 (Package Liquor Store) or 5813 (Bar/Nightclub), both of which flag age-restricted transactions. Your gateway must support age-restricted coding and your checkout must pass that flag with every order.
Require adult signature on every shipment
Your carrier agreement must mandate adult signature (21+) on delivery. USPS, UPS and FedEx all support this, but you must actively select it and pay the surcharge. An underwriter will ask for proof that your shipping settings enforce this. If you are currently allowing standard delivery without signature, change that setting immediately — it is a policy violation for the acquirer and a legal violation in most states.
Rebuild your subscription system if you run a wine club
Wine clubs are subscription-heavy, and a gateway shutdown breaks recurring billing as well as checkout. If you migrate to a new gateway and your existing subscriptions are tied to the old payment method, they will fail silently and customers will not renew. You need a subscription management system that can migrate payment methods cleanly or a plan to contact all active subscribers and re-authorize their cards. This is not just a compliance fix; it is a revenue protection step.
What underwriting will ask you for
- State alcohol license and resale certificate for each state you operate in
- Proof of three-tier distribution compliance or exemption documentation
- Age verification and adult-signature delivery system documentation
- Processing history for the past 12 months, including chargeback and dispute records
- Samples of your product pages showing warnings, age gates and shipping restrictions
Getting underwritten for alcohol
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite alcohol. 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 alcohol
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
- Find out why the hold was triggeredPayouts do not freeze for no reason. Check your recent account activity for unusual patterns: a spike in orders, a high chargeback rate, or transactions from new geographies. Look at your support tickets and emails for any hints Shopify has given you. Then contact Shopify support directly and ask for the specific reason. Be clear and factual. You will probably get a vague answer — many merchants do — but you need to know whether this is a precaution, a policy breach, or something you actually did. That answer determines your next move.
- Get a verified copy of your store out while you still have access — todayThis is the only step with a deadline you do not control. A payout hold can escalate to a payments suspension or account closure without warning. If that happens, admin access can go with it. Once the account is locked, the API closes — and without the API your catalog, order history, customers, and all stored metadata are unreachable. Not deleted; just inaccessible. Export your full store now: product catalog, orders, customer list, and any custom data your theme depends on. This is not a backup for paranoia. It is the step that separates a cash crisis from a dead business.
- Calculate your actual working-capital shortfallStop looking at the hold as a deadline and start looking at it as a cash problem. How many days of operating expenses can you cover without a payout? Rent, staff, inventory, shipping — add them up. Then work backwards: if your usual payout arrives weekly and payouts are now frozen, how long before you cannot pay your bills? This number — not the 120-day hold period — is what drives your next decision. If you can last 30 days, you wait. If you cannot last 7 days, you need a different payment method now.
- Apply for a third-party gateway while you keep Shopify PaymentsShopify allows multiple payment methods on one store. You can add Stripe, Square, or another gateway without removing Shopify Payments. This means new orders can flow through a different processor while you wait for the payout hold to release. It does not fix the hold, but it stops the checkout from becoming useless. Set it up as the primary method so new customers pay through the new gateway, then monitor both for fraud or blocks. Some gateways approve faster than others, and some are more tolerant of the categories Shopify flagged.
- Prepare to migrate if the hold becomes a suspensionA hold can become a deactivation. If Shopify sends a second notice saying payments are being switched off, treat it as urgent. At that point, Shopify Payments goes away and checkout stops unless you have a backup gateway. You will need to move your store to a new Shopify account, a different platform, or a new processor entirely. The longer you wait, the harder this is because your cash is even more depleted. Many merchants in this position cannot afford the migration on their own and report needing outside help — which is where a service that moves your full store, including SEO data and customer records, becomes a practical solution rather than a luxury.
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
Alcohol stores are dangerous to move by hand because compliance metadata lives in metafields. Age gates, state restrictions, three-tier exemption codes and carrier-signature requirements are often stored as custom metafields on products or orders. A naive CSV copy will leave these fields blank, so your migrated store will render products without the age-verification blocks or the carrier flags that payment processing requires. On a regulated product, silent data loss is a compliance failure, not a migration inconvenience — your new store could process orders without the adult signature requirement that the acquirer demands.
| What you own | How much of it | What breaks doing it by hand | What we do instead |
|---|---|---|---|
| Product images | 1,080images≈ 5 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 | 180descriptions≈ 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 | 540variants≈ 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 | 1,620metafields≈ 11 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 | 347records≈ 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 | 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,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 | 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 | 45discounts≈ 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 | 47articles & pages≈ 3 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 compliance requirements — an acquirer will run MATCH screening on the principals of any new company you form, and those principals will carry the payment history of the old business for five years. If your current business has declined accounts or chargebacks, forming a new company will not make them disappear. The honest answer is that most alcohol merchants do not need a new entity; they need the right acquirer and proper compliance documentation.
Frequently asked
Does moving to a new gateway reset my payment history?
No. An acquirer will screen the owners and principals of your business against MATCH and other payment networks for five years, regardless of which gateway you use. If your current account has declined, chargebacks or disputes, those follow you to the next gateway. A new company does not reset them. The value of moving is that a different acquirer may accept the category at all, not that you escape your history.
Which gateway works best for alcohol merchants?
The gateway is not the constraint — the acquirer is. Authorize.net, PaymentCloud, Soar Payments and Easy Pay Direct publicly advertise alcohol, but which one will take your account depends on your state licensing, your compliance documentation and your processing history. You will likely need to work with a payment facilitator or broker who specializes in alcohol to get a quote, because most high-risk acquirers do not list rates publicly.
Will my wine club subscriptions break when I move payment processors?
Yes, unless you plan for it. Existing subscriptions are tied to your old payment method and gateway. When you migrate to a new gateway, those recurring charges will fail because the card is no longer tokenized there. You must either migrate subscription payment methods in advance, or contact all active subscribers to re-authorize their cards on the new gateway. Some subscription apps can handle this; others cannot. Check your app's migration capability before you commit to a move.
What happens to my product data if I move stores incorrectly?
If you copy your store by hand using CSV exports, your state-specific shipping restrictions, age-gate rules and three-tier compliance codes will be lost. Shopify's CSV export cannot carry metafields, so any compliance data you stored there goes blank in the new store. Your products will render, but without the age verification blocks and carrier flags that your acquirer requires. This is why a proper migration tool matters for regulated categories like alcohol.
Why are my payouts frozen if I haven't broken any rules?
Shopify holds payouts against chargeback risk, and that screening is automatic. A high order volume, orders from unusual locations, a product category with higher dispute rates, or a sudden increase in sales can all trigger a hold even if every transaction is legitimate. You have done nothing wrong; the algorithm flagged a pattern. The hold is a precaution, not a penalty. Legitimate merchants are held regularly and the money is released on schedule.
How long will the hold actually last?
Up to 120 days from your last transaction, typically. But if Shopify suspects illegitimate commerce—not just unusual patterns, but actual fraud—the hold can extend longer. The hold period resets each time you get a new transaction, so if you are still taking orders, the 120 days starts counting from the most recent one. There is no way to know your exact release date without asking support, and support often cannot give a precise answer.
Can I speed up the hold or get an early release?
You can ask. An appeal works if you can explain what triggered the hold and show it has been resolved. Provide order details, customer feedback, or evidence that the spike in activity was legitimate. But Shopify does not publish a standard appeal process and most merchants report the response is vague or takes weeks. There is no guarantee an appeal will work, even with evidence.
What happens to my checkout while payouts are on hold?
Checkout typically continues working. Customers can still buy, orders keep coming in, and your inventory depletes normally. But money is not reaching your bank account, which creates a working-capital crisis. You are taking revenue without being able to use it. This is often worse than a checkout block because it creates the illusion that everything is fine while you bleed cash.
Do I need to switch payment processors to get my money unstuck?
Not to release the hold itself—Shopify will release the frozen balance on schedule regardless of what gateway you use. But if you cannot afford to wait, a backup gateway lets you process new orders through a different processor while the hold counts down. You can run Shopify Payments and a third-party gateway at the same time. A new gateway does not unlock the hold; it prevents new orders from becoming inaccessible if the hold escalates to a suspension.
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 →