Prohibited business type, and you sell gift cards and stored value. Migrate everything to a new Shopify store.
You applied for Shopify Payments and got a rejection that said your business type is not supported. You then searched Shopify's help centre for the prohibited list and found nothing, because Shopify does not publish one. Here is why that matters, and what to do. Shopify Payments is underwritten by a payment processor — Stripe, PayPal or Adyen, depending on your country. Shopify's own terms defer to the processor's underwriting rules. That means the restriction you hit is not Shopify's rule. It is the processor's rule, and it lives in a document you need to find and read. The operative document is your processor's restricted-businesses list. That list is not a vague policy. It is a specific set of business types, and if you can prove you do not belong in it, or that you belong in a carve-out, you have a move. If you do belong in it, a third-party gateway — one with a different acquiring bank — may accept you. Find out which one you hit first.
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
- "Your business type is not currently supported" — with no link to which list that came from
- Shopify help articles about Stripe's restricted list, but no link to Stripe's actual list — and Stripe's list changes
- Confusion about whether this is a Shopify decision or a processor decision
- Assumption that switching to another Shopify theme or store will reset it
- Search results for "Shopify prohibited business" returning other merchants' stories, not policy
Time matters here, but not for the reason you think. The decision is final unless you have new facts. A processor will not reconsider on the same evidence. But if you can submit a real carve-out — a specific merchant code, a subcategory exception, a proof of age or licence — the window to reapply stays open only as long as your business looks the same to their automated screening. The move is to find which processor will take you, and that is urgent because the longer you operate without a payment gateway, the harder it becomes to get one.
Why it happened — specifically for gift cards and stored value
Shopify Payments is underwritten by Stripe, and Stripe explicitly restricts stored value products. The primary trigger is the nature of the product itself: once a gift card is redeemed, the transaction is effectively irreversible and the funds are instantly liquid. This makes it a favourite target for card-testing fraud and stolen-card schemes. The secondary trigger is your chargeback history — any merchant with meaningful gift card volume typically shows elevated chargebacks, which alone can bring a decline even if the product category were permitted.
Rule out the easy fix first — then deal with the real one
Rule this out first. Shopify does not document a specific platform route for gift cards and stored value the way it does for some other restricted categories. What merchants usually try is requesting an exception through Shopify Support, citing low fraud or a clean chargeback record. That request is almost always declined because Stripe's policy is not negotiable at the Shopify level. The honest equivalent is that you need to move to an acquirer who specifically underwrites this category — one willing to price in the reserve and the chargeback risk — and then migrate your store to a payment gateway they actually support.
It only helps if all of these are true:
- Your chargeback ratio must be below 1% and documented for the last 12 months.
- You must have been processing for at least 24 months with no gaps or escalations.
- Your gift card terms must clearly state that cards are non-refundable and have an expiry date.
- You must be able to show that card-testing attempts have been blocked by your fraud tools.
- Your annual gift card sales volume must be under a threshold the acquirer sets during underwriting.
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
When average order value is high, a single fraud or chargeback event is material to your reserves and your underwriting profile. Shopify Payments does not publish its own prohibited list — it delegates to the processor (Stripe, PayPal or Adyen). That processor is pricing your risk, not just your category. If you are marked as prohibited, it is often because your dispute rate or fraud rate signalled risk, not because your product type is forbidden. Before approaching anyone new, pull your Stripe dashboard data: your dispute rate, chargeback rate, and average dispute amount. That evidence tells an underwriter whether the issue is category or performance. If it is performance, fix it. If it is category, you need a processor who accepts that category at that risk level.
🔁 Recurring billing is a large share of revenue
Shopify Payments delegates to your country's processor (Stripe, PayPal or Adyen). If you lose that processor, your stored payment methods stop working immediately, and every subscriber's next billing attempt fails. Those stored methods are held by the processor, not by you, and they cannot be exported or moved. A subscription business loses new orders and then bleeds existing revenue every day the account stays closed. Restarting means either a processor-to-processor migration arranged in advance, or asking thousands of customers to re-enter a card — which never fully recovers. Before anything else, deal with your subscription book and whether your replacement processor can take it on.
What you actually have to fix
Underwriters do not change their minds because you asked. They change them because the facts changed. For gift cards and stored value, these are the facts that move the decision:
Document your chargeback and card-testing history in detail
This is the single highest-yield fix because every acquirer in this category will ask for it. Pull 24 months of chargeback reports from your current processor and sort them by type: true chargebacks from customers disputing legitimate gift card purchases, versus card-testing attempts that succeeded because the card was stolen. Acquirers assume stored value attracts fraud; your job is to show that you have either kept it out or handled it so well that the risk is containable. If your chargeback ratio is high, that alone may make you uninsurable, and no other fix will matter.
Rewrite your gift card terms to remove any refund obligation
Most gift cards sold online come with implicit or explicit promises that they can be refunded or converted to store credit under certain conditions. Stripe and conservative acquirers read any refund language as a liability: it means the cardholder can claim the transaction was unauthorised, then you will refund it, and then they will get the original card issuer to refund them too. Your terms must state plainly that gift cards are non-refundable once purchased, that they are not insurance or an escrow, and that redemption is final. Display this prominently and get legal counsel to review the language for your jurisdiction.
Set a hard expiry date on every gift card issued
Gift cards without expiry dates look to underwriters like you are holding customer funds indefinitely — a liability and a reserve driver. Set an expiry of 12 to 36 months from issue, depending on your business model, and enforce it in your system. Make the expiry date visible on the card itself and in the customer's account, and warn them at redemption time if they are close. This converts an open-ended liability into a time-bound one and signals to an acquirer that you have thought about risk.
Audit your fraud tooling and document what card-testing you have blocked
You need to show that you are not a soft target. Run a fraud filter on all gift card purchases — basic velocity checks (more than three purchases from the same card in one day), BIN mismatch, and AVS or CVV failures — and keep logs of what you blocked. Pull those logs and include them in your application. Acquirers assume you will see fraud attempts; they want to know you are catching them before they become chargebacks. If you are not running any fraud tooling at all, that is a compliance failure you must fix before applying.
What underwriting will ask you for
- Gift card terms and conditions exactly as displayed to the customer at point of sale.
- Chargeback and fraud reports for the last 24 months, broken down by card-testing versus customer disputes.
- Bank statements and processing reports showing gift card revenue separately from merchandise sales.
- Your current fraud filter settings and any third-party fraud tools you run.
- Customer service logs showing dispute resolution for common refund requests on gift cards.
- A breakdown of your gift card redemption rate and average time-to-redemption by cohort.
- Proof of any chargeback management or reserve agreements you have held with previous processors.
Getting underwritten for gift cards and stored value
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite gift cards and stored value. 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 gift cards and stored value
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
- Find your processor and read its actual restricted listFirst: confirm whether you are in Shopify Payments or applying now. If you are in a Shopify store already, your processor is in your admin under Settings → Payment providers. If you are applying, your processor is determined by your country — see shopify.com/legal/processor-list. Once you have the name, find the processor's restricted-businesses document. For Stripe, this is at stripe.com/docs/connect/restricted-businesses. Do not rely on secondhand descriptions or forum posts. Read the actual list. Your business type may be listed with a carve-out you did not know existed.
- Check whether you meet a documented exceptionRestricted lists often include carve-outs. A category like "adult" may permit age-gating and ID verification. A category like "financial services" may permit licensed brokers but not unlicensed advisors. A category like "gambling" may permit lottery retailers but not online betting. Find the line that describes your business and read every word after it. If there is a condition you can meet — a specific merchant code, a government licence, a regulatory exemption — note it. This is the only path to reapplication on the same processor.
- Reapply with documentation of the exceptionIf you found an exception that applies to you, gather the documentation it requires: a licence, a registration, a certification, a merchant code, proof of age-gating, or whatever the list specifies. Submit a new application to the same processor with that documentation attached and a short note saying: "I believe I meet the exception at [the exact line]. My documentation is attached." Include the reference to the specific exception in the list itself. Do not argue that the rule is unfair. Do not submit a general appeal. The processor's automated screening will reject you again unless you are answering a specific carve-out.
- Get a verified copy of your store — before applying elsewhereIf the processor will not move, you will move to a different gateway. This is the moment to export a full backup of your store, before anything else changes. You need your catalog, your customers, your order history, your SEO metadata, your theme settings, your discount codes — everything. Shopify's CSV export cannot carry metafields, orders, gift card codes, videos, menus, discounts or redirects. That is the strongest reason to move to a new store built around a processor that will accept you: a fresh build with a proper migration handles the things CSV cannot. Get the backup now, while you have access and the store is still live.
- Move to a new store with a processor that accepts your businessOnce you know which processor rejected you, and whether you can appeal it, find a payment gateway that accepts your category. This means a different processor, which usually means a new Shopify store built around that gateway. A migration service can move your catalog, images, SEO data, theme, customers, orders and other data into the new store, then run the migration twice and compare counts to check nothing was lost. The move costs money and time, but it is the legitimate path from a misfit processor to a fit one. You are not hiding anything; you are disclosing your category truthfully to a processor who will accept it.
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
Gift card data is dangerous to move by hand because Shopify's gift card codes themselves are unreadable through any API — they are encrypted and stored server-side. If you try to export them, you get the structure but not the codes, so you cannot re-issue them into a new store. Outstanding balances can only be re-issued as new codes or as store credit, which means a real migration must plan for either a manual reconciliation window or a commitment to honour old codes in the old store while directing new customers to the new one. Get this wrong and you will either lose balances or expose yourself to double-redemption disputes.
| What you own | How much of it | What breaks doing it by hand | What we do instead |
|---|---|---|---|
| Product images | 540images≈ 2 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 | 180descriptions≈ 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 | 180variants≈ 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 | 1,440metafields≈ 10 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 | 337records≈ 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 |
| Customers | 8,500customers≈ 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 | 12,000orders≈ 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 |
| Gift card balances | 4,200gift cardsno manual routecannot be moved by anyone | By handthis is the one thing on this page that truly cannot be moved by anyone. Gift card codes are unreadable through EVERY Shopify API, by design — no tool, ours included, can copy them. Those balances are real money you owe real customers, and abandoning the old store does not abandon the liability: the customers still turn up expecting you to honour it | Automatedwe re-issue each card with an identical balance, customer and expiry date, and hand you the new codes as a CSV with customer email copy ready to send — the only honest way to move them |
| Blogs & pages | 37articles & pages≈ 2 hrsrecreated one at a time, ~4 min each | By handno CSV route for either. Articles also have no SEO fields of their own — their title and description tags live in metafields — so a hand-rebuilt blog loses its SEO even when every word of the text is right | Automatedarticles and pages recreated with authors, tags and publish dates, their SEO written to the metafields Shopify actually stores it in, and inline image URLs rewritten |
| Apps & app data | 8apps≈ 8 hrsabout 1 hr per app to reinstall, reconfigure and re-test | By handmost app data lives in metafields on your products and customers, so reinstalling the app gets you an empty app: reviews gone, subscription plans gone, loyalty balances gone, bundles gone. Flows and automations have to be rebuilt by hand and re-tested, and anything with its own billing has to be re-subscribed | Automatedthe metafield data your apps rely on migrates with the products and customers it hangs off, so a reinstalled app finds its data waiting instead of an empty store |
See these numbers for YOUR store, free
The figures above are a typical store in your category. The demo scan connects read-only to yours and counts the real thing — every product, variant, image, customer, order and metafield — then tells you exactly what a migration would carry across. No card, and it never writes to your store.
▶ Run the free demo scanDoes this need a new company?
A new legal entity will not help you here and will not reset your MATCH listing. Stripe's restriction on stored value is categorical, not a judgment on your company's history. What matters to an acquirer is your processing history as a person or business — chargebacks, card-testing volume, redemption patterns — all of which follow you across entities. A new company is more likely to fail underwriting, not less, because it has no history at all.
Frequently asked
Which payment gateway can actually process gift cards for me?
The gateway is straightforward — Authorize.net on a high-risk MID, PaymentCloud, Soar Payments and Easy Pay Direct all advertise this category. The real question is which acquirer behind them will take you. That depends on your chargeback ratio, your fraud history and your redemption speed. Rather than cold-email brokers, use the quote form on this page to connect with acquirers who specialise in stored value.
Why is my reserve so large, and how long will it be held?
Stored value is the highest-reserve category because the funds are instantly liquid and nearly impossible to reverse once redeemed. An acquirer will typically hold 10–25% of your monthly volume in rolling reserve for 180 days or more. That money is insurance against fraud chargebacks and card-testing losses. The exact percentage and hold period depend on your chargeback history and your sales volume — a cleaner history gets a smaller reserve and a shorter hold.
Can I move my outstanding gift card balances to a new store?
No. Shopify gift card codes are encrypted and cannot be read through any API, so you cannot export the actual codes. Outstanding balances must be re-issued as new codes in the new store, or you must honour them in the old store indefinitely and direct customers to redeem there. Plan for a reconciliation window where you issue replacement codes or store credit to customers who ask, and budget for a small loss from cards that go unredeemed.
If I get declined by one acquirer, will another even look at me?
Yes, but the clock is ticking. If you apply to multiple acquirers quickly without being declined, each will see a clean application. If you get declined, that decline is recorded in the industry database and subsequent acquirers will see it and be more conservative. Apply to one or two at a time and wait for a clear yes or no before moving on. Declining merchants commonly improve their application and reapply after six months.
Is there a Shopify Payments prohibited business list I can check?
No. Shopify Payments does not publish a list of prohibited business types. The payment processor for your country publishes one instead. Shopify's terms say the processor decides which categories are supported. If you were rejected, you need the processor's actual list, not Shopify's. You can find your processor at shopify.com/legal/processor-list, then search that processor's website for "restricted businesses".
Why did I get rejected if my business is legal?
Legal status and payment processor underwriting are different things. A processor may restrict a category for compliance, fraud, or chargebacks — not because it is illegal, but because the processor's risk profile does not cover it. Adult services, gambling, CBD, debt settlement and firearms are commonly restricted even where they are legal. The processor makes the call, and legality is not the only factor.
Can I reapply to the same processor?
Only if you have new facts. A processor will not reconsider on identical information. But if the restricted list includes a carve-out for your business — a specific merchant code, a licence requirement, an age-gating requirement — and you can document that you meet it, you can reapply with that evidence. Read the actual list line by line. Many merchants miss the exceptions because they are buried in small text.
What if I open a new store or company?
A new store on the same processor will be screened against the same criteria you just failed. A new company does not change your screening category. The processor is evaluating your business type and category, not your legal entity name. If Stripe rejected your business type as an individual, Stripe will reject it again when you apply as a limited company. The category itself is the issue, not your legal structure.
Can you turn Shopify Payments back on or move me to a different processor?
No. We cannot persuade a processor to accept your category or change their underwriting decision. What we do is help you move your entire store — catalog, customers, orders, SEO data, theme, everything — to a new store built around a processor that will accept your business type. We move the data, you provide the processor. The move is fixed price from £247, and we run the migration twice to compare counts against what was lost.
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 →