Payouts on hold, and you sell research peptides. 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 research peptides
Shopify Payments is underwritten by Stripe, and Stripe explicitly prohibits the sale of research chemicals and drug analogs. The primary trigger is that research peptides occupy a legal grey zone: their entire commercial viability depends on the RUO (research use only) disclaimer. The secondary trigger is enforcement risk — any language suggesting human consumption, health benefit or therapeutic use converts your listing from a regulated-but-legal product into an unapproved pharmaceutical claim, which moves you from restricted to prohibited. FDA enforcement activity in this category is documented and rising.
Rule out the easy fix first — then deal with the real one
Rule this out first. Shopify does not document an official route for research peptides the way it does for hemp. Most merchants try to apply through the standard high-risk merchant form and get declined at the Stripe level without appeal. The honest equivalent is that you need a high-risk acquirer willing to underwrite the category explicitly — one that accepts the RUO model and has evaluated the regulatory environment. That underwriting is separate from Shopify's approval, and the acquirer will scrutinise your exact copy, your customer acquisition channels and your compliance documentation before deciding whether to take you.
It only helps if all of these are true:
- Your product pages must state research use only and exclude all human consumption language
- You must hold liability insurance that covers the RUO product category explicitly
- Your ads and marketing materials cannot imply or suggest any health benefit or therapeutic use
- You need documented evidence of compliance with any applicable state or local research chemical rules
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
💊 Sold to be swallowed, inhaled or applied — health claims and product-liability risk
A hold on payouts for ingestible products almost always traces to dispute patterns. The processor is protecting itself against "it did not work" chargebacks, which dominate this category because causation is subjective and the customer experience is internal. A single high-dispute product page or a spike in refund requests can trigger a hold. Before you move anywhere, audit your product claims language — if your copy reads like a drug claim rather than a structure-function claim, underwriters will assume disputes are inevitable. Have your certificates of analysis and third-party testing visible on product pages or in a linked document. The hold itself is temporary, but the real cost is the stalled checkout and the cash gap while you fix the underlying trust issue.
⚖️ Legal status is genuinely contested or actively changing
A payout hold on legally contested goods reflects the fact that processors price legislative risk, not just chargeback risk. Your category may be legal in your home jurisdiction but actively prohibited or pending regulation elsewhere, and a few sales across state or country lines can trigger a hold that applies to all payouts. The hold is temporary, but it signals that underwriters see your entire category as volatility, not just your individual compliance. Before you move to a new processor, confirm that your sales record and marketing comply with the most restrictive jurisdiction you have shipped to — not your home market. You may also need to tighten geo-blocking or drop certain territories entirely.
💎 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.
What you actually have to fix
Underwriters do not change their minds because you asked. They change them because the facts changed. For research peptides, these are the facts that move the decision:
Remove every phrase that implies human consumption or health benefit
This is the single highest-yield fix and where most applications fail. Any statement that your peptides treat, prevent, cure or manage a condition — inflammation, muscle recovery, cognitive function, anything — converts your offer into an unapproved drug claim. Audit your product descriptions, FAQs, testimonials, email sequences, blog posts and customer reviews for therapeutic language. Even indirect claims like 'supports recovery' or 'enhances performance' trigger automated flagging. RUO language must be plain and unqualified: 'for research purposes only' with no implication of end use.
Obtain and display current product testing documentation
Processors in this category ask for laboratory analysis showing exactly what is in each peptide and at what purity. You need COA (Certificate of Analysis) from an accredited third-party lab for every SKU you sell. This becomes part of your underwriting file and is often requested during periodic compliance reviews. Store these securely and be able to produce them on demand. Testing gaps are the second reason applications get declined.
Document your RUO liability insurance explicitly
High-risk acquirers require proof that your insurance covers research-use-only products and your specific liability exposure. A standard general liability policy often excludes chemical or pharmaceutical products. You need an endorsement or a dedicated RUO product liability policy. Bring the certificate to your underwriting call and highlight the coverage limits and the RUO language.
Build a compliance dossier covering sourcing and storage
Acquirers will ask where you source peptides, how you verify supplier credentials, how you store them and what your return or destruction policy is. This should be written down, dated and available to send to underwriting. The detail here signals that you understand the regulatory environment and are not running a grey-market operation. Include any state-level registrations or licenses if applicable in your jurisdiction.
What underwriting will ask you for
- Research use only attestation signed by your company officer
- Product liability insurance certificate naming the RUO peptide category
- Customer acquisition and marketing examples (ads, emails, landing pages)
- Laboratory certification or third-party testing results for each peptide
- Detailed description of your quality control and storage protocols
- Financial statements for the last 12 months
- List of all suppliers and their certifications
Getting underwritten for research peptides
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite research peptides. 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 research peptides
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 research peptide store's data is uniquely dangerous to move by hand because compliance metadata lives in metafields. Batch numbers, Certificate of Analysis file links, purity percentages, chain-of-custody data and storage condition records are all stored as reference or file metafields that a CSV export cannot carry. If you copy them naively, they persist as pointers to the old store's files, so product pages render but compliance documentation silently fails to load. On a regulated product category under active FDA scrutiny, that is a compliance failure, not a cosmetic bug.
| What you own | How much of it | What breaks doing it by hand | What we do instead |
|---|---|---|---|
| Product images | 1,800images≈ 8 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 | 450descriptions≈ 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 | 1,350variants≈ 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 | 8,100metafields≈ 54 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 | 620records≈ 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 | 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,800customers≈ 2 hrsCSV import, then cleaning up the rows that fail | By handthe importer works, but marketing consent is the exposure: the CSV carries the current opt-in state and NOT the timestamp or source behind it. Re-opting someone in is a compliance breach, dropping them burns list revenue you paid for, and you cannot prove which happened afterwards. Default-address designation is also lost | Automatedcustomers upserted by email with every address, the default-address designation, and email and SMS consent states and timestamps preserved exactly as they were |
| Order history | 8,500orders≈ 8 hrsa paid third-party importer, plus a day of mapping and reconciliation | By handShopify's own CSV importer cannot create orders at all, so the hours here assume you buy a third-party importer — key them in by hand instead and 9,400 orders is closer to 390 hours, which is why nobody does that and why order history is simply abandoned in most DIY moves. Then support cannot answer a warranty claim, repeat-purchase segments are empty, and every returning-customer flow starts from zero. Getting the mapping wrong duplicates orders or re-dates them to today, and both are worse than not importing at all | Automatedfull order history recreated through the API with line items, properties, customers re-associated, original dates and tracking numbers intact |
| Navigation menus | 3menus≈ 1 hrsabout an hour to rebuild and relink them all by hand | By handmenu items store resource IDs, not paths, so nothing about them is portable — every link has to be re-pointed at the equivalent collection, page or product on the new store | Automatedmenus rebuilt with their nesting, and every item re-pointed at the equivalent object on the new store |
| Discount codes | 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 | 50articles & 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 | 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 process research peptides. Many merchants think a fresh company will reset their profile — it will not. MATCH filing on a business owner persists for five years, and Stripe and other processors check it. A new entity does not erase your history and usually signals to underwriters that you are trying to evade the prior decline, which makes approval less likely, not more.
Frequently asked
Will Shopify Payments process research peptides?
No. Stripe, which underwrites Shopify Payments, prohibits the sale of research chemicals and drug analogs explicitly. You must use a third-party payment processor that has explicitly agreed to underwrite high-risk RUO peptide merchants. Approval is not guaranteed — it depends on your product claims, your compliance documentation and your processing history. The processor will run its own underwriting even after you connect it to Shopify.
Which payment gateway will actually work for me?
Several high-risk acquirers publicly underwrite research peptides: Authorize.net on a high-risk merchant account, PaymentCloud, Soar Payments and Easy Pay Direct. But which one will accept your application, at what rate and with what reserve, depends on your volume, your specific peptides, your marketing channels and your underwriting profile. Rather than cold-contact each one, the quote form on this page will help you match with brokers who know this category.
Will my peptide test results and batch data survive the store move?
No, if you move by hand. COA files, batch numbers and compliance metadata live in product metafields, and Shopify's CSV export cannot carry metafields at all. A migration service using the Shopify API can copy them, but you must verify the file links work in the new store. Always download and re-upload your lab documentation rather than relying on file pointers from the old store.
What reserve should I expect?
High-risk acquirers typically hold 10–25 per cent of your monthly volume in rolling reserve for 180 days or longer, depending on your chargeback rate and processing history. Some hold a lump-sum reserve upfront. This varies by processor and your individual underwriting. Budget for 90 days of operating costs not held in your main account before signing a merchant agreement.
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 →