Shopify Payments disabled, and you sell adult toys. Migrate everything to a new Shopify store.
The email is short and it reads like a verdict: Shopify Payments has been deactivated, payouts stop, and support points you at the Terms of Service. Here is the part almost nobody tells you, and it is the only part that changes what you should do today. Your store has now been flagged. Shopify Payments is underwritten by Stripe, so your product category tripped a payment processor's policy — but the review happened against your account, and the account keeps that record. Bolt on a third-party gateway and you have changed who settles your money. You have not changed what Shopify knows about your store, and its terms allow it to act again at any time, on notice. Merchants report the same sequence constantly: payments off, a few more weeks of trading, then a second review that closes the store for good. So treat this as step one of two. Get a full copy of your store somewhere you control, now, while you can still log in — even if it is only a backup plan you never use.
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
- "Shopify Payments is no longer supported for your business type" — with no detail about which part of your business
- Payouts stopped, while orders that already went through keep needing to be fulfilled
- Checkout still working for days or weeks afterwards, which feels like a reprieve and is really a countdown
- Support declining to discuss the decision, and pointing at the Terms of Service
- A request for invoices, supplier agreements or fulfilment evidence that arrived shortly before the shutdown
- And the one nobody warns you about: your account now carries a risk-review record that a new gateway does not erase
The hold is the visible problem. The stall is the expensive one — every day without a working checkout burns the ad spend that produced the traffic anyway. But the risk nobody warns you about is the third one: your account has now been through a risk review, and it keeps that record. A new processor changes who settles your money. It does not change what Shopify knows about your store, and the terms let Shopify act again at any time on notice. Assume this is step one of two, and get a copy of everything out while you can still log in.
Why it happened — specifically for adult toys
Stripe, the processor behind Shopify Payments, prohibits adult content and services globally. Physical pleasure products sit in a different bucket: they are prohibited in Brazil, India, Japan, Malaysia, Singapore, UAE and Mexico, but restricted elsewhere. A US or UK retailer is usually declined not because the product exists, but because your product images, payment descriptor, and age-verification are not robust enough to satisfy Stripe's underwriting. The secondary trigger is any suggestion of therapeutic benefit—marketed as improving sexual health or treating dysfunction moves you from restricted to prohibited.
Rule out the easy fix first — then deal with the real one
Rule this out first: Shopify does not publish a documented route for adult retailers. What merchants try is applying to Shopify Payments directly, and most are declined within days. The honest path is to acknowledge the restriction upfront and move to an acquirer that publicly underwrites this category. You will find them by searching for adult payment processing or by using the quote form on this page. That acquirer will run their own underwriting on your age controls, your imagery, your descriptor and your payout bank details—it is a real review, not a rubber stamp—but they are used to the category and will not decline you solely for selling the product.
It only helps if all of these are true:
- Your store must have a robust age-gating system (18+, with ID verification if payment processor requires it)
- Product images and descriptions must not contain nudity, explicit poses, or graphic depictions
- Payment descriptor must be neutral and discreet—never brand-identifiable as adult retail
- You must not market products as treating sexual dysfunction or improving sexual performance
- Payout bank account must be in your own business name, not a third party's
If any one of them does not hold, you are where everyone else on this page is: you need a store built around a gateway that will actually accept you — and everything you have built has to move into it without losing the catalog, the customers, the order history or the rankings.
What this means for a business like yours
🔞 Requires age verification, and shipping is regulated in its own right
Age-restricted categories get declined on process, not product. The underwriter's question is not whether your goods are legal, it is whether you can prove a minor cannot buy them and that you are meeting the shipping regime that applies — carrier restrictions, adult-signature delivery, state registration and remittance where required. A real age gate, a compliant carrier arrangement, and evidence you geo-block the jurisdictions that ban you will change the outcome of the next application far more than any appeal to this one.
📦 Thousands of SKUs, deep variant matrices, distributor feeds
A large catalog does not affect the underwriting decision much, but it dominates everything that happens afterwards. Thousands of SKUs with deep variant matrices, distributor-fed data and years of accumulated metafields are exactly what does not survive a hand-rebuild — and a store this size is where merchants discover, weeks in, that the CSV route silently dropped the fields their theme renders from. If a move is on the table, the size of your catalog is the single biggest factor in how it should be done.
What you actually have to fix
Underwriters do not change their minds because you asked. They change them because the facts changed. For adult toys, these are the facts that move the decision:
Remove or neutralise all product photography and language
This is the single highest-yield fix. Explicit imagery, nude models, and graphic positioning are the primary reason for decline. Audit every product photo, every collection banner, every lifestyle image. If it shows nudity or explicit use, replace it with clean product shots, packaging, or abstract materials. Do the same for product descriptions: remove language that emphasises visual appeal or sexualisation. Straightforward functional language works; suggestive language does not.
Implement verifiable age-gating before the first product view
You must be able to prove to an underwriter that customers confirm they are 18+ before they see any product. A modal on first visit is the minimum; linking it to ID verification is stronger. Screenshot the gate, document the process, and make sure it fires every session or on return visits as well. This is a standard condition in the acquiring agreement and a common reason for hold-ups.
Secure a neutral payment descriptor that does not identify the category
Your payment descriptor—the text appearing on customer bank statements—cannot brand itself as adult retail. Vague, neutral names work; category-specific branding does not. Agree the exact descriptor with your acquirer before you switch, because changes later create chargebacks and review flags. This is also the moment to verify the descriptor with your payout bank, since some banks decline adult merchants at the banking layer.
Audit your chargeback history and fraud controls now
Acquirers underwriting this category pay close attention to chargebacks and refund disputes, because payment reversal is common and high chargeback rates are a decline trigger. Pull your chargeback data from your current processor (if you have it) and be honest about the rate. If you are high, tighten your return policy, improve product descriptions to set expectations, and document how you handle disputes. Also review your fraud filters: are you blocking obvious fraud, or does noise in your transactions signal poor controls.
What underwriting will ask you for
- Age-verification policy and implementation screenshots showing the gate before checkout
- Product imagery review document (sample product photos and pages from your store)
- Payment descriptor approval—the exact text that will appear on customer bank statements
- Underwriting questionnaire from the acquirer (usually covers volume, history, chargeback rates, and fraud controls)
- Business license or registration documents if the jurisdiction requires it
Getting underwritten for adult toys
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite adult toys. 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 adult toys
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
- Work out which layer actually said noThere are three, and they have completely different consequences. If Shopify Payments declined you, your store is still open and you need a different gateway. If the Shopify platform suspended you under the Acceptable Use Policy, no gateway on earth fixes that. And if a third-party gateway's acquiring bank dropped you, that is a third decision with its own appeal route. Read the notice for which entity is speaking before you spend a day fixing the wrong problem.
- Get a verified copy out while you still have access — todayThis is the step people skip, and it is the only one with a deadline you do not control. A payments deactivation is not the end of the process. It is the first thing that happened. Your account has now been through a risk review and it keeps that history — the flag does not leave when the gateway does. Bolting on a third-party processor changes who settles your money; it does not change what Shopify knows about your store, and Shopify's own terms let it act again at any time, on notice. Merchants report exactly that sequence constantly: payments off, trade on for a few weeks, then a second review that closes the store. And if the store closes, admin access can go with it. That is the part that turns a bad month into a dead business, because with no admin there is no API — and with no API your catalog, your order history, your consent timestamps and every metafield your theme renders from are simply gone. Not deleted; unreachable, which is the same thing. Shopify's own CSV export cannot carry metafields, metaobjects, orders or gift card codes, so "I'll just export it" is not the plan you think it is. Take a full, verified copy into a store you control now, while you can still log in. If you recover, you have lost nothing but the price of a migration. If you do not, you still have the business.
- Fix the thing that triggered itUnderwriters do not reverse a decision because you asked nicely; they reverse it because the facts changed. That usually means product labelling and claims, an age or geography gate you were not running, a clearer billing descriptor, published shipping and refund terms, or evidence of fulfilment for the orders that generated disputes. Unglamorous, and the step that decides whether the next processor keeps you — because whatever tripped the first review will trip the second one too.
- Get underwritten somewhere that wants your categoryHigh-risk acquiring is an entire industry that exists precisely for businesses Stripe declines. You apply as what you are, disclose the termination, and expect worse terms than a low-risk merchant gets — a rolling reserve, higher rates, a volume cap. On Shopify the practical route is a high-risk merchant account fronted by a gateway Shopify supports natively, which keeps checkout on your store rather than sending customers off-site.
- Decide whether you need a new entity — honestlySometimes you genuinely do: a new legal entity is the right answer for an acquisition, a partner split, a change of jurisdiction, or separating a high-risk product line so it can never take your main brand down with it. Sometimes it is being sold to you as a way to look like a different applicant — which is a completely different thing, and is fraud. The section below is blunt about which is which.
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 adult store's data is dangerous to move by hand because product images are the entire catalogue asset. If you batch-migrate images naively, you are copying URLs pointing at your old store—they render during the move, then break when you sunset the old site. All 8 product images per item across 420 products must be physically re-uploaded and re-linked, not URL-swapped. Additionally, any age-gating logic in your theme or apps must be manually rebuilt; the standard Shopify theme transfer does not carry custom access rules, so new customers see unrestricted product pages until you rewire the gate.
| What you own | How much of it | What breaks doing it by hand | What we do instead |
|---|---|---|---|
| Product images | 3,360images≈ 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 | 420descriptions≈ 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,520variants≈ 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 | 2,100metafields≈ 14 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 | 630records≈ 4 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 | 3,200customers≈ 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 | 30articles & 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 | 8apps≈ 8 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 will not reset a MATCH listing or your processor history, and most adult retailers do not need one. You are moving from a processor that restricted you to one that accepts the category—the move is legitimate underwriting, not entity structuring. Keep your business registration straightforward and in your own name.
Frequently asked
Which payment gateway actually accepts adult retailers?
The gateway itself is rarely the bottleneck—Stripe, Adyen and Square all power gateways that adult acquirers use. The real decision is which acquirer you work with. CCBill, Verotel, Segpay, PaymentCloud and Corepay all publicly advertise adult merchant services and will underwrite your application directly. They will also ask the hardest questions: your age verification, your imagery, your descriptor, and your chargeback history. Rather than guess which one fits your profile, use the quote form on this page to request underwriting from multiple providers at once.
What reserve should I expect?
Adult retailers typically face a 5–10 percent rolling reserve, held for 90–180 days. That means 5–10 percent of every daily batch is set aside and not released to you until the hold period expires. If you process £10,000 a day, you might see £500–1,000 withheld each day, released only after 90–180 days have passed. This is normal for the category and reflects the chargeback and refund profile. Ask your acquirer for the exact percentage and hold period upfront so you can model your cash flow.
Will my product images and data survive the move to a new store?
Only if you re-upload them actively. Shopify's migration tools do not automatically re-host images from your old store into the new one—they copy the URL references, which point back to the old site. Once you sunset the old store, those images are gone and your new store shows broken image placeholders. You must download your images from the old store and upload them as new assets into the new one. For 3,360 images across 420 products, this is the single largest manual task and why most merchants use a migration service.
Do I need a new company to apply to a better processor?
No. A new legal entity does not erase your payment history or MATCH listing, and most adult retailers do not benefit from forming one. You are moving to an acquirer that accepts the category—that is a legitimate business decision, not one that requires structural change. Keep your existing business registration and be transparent about your processing history with the new acquirer.
Can I get Shopify Payments reinstated?
Occasionally, when the decision rested on a fact you can correct and evidence — a mislabelled product, a missing licence, an unclear descriptor, fulfilment records for disputed orders. If your product category is on the payment processor's prohibited list, no reviewer has the authority to grant an exception, and waiting for one costs you the selling window. Appeal once in writing, then start the alternative the same day.
How long does Shopify hold my money after Shopify Payments is disabled?
A standard hold against chargeback risk runs up to 120 days from the last transaction, because that is roughly how long a cardholder has to dispute one. It can run longer where Shopify suspects illegitimate commerce. The held balance is still yours and is normally released after the window; it is the loss of a working checkout, not the hold itself, that does the real financial damage.
Do I need a new Shopify store, or just a new payment gateway?
If only Shopify Payments was disabled, your store is fine — you need a third-party gateway whose acquiring bank accepts your category, and nothing has to move. You need a new store when the platform itself closed the old one, when you are separating a high-risk product line into its own entity, or when a new provider requires a clean install. Those are genuinely different situations and it is worth being sure which one you are in before you migrate anything.
Will opening a new company get me a new merchant account?
Not by itself, and this is the most important thing on this page. MATCH — the card networks' terminated-merchant file — lists the people behind a terminated business as well as the business, for five years, and every acquirer screens it. A new company with the same beneficial owner does not present as a new applicant. A new entity is the right answer for real structural reasons; it is not a way to look like someone else, and anyone selling it to you that way is selling you fraud.
Can you get my payments turned back on?
No, and nobody outside Shopify and its payment processor can. We are a migration service: if you need to move to a new store built around a gateway that accepts you, we move everything into it — catalog, customers with their consent states, full order history, metafields, theme, redirects — and prove nothing was lost by re-running the entire migration a second time.
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 →