Appealing a Shopify Payments decision, and you sell lingerie. Migrate everything to a new Shopify store.
The decision came down by email, and the temptation is to write back immediately. Stop. Before you draft anything, you need to know what you are actually appealing — because Shopify Payments decisions split into two different categories, and only one of them can be reversed. If the decision turned on a fact — a mislabelled product, an unclear payment descriptor, a missing licence, or disputes you can now prove were fulfilled — then evidence can change the outcome. If the decision turned on your product category itself, then no reviewer has authority to except you from the processor's policy, and the appeal will fail no matter what you write. The difference matters because merchants who appeal the second kind waste weeks waiting for silence while their store runs on checkout alone, unable to plan around the real timeline. So diagnose first. Write second. Start plan B on the same day you appeal, not after.
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
- Email saying Shopify Payments cannot support your business, with no detail on which fact or category triggered the review
- Checkout still working for days or weeks after Payments deactivated, creating false hope that the problem might reverse itself
- Support responses repeating the same brief reason without elaborating on what specifically was found
- Requests to provide evidence met with 'appeal to Stripe' — passing the merchant to Shopify's processor without direct contact
- Radio silence lasting weeks after submitting an appeal, with no published timeline for a response
The checkout clock is a trap. It creates the impression you have time to appeal while payouts are actually frozen. The real deadline is the one Shopify does not advertise — when it decides whether to review your store a second time and close the whole account. That usually comes weeks in, which is why plan B must start immediately, not after the appeal fails.
Why it happened — specifically for lingerie
Stripe, which underwrites Shopify Payments, restricts intimate apparel on two grounds. The first is imagery classification—product photography of lingerie, even when non-explicit, can trigger adult-content filters in automated review systems. The second is chargeback and dispute patterns: lingerie has historically high return rates and sizing disputes, which acquirers read as revenue risk and customer dissatisfaction risk combined. A merchant flagged here is not being rejected for selling something illegal; they are being sorted into a higher-risk bucket because their product category comes with predictable payment friction.
Rule out the easy fix first — then deal with the real one
There is no documented Shopify route for lingerie. What merchants try first is connecting a different payment gateway on Shopify, which works and is the correct first move—but it only moves the problem to a different processor's underwriting. You will then need a high-risk merchant account, which requires a separate application to an acquirer outside the Shopify ecosystem. That underwriting is slower, more detailed, and they will scrutinise your return policy, your chargeback history and your product photography. This is not a quick fix, but it is the standard path when Shopify Payments declines you for category risk rather than fraud.
It only helps if all of these are true:
- Your return and sizing policies must be crystal clear at checkout and on every product page.
- You must have chargeback data showing your rate is controllable and trending downward if you have history.
- Product photography cannot be sexually suggestive, even if not explicit.
- Your customer reviews and social proof must not be from adult retail or adjacent categories.
- You must be able to prove you are an established merchant—new stores face harder scrutiny.
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
📦 Thousands of SKUs, deep variant matrices, distributor feeds
Thousands of SKUs across deep variant matrices make a hand-rebuild impractical, so migrating to a new processor must be automated. An appeal buys time only if that time lets you plan the technical migration properly. A successful appeal on product claims or compliance means nothing if you cannot execute the re-work at scale. Before you appeal, confirm you can migrate your catalog programmatically—via API, CSV with metafield support, or a migration service—and verify the target processor accepts your category. If the appeal fails and you have no migration path, the delay cost you more than it gained. Plan the infrastructure move before you submit the appeal.
🔁 Recurring billing is a large share of revenue
A disabled Shopify Payments account stops new subscriber signups and breaks billing on existing subscribers simultaneously—because stored payment methods are held by the processor and cannot move to a new gateway without customer consent. An appeal buys you time, but it also leaves your subscriber base decaying. The honest move: appeal once in writing with evidence, and start migrating to a new processor the same day. Do not wait for a decision before you contact a gateway that accepts your category. Weeks of silence will cost you more revenue than the appeal effort saves.
What you actually have to fix
Underwriters do not change their minds because you asked. They change them because the facts changed. For lingerie, these are the facts that move the decision:
Rewrite your return policy to emphasize sizing and fit.
This is the single highest-yield fix. Lingerie chargebacks cluster around fit disputes and sizing confusion. Your return policy must acknowledge that sizing varies, offer a clear and generous timeframe for returns, and explain how customers can get the right size without friction. This policy must be linked from the product page itself, not buried in footer legal. Customers who understand your returns before buying are customers who dispute less. Make this visible and specific to intimate apparel.
Audit every product image for ambiguous or suggestive framing.
Automated review systems flag imagery before humans see your application. Every product photo must show the garment clearly in a neutral, non-suggestive context. If you use lifestyle shots, ensure they are tasteful and do not imply sexual content or adult retail. Pull 20 random product images and ask yourself honestly: would a corporate brand show this? If the answer is no, reshoot or replace it. This matters because reviewers see your photos first and form opinions fast.
Gather your chargeback and return rate data and present it honestly.
Acquirers will ask for this and you need it ready. Pull your last 12 months of Shopify admin data: how many orders, how many returns, how many chargebacks, what was the reason for each chargeback. Calculate your return rate and your chargeback rate as percentages of total orders. If your rates are high, do not hide it—instead, show the trend. If you have improved them, show that improvement. If you have just started, say so. Honesty here prevents delays later.
Document your customer support process for sizing and disputes.
Underwriters want to see that you do not ignore complaints. Keep records of your support tickets, response times and resolutions for sizing disputes specifically. Show that you offer exchanges, full refunds or store credit promptly. If a customer initiates a chargeback instead of contacting you, that signals poor communication. Set up a simple ticketing system if you do not have one, and train your team to resolve sizing issues before they become chargebacks.
What underwriting will ask you for
- Your return and refund policy, in writing, covering sizing and fit disputes specifically.
- Your chargeback and dispute data for the last 12 months, showing volume and resolution rates.
- Your product photography guidelines and a sample of 10–15 product images showing how you present the category.
- Your customer support contact and escalation procedures for sizing and fit complaints.
- Your processor application history: details of any previous declines or accounts closed.
- Proof of business formation and your merchant descriptor as it appears on customer statements.
- Your traffic and sales volume data for the last 6 months, to establish merchant stability.
Getting underwritten for lingerie
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite lingerie. 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 lingerie
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
- Identify whether the decision turned on a fact or a categoryRead the email carefully. It will say something like 'cannot support' or 'incompatible with our policies'. The next step depends on which it is. If the decision mentioned a specific product, descriptor, licence, or type of dispute, then it may be a fact problem — and facts can change. If it mentioned your business type, industry, or product category as the reason, then no reviewer has authority to except you. Calling Shopify support at this stage usually produces the same email language again, so focus on diagnosis first.
- Gather the evidence for one written appeal — and do it todayThis is the step with a deadline you do not control. Do not wait for the appeal result. Do not assume checkout will keep working while you appeal. Collect the specific evidence that addresses the decision: corrected product screenshots, updated payment descriptors, licence documents, fulfilment records, customer consent, delivery proof. File them all in one place so you can reference them in writing. Set a deadline for the appeal to arrive with Shopify within 48 hours — not because speed guarantees anything, but because waiting is a sunk cost that keeps you from building plan B.
- Appeal once in writing, with only the evidence that counters the decisionWrite directly to the email address that notified you. Be specific: 'You cited [reason]. Here is the evidence that [corrected fact].' Attach or link the documents. Do not argue that the decision is unfair, do not ask for another review, do not promise future compliance. Processors see hundreds of these, and generic appeals are routed as low-priority. You are simply putting the fact on record. If the decision was based on a category prohibition rather than a fact, say so in your diagnostic email to yourself and move on.
- Start plan B the same day: migrate to an accepting gatewayDo not treat the appeal as your plan. Treat it as something you put in motion and then ignore while building what actually survives. A new store on a different payment processor — built into a fresh Shopify domain or migrated into one — with a provider that underwrites your category is the real recovery. The migration takes days, costs a fixed price, and runs in parallel to your appeal. Many merchants never hear back from the appeal. Those who moved the same week have zero downtime in the one business metric that matters: can they take payment.
- If the appeal succeeds, shut down the new store or keep it running dual-processorSuccess is rare and usually takes weeks. If it comes, you will be notified that Shopify Payments is re-enabled. At that point you have a choice: move back to Payments and deactivate the other gateway, keep both running, or stay on the new processor. Dual processing costs more but insures against a second deactivation. Many merchants who have been through this once choose to stay dual, or to stay with the accepting gateway entirely, because the reputational cost of promising customers they can take payment and then freezing is higher than the processing fee difference. That is a business call you make once you are not in crisis mode.
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
Lingerie's size and colour variant matrices are unusually deep—a single item often has 15–20 colour choices and 8–12 size options—and the metafields that hold fit guidance and sizing disclaimers do not survive a naive CSV export. If you move your store by hand, those fit notes vanish silently, and customers land on a product page with no indication that size runs small or that the item is cut generously. On a category where fit is the number-one dispute driver, that omission directly increases chargebacks. The new store's size guides must be rebuilt in the migration, not assumed to copy over.
| What you own | How much of it | What breaks doing it by hand | What we do instead |
|---|---|---|---|
| Product images | 6,400images≈ 27 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 | 800descriptions≈ 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 | 9,600variants≈ 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 | 4,800metafields≈ 32 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 | 950records≈ 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 | 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,900orders≈ 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 | 4menus≈ 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 | 28discounts≈ 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 | 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?
A new legal entity does not reset your payment history or your MATCH status. If you are flagged for disputes or chargebacks, incorporating a new company will not make that history disappear. An acquirer pulls your personal credit and your processing history, and MATCH listings follow the person—not the company—for five years. A new entity only makes sense if you have a genuine operational reason, not as a workaround for underwriting.
Frequently asked
Will Shopify Payments ever work again for a lingerie store?
Not reliably. Stripe's restricted-business list treats intimate apparel as higher-risk, and that classification does not change—it is a category-level decision, not a merchant-level one. Your account status might be restored if chargebacks drop dramatically, but approval is not guaranteed. The realistic answer is to move to a high-risk processor outside Shopify's ecosystem. It is slower to set up, but it is the permanent solution.
Which payment gateway should we use instead?
Authorize.net, PaymentCloud, Soar Payments and Easy Pay Direct publicly advertise support for lingerie and intimate apparel, and Shopify supports integration with all of them. The gateway itself is not the hard part—the hard part is the merchant account behind it. Those processors front accounts through high-risk acquirers, and which one will approve you depends on your chargeback history, your return rates and your sales volume. Rates and reserves are not standard. Use the quote form on this page to speak to brokers who know this category.
How much reserve should we expect?
High-risk lingerie accounts typically carry a rolling reserve of 5–10%, held for 90–180 days. That means 5–10% of your monthly revenue sits in the processor's account, released only after the hold period ends. If your monthly sales are consistent, this becomes your working capital. If they spike or drop, your reserve shifts with them. Ask any processor you speak to about their specific reserve terms before signing, because it directly affects your cash flow.
Will our size guides and fit notes survive a store migration?
Not if you move by hand. Fit guidance, sizing disclaimers and size-run notes typically live in metafields, which CSV exports cannot carry. When you migrate to a new platform or processor, those fields are left behind, and customers see blank product pages. This is why automated migration services rebuild metafields during the transfer—they read the old store's metafields and repopulate the new one. On a category where fit disputes drive chargebacks, this is not cosmetic. Check what the migration service does with metafields before you pay.
Can Shopify Payments be turned back on if I appeal?
Only if the decision was based on a fact — a mislabelled product, unclear descriptor, missing licence, or disputed orders you can now prove were fulfilled. If the decision turned on your category being on the processor's prohibited list, then no reviewer has authority to make an exception, and the appeal will not change it. The decision tells you which it is if you read it carefully.
How long does an appeal take?
There is no published SLA. Merchants commonly report anywhere from a few weeks to no response at all. Some receive a yes or no answer; others receive the same generic reason again without elaboration. The lack of transparency is why you should not wait for the result before building a backup plan. Filing the appeal and then moving to a different processor in parallel is the only timeline you control.
What evidence actually works in an appeal?
Evidence that addresses the specific decision, not the general principle. If you were rejected for mislabelled product names, show the corrected listings. If for unclear payment descriptors, show what the new descriptor is. If for missing licences, provide the document. If for disputed orders, provide proof of fulfilment — tracking, delivery signature, or customer communication proving the goods were as described. Generic promises to comply do not work because the processor's decision was based on documented risk, not intent.
What if Shopify Payments is re-enabled but then disabled again?
This pattern is common. Merchants report being re-enabled, trading for a few weeks, and then receiving a second deactivation notice. If this happens to you, the underlying decision was likely not actually overturned — it was suspended pending more observation. This is why having a backup payment processor in place before the first appeal is worth the setup cost. You are no longer betting the business on a single gateway.
If I move to a different processor, do I have to close my Shopify store?
No. Your store stays live. You simply connect a different gateway for payments — Stripe, Square, PayPal, Braintree, or another processor that underwrites your category. The store itself, your catalog, your customers, and your orders are unaffected. If your new processor later deactivates you as well, migration to a third processor is the same move again. The goal is to find a gateway whose underwriting actually fits your business model and stick with it.
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 →