New company, new merchant account, and you sell crypto mining hardware. Migrate everything to a new Shopify store.
You have a terminated merchant account and you are thinking about starting a new company so that you can open a new one. That instinct is not wrong. A new entity is the legitimate answer for real structural reasons: splitting a high-risk product line away from your main brand, formalising a partnership split, moving to a new jurisdiction, acquiring another business. But here is what changes and what does not. Every payment acquirer screens merchants against MATCH — the card networks' terminated-merchant file — which is keyed to the person behind the business, not the business name. MATCH follows you for five years, and it follows everyone listed as a beneficial owner, director or signatory. A new company with you as the owner does not present to Stripe, Square or any other acquirer as a new applicant. They see the same person applying again. If you apply truthfully — naming the termination and your role in the previous business — you have done nothing wrong. If you apply as if the history does not exist, every processor will spot it during underwriting, and that becomes a fraud marker, not a fresh start.
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
- "We found a previous merchant account in your name. Please explain the termination" — and your new company's application stalls
- Unable to connect a payment processor because Stripe, Square and others screen the beneficial owner, not the business name
- Advice online suggesting a new LLC is the "workaround" — which makes you sound like you are trying to hide something
- The option to list someone else as the owner to dodge MATCH — which is transaction laundering and criminal
- A legitimate need: you genuinely split from a partner, moved jurisdictions, or want to ring-fence a new product line
The real clock is your runway without payment processing. The second clock is harder to see: every day you delay truthful application is a day closer to the five-year MATCH window closing — but only if the termination reason was legitimate. Running a new company as a shell while the old one's liabilities compound does not help either clock. Truthfulness now is the only move that works later.
Why it happened — specifically for crypto mining hardware
Shopify Payments is underwritten by Stripe, which restricts cryptocurrency services—mining hardware falls under guilt by association, even though you are selling physical goods, not trading or custody services. The primary trigger is the crypto link itself. The secondary trigger is operational: long pre-order lead times on equipment whose resale value moves daily create a pattern of cancellation disputes and chargeback claims that underwriters see as unmanageable risk. Underwriters will interrogate your delivery timeline and refund policy in detail.
Rule out the easy fix first — then deal with the real one
Rule this out first. Shopify does not document a platform route for mining hardware, and the category is not on the allowlist for Shopify Payments. You have no permission-to-apply process through Shopify itself. What merchants try first is opening a standard Shopify Payments account and disclosing the category in the underwriting form, expecting a case-by-case review. This usually fails because Stripe's policy is stated and clear: the category is restricted at the processor level, not at Shopify's discretion. Your only path is to apply through an acquirer that publicly underwrites mining hardware on a high-risk merchant account and connect that gateway to your store.
It only helps if all of these are true:
- Shopify does not offer a documented approval route for this category.
- You must apply to a third-party acquirer, not Shopify Payments.
- The acquirer will underwrite you separately; approval is not guaranteed.
- You will need to prove a realistic pre-order-to-delivery timeline and a clear refund policy.
If any one of them does not hold, you are where everyone else on this page is: you need a store built around a gateway that will actually accept you — and everything you have built has to move into it without losing the catalog, the customers, the order history or the rankings.
What this means for a business like yours
💎 High average order value, so fraud and disputes cost more per event
A new entity does not reset MATCH screening, which follows the person for five years. If your previous account was terminated for fraud, reserves depletion or a single material dispute, that underwriting decision is visible to every new acquirer. High average order value means a single chargeback or fraud event is material to reserves, so underwriters are extremely cautious about applicants with prior terminations. A new legal entity is legitimate if the termination was an entity-level problem — an acquisition, a jurisdiction change, or a ring-fence for a high-risk product line — and disclosed truthfully. Nominee ownership, misdescribed products and running sales through another business's MID are fraud. Disclose the termination, your dispute history and your reserves sizing.
📦 Thousands of SKUs, deep variant matrices, distributor feeds
A new merchant account does not reset MATCH screening, which follows the person for five years. If your previous account was terminated, that decision is visible to every new acquirer. A new legal entity is legitimate if it solves an entity-level problem — an acquisition, a split, or a ring-fence — and disclosed truthfully. The practical consequence is that rebuilding your catalog by hand is impossible; you need an API or bulk-export pathway to move thousands of SKUs, variants and distributor feeds. But if your previous termination was for catalog-level product misclassification or misdescription, moving to a new entity does not fix the underlying problem. Acquirers will scrutinize the new catalog with the same eye. Disclose the termination, audit your product data for accuracy, and ensure your MCC coding is defensible.
What you actually have to fix
Underwriters do not change their minds because you asked. They change them because the facts changed. For crypto mining hardware, these are the facts that move the decision:
Document your pre-order lead times and shipping schedule in writing.
This is the single highest-yield fix because it addresses the underwriter's core concern: cancellation disputes from long waits. Create a page or PDF showing exactly how long a customer waits from order to shipment for each product or product family. Include how supply-chain delays might affect that timeline. Underwriters are not looking for zero delays—they are looking for transparency and a realistic plan. If your lead time is 90 days or more, state it plainly. Hidden timelines or vague "ships when in stock" language is what kills applications.
Write and publish a crystal-clear cancellation and refund policy.
State precisely when a customer can cancel (before payment clears, within 48 hours, never once shipped—pick what you actually do). Explain how you handle refunds if hardware has not shipped yet, and separately, what happens if a customer cancels after shipment has begun. Address the resale-value problem directly: if you allow cancellations but only after deducting a restocking fee because market value has moved, say that. Underwriters need to see that you have thought about dispute scenarios and have a defensible answer.
Gather and present your chargeback and dispute history.
If you have processed through another gateway or processor before, your dispute ratio matters. Request your chargeback statistics from your previous processor and summarize them for the new acquirer. If you are new to payments, say so. If your ratio is above industry norms for high-risk categories, address it head-on in your application: explain what changed operationally or in your policy to prevent repeat disputes.
Verify your supplier and inventory commitments in writing.
Underwriters want evidence that you are not taking pre-orders for hardware you cannot actually deliver. Provide letters or contracts from your suppliers showing that you have secured inventory or firm pre-order capacity. If you drop-ship, provide the supplier agreement. This proves you are not running a financing scheme where customer payments fund your supplier purchases—a pattern that correlates with dispute risk.
What underwriting will ask you for
- A detailed pre-order and delivery timeline showing when customers pay versus when hardware ships.
- Your refund and cancellation policy, including how you handle disputes when resale value has moved.
- Processing history from any previous payment processors, including chargeback and dispute ratios.
- Business registration and tax documentation.
- Bank statements covering at least three months.
- Proof of supplier relationships and inventory commitments.
Getting underwritten for crypto mining hardware
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite crypto mining hardware. 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 crypto mining hardware
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
- Decide whether a new entity is real or a workaroundNew entity is the right move if you are: splitting a high-risk product line away from your core brand to protect both, formalising a genuine partnership split, moving to a new jurisdiction, acquiring another business, or restructuring for tax or operational reasons. It is not the right move if your only reason is that a payment processor said no. If it is real, proceed. If it is a workaround, that intention will show up in underwriting and you will be declined on fraud grounds — worse than being declined on category grounds. Honesty saves time.
- Get a verified backup of your store out nowBefore you apply anywhere, export and store a full copy of your current Shopify store. This is the step with a deadline you do not control. Shopify's CSV export pulls products, variants and basic order data, but it cannot carry metafields, metaobjects, gift card codes, videos, themes, menus, discounts or redirects. If your store is already flagged or restricted, you may lose admin access without warning. With no admin access, there is no API — and with no API, your catalog, order history and custom data are unreachable. Get the copy out while you can still log in, even if you never use it.
- Prepare a truthful application with full termination disclosureGather the termination letter from your previous processor, and the reason code if you have it. When you apply to the new processor — Stripe, Square, Shopify Payments or any other — disclose the termination and your role in the previous business. Do not wait for them to find it. Every processor checks MATCH as part of underwriting. They will see the listing. If you have already disclosed it clearly, they move forward. If they discover it from the MATCH file, the application flags as fraud — deceptive application — and you are declined. Truthfulness is not a disadvantage; it is the only way through.
- Research processors that underwrite your product categoryNot all processors underwrite all categories. Some categories are on some processors' prohibited lists entirely. Before you apply, check whether your product category — not just your new company name — can be underwritten by the processor you have chosen. Publicly advertised category pages on Stripe, Square and others show which businesses they take. This is not a guarantee of approval; it is a filter to avoid wasting time and creating another declined application on your record.
- Move your store to a processor who will underwrite youOnce you have a new merchant account approval, migrate your store to a payment gateway that the new processor supports. This means moving your Shopify store to a new store configured with a compatible gateway. Moving means rebuilding your catalog, re-uploading images, re-adding descriptions, SEO data, metafields, product options, videos, customers, order history, discounts, menus and redirects. Shopify's CSV export cannot carry most of this — so the verified backup you took in step 2 is what lets you do this without losing data. Once the new store is live, you have a working business again. The old store can stay or close; the new processor does not care about historical platform, only about current and ongoing risk.
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
Mining hardware stores are dangerous to move by hand because pre-order and backorder state lives in metafields and custom product options. Expected delivery dates, batch numbers, supplier references and customer notification settings for stock alerts are all stored in custom fields that a naive CSV export cannot carry. If these fields are lost or point at blank references after a migration, customers see no delivery date on their order page and no way to know when their hardware will ship—which immediately triggers support tickets and refund requests.
| What you own | How much of it | What breaks doing it by hand | What we do instead |
|---|---|---|---|
| Product images | 6,800images≈ 28 hrsbulk re-upload, ~15 sec each | By handthe CSV carries image URLs and alt text, but they point at your OLD store's CDN — so the moment the old store goes, every image 404s. Re-upload and Shopify appends a dedupe suffix to the filename, which breaks every theme section and product description that referenced the original URL | Automatedevery file re-uploaded through the API with its alt text and variant attachment intact, its content type preserved so image-restricted fields still accept it, and every reference to the old URL rewritten |
| Product descriptions | 850descriptions≈ 2 hrsone pass to repair inline image links — the CSV carries the text | By handdescriptions are full of inline images and links pointing at the old store's CDN. Paste them into the new store and the text survives perfectly while every embedded image quietly dies — which you usually discover from a customer, not from a report | Automatedbodies copied verbatim, then a second pass rewrites every source-CDN URL inside them to the re-uploaded file on the new store |
| Product attributes & variants | 3,400variants≈ 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 | 5,100metafields≈ 34 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 | 1,016records≈ 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,100customers≈ 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 | 4,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 | 15discounts≈ 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 | 46articles & 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 | 11apps≈ 11 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 processor risk. Underwriters conduct MATCH screening on the people behind the business—owners, signatories, beneficial owners—not just the company name. If you have been declined for mining hardware before, opening a new company under the same person does not reset that history. The new entity will inherit the scrutiny. Your leverage is in fixing the operational and policy issues that triggered the decline, not in restructuring the legal shell.
Frequently asked
Which payment gateway will accept a mining hardware store?
The gateway is not the bottleneck—the merchant account behind it is. Authorize.net, PaymentCloud, Corepay and Easy Pay Direct publicly advertise high-risk mining hardware accounts, and they can connect through gateways Shopify supports. Which one will underwrite you depends on your delivery timeline, your dispute history and your refund policy. Rather than apply blind, use the quote form on this page to get commitments from multiple acquirers before you migrate.
What reserve should I expect?
Mining hardware typically carries a rolling reserve of 10–20%, held for 90–180 days. This means your processor holds that percentage of revenue to cover chargebacks and disputes. Larger reserves apply to newer merchants or those with higher chargeback ratios. Some acquirers will negotiate the reserve down as your history improves, but you should plan for the upper range in your first year of processing.
Will my pre-order data survive a store migration?
Only if the migration tool reads and writes your custom metafields and product options correctly. Shopify's CSV export cannot carry metafields at all, so a hand-copy migration will lose delivery dates, batch numbers and stock alert settings. A proper migration tool—one that uses the Shopify API—will preserve them if they are properly mapped. Before migrating, audit which fields are critical and verify with your migration partner that they can move those fields end-to-end.
Do I need a new business entity to get approved?
No. Opening a new company does not reset your payment processor history because underwriters screen the people behind the business, not just the company name. If you have been declined before, a new legal entity under the same owner will undergo the same scrutiny. The fix is to address the operational issues—delivery timelines, refund policy, dispute handling—that triggered the decline in the first place.
Will a new LLC get me approved when my old company was terminated?
Only if you apply truthfully and disclose the termination. Every processor screens beneficial owners against MATCH, the card networks' terminated-merchant file, keyed to the person — not the company name. They will find your previous termination during underwriting no matter what you call the new entity. If you disclose it upfront, showing the reason and your account in it, that is legitimate and they evaluate based on facts. If they discover it from MATCH without you mentioning it, the application flags as fraud, which is much harder to recover from. The new company is real if you need it for structural reasons; it is not a way to look like someone else.
What is MATCH and why does it follow me to a new company?
MATCH is the card networks' terminated-merchant file, screened by every payment processor during underwriting. It is keyed to the person — name, Tax ID, address — not the business name, and it persists for five years from the termination date. When you apply to a new processor with a new company, they check MATCH as part of standard risk review. Your name and TIN appear in the file, showing a previous termination and the reason code. Every processor sees this. A new LLC with you as the owner does not hide it; it makes the situation clearer, because you are the person applying again.
Can I put someone else's name on the new company to avoid MATCH?
No. Using another person as a nominee or straw owner to obscure your involvement is transaction laundering, classified as MATCH code 03, and it is criminal fraud. Payment processors detect this during underwriting through UBO (ultimate beneficial owner) verification. If discovered, you are not just declined; you face fraud investigation. The legitimate move is to apply in your own name, disclose the previous termination, explain the reason, and show why the new company structure is necessary for real business reasons.
What happens if I apply and hide the previous termination?
The processor will find it. Every major processor screens applicants against MATCH during underwriting. If your name or TIN appears in the file and you do not mention it, the application flags as deceptive application — fraud code 08 or similar — and you are declined. That declined application stays on your record and makes future applications harder, because processors see that you concealed a material fact. Truthful disclosure of a termination is not disqualifying on its own; concealment is.
If I open a new company, can Shopify turn my payments back on?
No. Shopify cannot reinstate a terminated account, and opening a new company does not change that. What you do instead is: build a new Shopify store, connect it to a payment processor willing to underwrite your category and your termination history, and run the business from there. This requires migrating your catalog, images, customers, order history, and custom data to the new store — which is why the verified backup you took before the first store closes is critical. You cannot move gift card codes through any API, so those must be re-issued to affected customers. The new company is legitimate if you need it for structural reasons; the new store is how you keep selling.
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 →