Appealing a Shopify Payments decision, and you sell medical devices. 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 medical devices
Stripe, which underwrites Shopify Payments, restricts prescription-only and regulated medical devices outright. The primary trigger is device class and registration status: a Class I wellness device is ordinary retail, but Class II or higher devices require regulatory clearance evidence. The secondary trigger is efficacy claims — any statement that your device diagnoses, treats or prevents a condition reads to a reviewer as an unproven medical claim, which moves you from restricted to prohibited. Japan additionally restricts health instruments specifically, regardless of class.
Rule out the easy fix first — then deal with the real one
There is no documented Shopify route for medical devices, and the honest reason is that Shopify Payments cannot take them at any class level without a separate underwriting conversation that Stripe controls entirely. What merchants try first is connecting through Shopify's high-risk gateway integrations and hoping the device classification does not come up — it always does. The real path is to find a high-risk acquirer willing to take your specific device class, which means proving your regulatory status upfront: FDA 510(k) clearance, CE marking, or a genuine wellness exemption. That conversation happens outside Shopify.
It only helps if all of these are true:
- Your device must have valid regulatory clearance or a documented exemption for your jurisdiction.
- You must remove any claim that your device diagnoses, treats, prevents or cures a condition.
- You need a high-risk merchant account before connecting any gateway; Shopify integration alone does not secure one.
- Your processing history must show no prior payment declines or chargebacks related to device claims.
- You cannot process if your device is restricted in Japan and you ship there.
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
High average order value means a single fraud or chargeback event can trigger holds or account review, and Shopify Payments applies reserve policy and dispute thresholds that do not always distinguish between isolated incidents and patterns. An appeal works if the decision rested on a specific disputed order you can prove with fulfilment evidence, shipping tracking and communication records. It fails if the review was based on your category's general chargeback profile or perceived fraud risk. Check whether the decision names a specific order or a pattern. If it names one, appeal with evidence. If it is categorical risk, prepare to migrate.
⚖️ Legal status is genuinely contested or actively changing
Legal status that is contested or changing makes processors price legislative risk, not just chargeback risk. Shopify Payments may have disabled you not because of your compliance, but because the category itself is uncertain in law. An appeal based on 'it is legal in my jurisdiction' often fails because the processor avoids regulatory ambiguity entirely. Your appeal succeeds only if you can show the legal question has been definitively resolved in your favour by recent case law or statute. If the law is still genuinely contested, the processor will likely not reverse. Check the legal landscape first—if it is still moving, appeal is a formality. Start plan B immediately.
📦 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.
What you actually have to fix
Underwriters do not change their minds because you asked. They change them because the facts changed. For medical devices, these are the facts that move the decision:
Obtain and document your device's regulatory clearance
This is the highest-yield fix because without it you cannot move forward with any acquirer. If you are selling in the US, you need either an FDA 510(k) clearance letter for your specific device and intended use, or a genuine Class I wellness exemption backed by a legal opinion. If you sell internationally, you need CE marking or equivalent. Gather the actual clearance documents, not a screenshot or a claim — acquirers ask for originals and will verify them.
Remove every medical and efficacy claim from your store
Efficacy claims are the most common decline trigger. Audit your product descriptions, your FAQs, your email sequences and your ads for any statement that your device diagnoses, treats, prevents, cures or manages a condition. This includes indirect claims: 'supports joint health' or 'promotes better sleep' read as therapeutic. Switch to structure-and-function language only — what the device does mechanically, not what it does to the body.
Identify a high-risk acquirer before applying through any gateway
Do not assume that connecting a gateway on Shopify will unlock payment processing. High-risk acquirers for medical devices publicly advertise they take this category, but they run their own underwriting after you apply — they will ask for your clearance documents, your product claims, your processing history and your chargeback data. Start conversations with acquirers who explicitly mention medical devices. Have your regulatory documents ready before you reach out.
Prepare a clear business plan for your underwriting conversation
Acquirers want to understand your customer, your distribution and your claim-handling process. Write a one-page summary of who you sell to, how you acquired your customers so far, what your return and chargeback rates have been, and how you handle customer disputes or product returns. If you have been declined before, explain what changed. Honesty here outweighs a polished pitch.
What underwriting will ask you for
- FDA 510(k) clearance letter or CE certification for your specific device model and intended use
- Product labeling and instructions for use, showing no efficacy or medical claims
- A completed product classification worksheet mapping your device to its FDA class or equivalent regulator
- Supplier or manufacturing agreement proving you are authorised to sell this device
- Your privacy and data-handling policy, particularly if your device collects health information
- Recent bank statements showing transaction history and chargeback ratio
- A detailed business plan describing your target customer and distribution method
Getting underwritten for medical devices
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite medical devices. 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 medical devices
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
Medical device data is dangerous to move by hand because regulatory compliance metadata lives in metafields: FDA clearance references, intended-use codes, contraindication warnings, and device-classification codes are all stored as custom fields that a CSV export cannot carry. If these fields are lost or point to the wrong product during migration, your store renders with incomplete or missing regulatory information — and a customer injured by an unmarked contraindication creates liability that no processor will touch. The compliance chain must survive the move intact.
| What you own | How much of it | What breaks doing it by hand | What we do instead |
|---|---|---|---|
| Product images | 3,600images≈ 15 hrsbulk re-upload, ~15 sec each | By handthe CSV carries image URLs and alt text, but they point at your OLD store's CDN — so the moment the old store goes, every image 404s. Re-upload and Shopify appends a dedupe suffix to the filename, which breaks every theme section and product description that referenced the original URL | Automatedevery file re-uploaded through the API with its alt text and variant attachment intact, its content type preserved so image-restricted fields still accept it, and every reference to the old URL rewritten |
| Product descriptions | 450descriptions≈ 2 hrsone pass to repair inline image links — the CSV carries the text | By handdescriptions are full of inline images and links pointing at the old store's CDN. Paste them into the new store and the text survives perfectly while every embedded image quietly dies — which you usually discover from a customer, not from a report | Automatedbodies copied verbatim, then a second pass rewrites every source-CDN URL inside them to the re-uploaded file on the new store |
| Product attributes & variants | 1,350variants≈ 45 minthe CSV carries these; the time is verifying option order | By handoption ORDER is part of the product's identity. Rebuild "Size, Colour" as "Colour, Size" and every theme swatch, saved customer URL and app that keys on variant position breaks — silently, because the product page still renders | Automatedvariants upserted by SKU with option names and order preserved, so swatches, deep links and app data keep working |
| Metafields & metaobjects | 6,300metafields≈ 42 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 | 600records≈ 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 | 25videos≈ 2 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 | 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 | 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 | 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 | 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 help you in this category. If you have been declined for medical device processing, a new company does not reset your underwriting risk — it simply restarts the same clearance and claims review. MATCH, the payment industry's decline database, follows the person behind the business for five years. A new entity structure without addressing your regulatory status or efficacy claims will result in the same decline.
Frequently asked
Which payment gateway will process medical devices?
The gateway is not the bottleneck — the merchant account is. Several acquirers publicly advertise high-risk medical device processing and integrate with gateways Shopify supports natively, but which one will take your application depends on your device class, your regulatory clearance, your product claims and your history. Authorize.net on a high-risk MID, PaymentCloud, Soar Payments and Easy Pay Direct are known to underwrite in this space, but approval is never guaranteed. Start by preparing your regulatory documents and removing efficacy claims, then approach acquirers directly with a clear application.
What reserve should I expect?
Medical device merchants commonly report reserves of 5–10% rolling, held for 90–180 days. The exact reserve depends on your device class, your clearance status, your transaction volume and the acquirer's risk appetite. Class II devices with solid regulatory documentation often see the lower end; higher-risk classifications or new merchants may see the upper end. Ask any acquirer for their reserve policy before you commit.
Will my product metafields survive a store migration?
Shopify's native CSV export cannot carry metafields at all — not your FDA clearance references, not your device-class codes, not your contraindication warnings. If you migrate by hand, those fields vanish and must be re-entered manually, which is labour-intensive and error-prone on a catalogue of hundreds of devices. A full API-backed migration preserves every metafield intact, which is why compliance-heavy categories like medical devices are the highest-risk candidates for manual moves.
Can I start selling if I do not have FDA clearance yet?
No. Stripe and high-risk acquirers will not process a device without regulatory clearance or a documented exemption for your jurisdiction. If you are still in the FDA review process or pursuing a 510(k), you cannot legally take payments until clearance is granted. Attempting to process before clearance invites processor decline, chargeback exposure and regulatory action. Wait for the clearance letter before building your Shopify store.
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 →