Shopify Payments disabled, and you sell auto parts. 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 auto parts
Stripe, the processor behind Shopify Payments, lists auto parts as a restricted business — not prohibited, but flagged for active review. The primary trigger is operational risk: your catalog is enormous, fitment data is complex and held in metafields, and returns driven by wrong-part orders are your biggest exposure. When disputes climb, Shopify Payments' underwriting team escalates, and most merchants see their account closed before they even understand why. The secondary trigger is emissions-related parts sold to the US or EU market — some aftermarket components are illegal for road use in those jurisdictions, which creates regulatory liability for the processor.
Rule out the easy fix first — then deal with the real one
Rule this out first. Shopify documents no hemp-style attestation for auto parts, and there is no special application process inside Shopify itself. What you hear from other merchants is that they got approved under a different category code — usually "general merchandise" — and kept their head down. That strategy fails because it relies on invisibility, and invisibility ends the moment your chargeback rate climbs or a processor audit flags your MCC. The honest move is to apply to an acquirer that underwrites auto parts as a category, disclosed truthfully, rather than hoping Shopify's review never deepens.
It only helps if all of these are true:
- Your chargeback and dispute rate must stay below the threshold your processor sets — typically 0.5–1% of volume
- You cannot advertise emissions-related parts or modifications illegal in the US or EU
- Your fitment data must be provably accurate; wrong-part returns spike disputes immediately
- You need documented returns and warranty policies that are visible to customers at checkout
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
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.
💎 High average order value, so fraud and disputes cost more per event
High order values change the arithmetic of every review. A single disputed order can put you over a threshold that a low-value store would take hundreds of chargebacks to reach, and reserves are sized against your exposure rather than your revenue — so expect a bigger one, held longer. Underwriters will want to see delivery evidence and signature confirmation for high-value shipments, and they will look closely at any sudden increase in average order value, because that pattern is also what fraud looks like.
What you actually have to fix
Underwriters do not change their minds because you asked. They change them because the facts changed. For auto parts, these are the facts that move the decision:
Audit your fitment data and fix wrong-part risk
This is the single highest-yield fix: pull your catalog and map every product to the vehicles it fits. Auto parts acquirers run silent chargeback predictions on fitment accuracy — if your database says a suspension part fits a car it does not, that wrong sale converts to a return and a dispute before you know it. Check your metafields for year, make, model and engine-code data. If that data is incomplete or out of sync with your descriptions, disputes will climb faster than fraud. Fix it before you reapply.
Document your return and dispute rate honestly
Pull 12 months of Shopify admin data on returns, refunds and chargebacks, broken down by reason. Calculate your dispute rate as a percentage of total volume. If wrong-part returns are driving the rate up, that is what an underwriter will ask about first — and the honest answer is better than silence. Be ready to show how you plan to reduce wrong-part returns: better fitment warnings, vehicle-selector tools, or tighter quality control on your supplier data.
Remove any parts marketed as illegal for road use
Search your product descriptions and tags for emissions-related language: emissions defeat devices, off-road-only modifications, or parts marketed as illegal in the US or EU. Even if your customers use them off-road, marketing language that positions them as road-use substitutes creates regulatory liability that processors will not carry. Rewrite those listings to be clear about their legal use, or move them to a separate shop that is walled off from your main payments flow if your processor allows it.
Register as a business and keep clean banking records
Auto parts acquirers require proof of business registration, a dedicated business bank account and 3–6 months of clean statements. Do not commingle personal and business spending. If you have been flagged by Shopify Payments, you will also need to disclose any prior processor relationships and the reason they ended. Honesty here saves time: acquirers check anyway, and hiding a closure just moves you to the decline pile.
What underwriting will ask you for
- Year-make-model fitment data mapping and the source of your database — Shopify acquirers ask this before anything else
- A full catalog audit showing high-value items and their typical return rates
- Your chargeback and dispute history for the past 24 months, broken by return reason
- Proof of address and tax registration for your business
- Details of your returns and restocking policy, and how you handle cross-selling to avoid wrong-part orders
- Bank statements showing average monthly volume and transaction size
- Any prior payment processor accounts and the reason they were closed, if applicable
Getting underwritten for auto parts
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite auto parts. 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 auto parts
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 auto parts catalog is dangerous to move by hand because the fitment data lives entirely in metafields — year, make, model, engine code, part category and compatibility flags are all reference or string types that a CSV round-trip cannot preserve correctly. If you copy them naively, the metafields come across but the data relationships break: a product marked as fitting 2010–2015 Civic stays marked that way, but the year-range parsing breaks in the new store, or the vehicle-selector app cannot read it, and customers see fitment information silently vanish. On a product where fitment is the entire value, that is not a cosmetic failure.
| What you own | How much of it | What breaks doing it by hand | What we do instead |
|---|---|---|---|
| Product images | 42,500images≈ 177 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 | 8,500descriptions≈ 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 | 34,000variants≈ 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 | 153,000metafields≈ 1,020 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 | 8,642records≈ 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 | 5,200orders≈ 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 | 35discounts≈ 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 | 22articles & 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 | 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 will not reset your MATCH listing if you personally own the current business — MATCH tracks the person, not the company name, and a five-year record follows you. Creating a new company to evade a processor decline is not a workaround; it is why most second attempts fail. If you genuinely need a new entity for tax or liability reasons, do it — but approach underwriting as the same person, disclosed truthfully.
Frequently asked
Will Shopify Payments give us another chance if we reduce our dispute rate?
Rarely. Once Shopify Payments closes an account for disputes, reapplication is not a documented path — they do not usually reverse the decision if the rate improves. Your best move is to migrate to an acquirer that underwrites auto parts in the first place and will let your rate improve over time. That does require building a new merchant account, which is why catching the problem early matters so much.
Which payment gateway works for auto parts?
Several high-risk acquirers explicitly underwrite auto parts merchants: Authorize.net on a high-risk MID, PaymentCloud, Soar Payments and Easy Pay Direct all advertise this category. Which one will approve you depends on your volume, your dispute history and your fitment-data hygiene. Rather than cold-email them all, use the form on this page to get real quotes. Gateway choice is usually the easy part; the merchant account behind it is where the real decision lives.
Do we have to move our whole store, or can we just switch the payment method?
You need a new merchant account, which typically means a new store or a parallel one that routes to the new processor. Shopify Payments is tightly integrated into the Shopify admin, and you cannot simply "swap out" the processor without rebuilding. If your store is large and your catalog is fitment-heavy, moving by hand will break your metafields. That is why the migration service on this page exists: it moves the catalog, images, descriptions, metafields, SEO data, customers, orders and discounts in one batch, then runs a second pass to verify counts match.
Will our fitment data survive if we move stores?
Only if it is migrated programmatically. Shopify's CSV export cannot carry metafields at all — so if you export your catalog by hand, your year-make-model data, engine codes and fitment flags will be left behind. A proper migration reads your metafields through the GraphQL API and writes them to the new store intact. That is what protects the data layer that makes your catalog valuable.
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 →