Payouts on hold, and you sell subscription boxes. 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 subscription boxes
You are not flagged for selling subscription boxes. You are flagged for the dispute rate on recurring charges. Stripe and the card networks treat negative-option and hard-to-cancel billing flows as a compliance liability. The primary trigger is a chargeback rate that climbs above what the processor will tolerate — typically disputes marked "I did not authorise this" or "I could not cancel". The secondary trigger is FTC click-to-cancel compliance: if your cancellation flow is not frictionless, the processor flags it during underwriting and may decline you before you process a single charge.
Rule out the easy fix first — then deal with the real one
Rule this out first: Shopify does not document a subscription-box-specific route, and Stripe's underwriting will scrutinise your cancellation flow as a condition of approval. What most merchants try is to apply to Shopify Payments and hope the underwriting team approves the billing model. That fails because the underwriting team cannot approve something the processor itself treats as high-risk. Your actual path is to apply to an acquiring bank or high-risk specialist that publicly takes subscription merchants and has appetite for your chargeback rate. Shopify Payments cannot override a processor's category decision.
It only helps if all of these are true:
- Your chargeback rate must be below the processor's threshold — typically under 1% of transaction volume.
- Your cancellation page must be immediately accessible, no password required, and take effect within one billing cycle.
- You must display your subscription terms, billing frequency and cancellation policy before the first charge, in plain language.
- You cannot use dark patterns, negative options, or pre-ticked renewals that require opt-in rather than opt-out.
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
🔁 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 subscription boxes, these are the facts that move the decision:
Make cancellation a one-click action on your account dashboard.
This is the single highest-yield fix. A customer must be able to cancel their subscription with no more steps than it took to buy it. If they must email support, call a number, or fill a form, you will fail underwriting and you will accumulate disputes. Build a cancellation button into the customer portal that terminates the subscription immediately and sends a confirmation email. Do not require a reason, do not offer a pause option as a friction point, and do not charge a final fee. Test the flow yourself as a customer — if it takes more than two clicks, it is too slow.
Document your chargeback handling and dispute response process.
Processors review not just your chargeback rate but how you respond to disputes. Write down your dispute-response SLA, who handles them, and what you do to prevent repeats — for example, confirming renewal charges by email 7 days before they post. Underwriters want to see that you have a system, not just a number. Include templates of your pre-charge and cancellation confirmation emails, and proof that you send them. A merchant who processes 100 chargebacks but responds to every one systematically is often lower risk than a merchant who has 10 chargebacks and no process.
Pull 12 months of transaction and dispute data in a clean spreadsheet.
Your acquiring bank or specialist processor will ask for this. You need monthly volumes of transactions, chargebacks, refunds and reversals, with reason codes for every chargeback. If you are currently processing with another provider, export your history before applying — most banks want to see the data before they move you. If your rate is above the processor's threshold, do not apply yet; work on it first. If you cannot pull the data, you cannot prove you are a candidate.
Audit your product pages and checkout for negative-option language.
Review every place a customer sees the word 'subscription' or 'recurring' before they buy. You cannot hide the billing model in fine print or bury the frequency on a separate page. The cancellation policy must be stated at the point of purchase in plain language, not linked to a terms page. Check that your email receipts clearly show the subscription terms and the next billing date. If you offer a trial, state that it converts to a paid subscription and the exact date it will charge. Underwriters will read your checkout flow as a customer would.
What underwriting will ask you for
- Cancellation policy document showing exact process and timing — this is the document acquirers request first for your category.
- Screenshot of your live cancellation page showing the flow from login through confirmation.
- Chargeback and dispute history for the last 12 months, broken down by reason code.
- Processing statements from your current or previous processor showing monthly transaction and chargeback volumes.
- Product descriptions and subscription terms as they appear to customers at checkout.
- Copy of your privacy policy and billing terms.
- Proof of FTC compliance training or a signed attestation that your flow meets click-to-cancel standards.
Getting underwritten for subscription boxes
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite subscription boxes. 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 subscription boxes
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
A subscription box store's data is dangerous to move by hand for one specific reason: the subscription records themselves live outside the product catalog. Customer subscription cycles, billing dates, pause states, renewal schedules and linked payment methods are not stored in products, variants or metafields — they live in a subscription app's database. If you migrate the store without migrating the subscription engine, every customer's next renewal will fail because their payment method will not carry over, and you will generate a wave of involuntary chargebacks and payment failures. The catalog moves cleanly; the billing does not.
| What you own | How much of it | What breaks doing it by hand | What we do instead |
|---|---|---|---|
| Product images | 960images≈ 4 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 | 120descriptions≈ 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 | 360variants≈ 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 | 960metafields≈ 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 | 236records≈ 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 | 15videos≈ 1 hrsre-upload and re-attach, ~4 min each | By handthe product CSV does not carry video or 3D media, so every one is a manual re-upload. They also cannot be pulled straight from a remote URL — the bytes have to be downloaded and staged first, and a wrong content type lands the file as a generic attachment that media-restricted fields then reject | Automatedvideo bytes downloaded, staged through a proper upload target, re-attached to the right product, and verified as processed rather than silently failed |
| Customers | 8,500customers≈ 2 hrsCSV import, then cleaning up the rows that fail | By handthe importer works, but marketing consent is the exposure: the CSV carries the current opt-in state and NOT the timestamp or source behind it. Re-opting someone in is a compliance breach, dropping them burns list revenue you paid for, and you cannot prove which happened afterwards. Default-address designation is also lost | Automatedcustomers upserted by email with every address, the default-address designation, and email and SMS consent states and timestamps preserved exactly as they were |
| Order history | 42,000orders≈ 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 | 18discounts≈ 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 | 36articles & 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 | 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 accept subscription payments. The risk is your billing model and your dispute rate, both of which follow you to a new entity — a MATCH listing follows the person for five years, and opening a new company does not reset it. If you have a dispute history with your current processor, the new processor will see it during underwriting under your social security number or tax ID. The leverage you have is demonstrating that you have fixed the cancellation flow and the chargeback rate, not hiding it behind a new legal structure.
Frequently asked
Which payment gateway should I use for subscription boxes?
The gateway itself is rarely the problem — Shopify supports many that work with subscriptions. The bottleneck is the merchant account behind it. You need a processor or acquiring bank that explicitly underwriters subscription merchants and has appetite for your dispute rate. Several high-risk specialists publicly advertise subscription support. Rather than apply cold to Shopify Payments, apply to one of them with your 12-month chargeback data, your cancellation policy, and proof that you have reduced your dispute rate. Stripe and most mainstream processors treat subscription billing as high-risk review even when it is allowed.
How much of my revenue will be held in reserve?
For subscription merchants, reserves typically start at 0–5% of monthly volume and are held for 90 days rolling. This means if you process £10,000 in subscriptions in a month, the processor may hold £0–£500 of that for three months. The actual percentage depends on your chargeback rate, your processing history, and the processor's appetite for your category. New subscription merchants often see the higher end of that range until they prove six months of low-dispute history.
Do I need to reissue all my gift cards if I switch processors?
Gift card codes cannot be read or migrated through any Shopify API, so if you use Shopify's gift card product, the codes are stored in your current store and cannot be exported. You will need to reissue any active gift cards to your customers as credits or new codes in the new store. This is not a processor question — it is a Shopify platform limitation. For a subscription box store, this is rarely a major issue because gift card codes are usually single-use, not recurring.
Will my customer subscription data move to the new store?
No. Your customer records, order history and email addresses will migrate, but not their active subscriptions. Those live in your subscription app's database and cannot be exported through Shopify's standard data APIs. You will need to contact your subscription app provider to export the list of active subscribers, their next billing dates, and their stored payment methods. Then you will manually re-enrol them in your new store, which is why this migration is time-consuming. Your new processor will see the transition as a spike in new signups, so flag this to their underwriting team before you move.
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 →