Payouts on hold, and you sell in-game items. 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 in-game items
Stripe, the processor behind Shopify Payments, restricts virtual-world currency and items when you do not operate the virtual world yourself. Third-party trading — reselling skins, accounts, in-game currency or other virtual goods — lands on the restricted list. The secondary trigger is chargebacks. Delivery is invisible and unverifiable to a payment processor, so a buyer can dispute the transaction months later with no evidence against them. Minors using a parent's card without consent drive chargeback rates far higher than a processor will accept.
Rule out the easy fix first — then deal with the real one
Rule this out first. Shopify Payments does not document a route for third-party virtual items, and asking their support team will not change that answer. What merchants try instead is applying for a high-risk merchant account through a separate acquirer and connecting it via a payment gateway Shopify supports — Authorize.net on a high-risk MID, or PaymentCloud, Soar Payments and Easy Pay Direct. That application will reach an underwriter who specialises in digital goods, not Shopify's team. They will decline you too if your chargeback rate is already high or if you cannot prove delivery.
It only helps if all of these are true:
- Your chargeback rate must sit below the threshold your target acquirer publishes — typically 1–2%.
- You must be able to document delivery: transaction IDs, account confirmation emails, or API logs showing the item appeared in the buyer's inventory.
- You cannot resell items whose publisher terms prohibit trading — check the game's ToS before you list anything.
- Your buyer base must skew adult, or you must collect parental consent at checkout for any transaction from a cardholder under 18.
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
💎 High average order value, so fraud and disputes cost more per event
A payout hold on high average order value sales means a single fraud or dispute event has material impact on your reserves and your solvency right now. The processor is protecting against chargeback liability that, for your order size, could exceed their reserve anyway. The working-capital gap is not theoretical — you may have shipped goods on credit or taken loans to fund inventory and now have no payout to cover it. The hold typically runs up to 120 days from your last transaction, but the real damage is the stalled checkout, not the hold itself. Before you approach a new processor, have clean transaction records and fulfillment proof for the last 90 days, and be honest about what triggered the hold.
🔁 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.
What you actually have to fix
Underwriters do not change their minds because you asked. They change them because the facts changed. For in-game items, these are the facts that move the decision:
Build a chargeback documentation system before you reapply.
This is the single highest-yield fix. Underwriters will ask to see proof that you can prove delivery, and 'the buyer said they got it' does not count. You need transaction records, confirmation emails sent to the buyer's in-game account, API logs, or screenshots that show the item appeared in their inventory after purchase. Set this up now, capture it for every transaction going forward, and then pull a 90-day sample to show your next acquirer. You will also need a chargeback rate calculation: total disputes divided by transaction count, usually expressed as a percentage. If you do not have clean records, start from today.
Rewrite your terms of service to address minor cardholders explicitly.
Your merchant account underwriting will include a review of whether you verify cardholder age at purchase or collect parental consent. Write a clear policy: either you collect a parent's email and a signature (wet or digital), or you reject the sale if the cardholder appears to be under 18. This is both a compliance requirement for an acquirer and a chargeback defence — a parent who later disputes the charge has a harder claim if they consented in writing. Make the policy visible at checkout and store proof of consent with every transaction.
Audit the game publisher terms you are reselling under.
Check the official terms of service for every game whose items you sell. Many prohibit third-party trading or require explicit permission. If you cannot find the terms, or they forbid resale, stop listing those items immediately. An acquirer will ask to see the relevant ToS, and if it prohibits what you are doing, you will be declined or terminated. Even if you are approved, the game publisher could take action against your buyer accounts, which will destroy your reputation and your chargeback rate.
Request a chargeback rate baseline from your current processor or bank.
Contact Shopify Payments support and ask for your dispute rate, or ask your bank for a 90-day chargeback statement. You need to know the real number before you apply elsewhere, because an acquirer will pull it from the card networks and will decline you if you are already over their threshold. If you do not have this data, you will waste time and rejection fees applying blind.
What underwriting will ask you for
- Chargeback analysis: a 90-day history showing your dispute rate, the reasons given (item not received, unauthorised, buyer remorse) and how many you won on appeal.
- Proof of delivery method: screenshots or API documentation showing how you confirm the item reached the buyer and appears in their account.
- Samples of your product listings and the game publisher terms of service that govern resale of those items.
- Processor statements from any previous merchant account, showing volumes and any reserves or rate increases.
- Your refund and dispute handling policy, in writing, and evidence you have enforced it.
- Business registration and beneficial owner information.
- Bank statements covering the last three months.
Getting underwritten for in-game items
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite in-game items. 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 in-game items
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
An in-game items store's data is dangerous to move by hand because delivery proof lives in custom metafields. Account usernames, character names, server IDs, item IDs and confirmation hashes are all stored as reference or text metafields that a CSV export cannot carry intact — and if you copy them naively they break or point to the old store's records. On a chargeback-sensitive category, silent data loss on the product page means you lose your proof of what you promised the buyer, which will cost you disputes.
| What you own | How much of it | What breaks doing it by hand | What we do instead |
|---|---|---|---|
| Product images | 3,400images≈ 14 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 | 990records≈ 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 | 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 | 12,000customers≈ 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 | 18,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 | 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 | 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 | 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?
You do not need a new legal entity to sell virtual items — the category risk is behavioural, not structural. A new company will not reset a MATCH listing, which follows the person or beneficial owner for five years. If you have been declined or terminated before, a fresh entity solves nothing. Focus on the delivery proof and chargeback documentation instead.
Frequently asked
Which payment gateways work for virtual items?
Shopify Payments will not touch it, so you need a separate merchant account from an acquirer that specialises in high-risk digital goods. Authorize.net, PaymentCloud, Soar Payments and Easy Pay Direct all publicly advertise this category. Your gateway is the easy part — the hard part is the merchant account itself, because the underwriter will ask for chargeback documentation and proof of delivery before they approve you. Rather than apply cold, use a quote form or broker who can match you to an acquirer whose threshold matches your actual rate.
What reserve should I expect?
Most acquirers in this category hold 10–25% of your revenue in a rolling reserve, often for 180 days or more. That means if you process $10,000 in a month, $1,000 to $2,500 sits in the reserve account and does not reach you for six months. Plan your cash flow around this. Some acquirers offer faster releases if your chargeback rate stays low, but you will not see that negotiation until after you are approved.
Will my delivery records survive a store move?
No — not if they are stored in metafields and you move by hand. A CSV export cannot carry metafield values, so if you copy your products naively, the account names, item IDs and confirmation hashes all go missing. You will have no proof of what you promised the buyer, which makes chargebacks impossible to defend. A programmatic migration reads those fields through the API and rebuilds them in the new store, so they stay intact. That is the only safe way to move an items store.
What if a buyer says they did not receive the item?
You are liable unless you can prove delivery. Your chargeback defence is the documentation you captured at the time — a screenshot showing the item in their account, an API log, a confirmation email to their in-game username, or a transaction ID from the game's trading system. If you do not have that record, you will lose the dispute and the charge will be reversed. Set up proof-of-delivery logging now, before you reapply for processing.
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 →