Finding a high-risk payment gateway, and you sell packaged food. Migrate everything to a new Shopify store.
You have been looking at lists of payment gateways that work with Shopify. Stripe, Square, PayPal, Adyen — they all have checkboxes next to them saying 'high-risk' or 'supports adult' or 'accepts CBD'. Here is what those lists do not say. The gateway is the technical plumbing. It connects your checkout to a payment processor. Shopify supports dozens of them natively, and more through apps. But the gateway itself does not underwrite you. Behind every gateway sits a merchant account — a MID, a relationship with an acquiring bank or payment processor. That is where the actual application lives. That is where a human or an algorithm decides whether to accept your business type, your geography, your volume, your history. A gateway that 'supports high-risk' merchants does not mean it will approve you. It means it accepts applications from people in your category. The approval is separate, specific, and yours alone. Merchants commonly spend weeks comparing gateways and hours on the actual underwriting — and then get declined by the merchant account on day one.
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
- Gateway comparison lists showing 20 options, each marked 'high-risk friendly', with no mention of MID approval odds
- Shopify's app store showing third-party gateways as a simple install, with no warning about the separate merchant account application
- A message that a gateway 'accepts high-risk merchants', interpreted as approval, actually meaning only that they take applications
- Assumption that if Shopify integrates a gateway, it will approve a new high-risk merchant — not true
- Discovery three weeks into setup that the gateway's parent processor has declined the merchant account application
The merchant account decision is the actual deadline. You can prepare the technical setup while applications are pending, but nothing clears until underwriting says yes. Some processors publish estimated timelines; most do not. Time in underwriting is time your store makes no money.
Why it happened — specifically for packaged food
Stripe, which underwrites Shopify Payments, lists packaged food and beverages as a restricted business in Thailand and Indonesia, which means any transaction routed to those jurisdictions will be blocked outright. More commonly in the US and Europe, a food brand is approved but then dropped when dispute rates climb — subscription boxes and meal kits see churn-driven chargebacks that trigger reserve holds and then termination. The secondary trigger is functional and health claims: if your product is marketed as treating, preventing or curing a condition, or as having a drug-like effect, it shifts from restricted to prohibited, because it reads as an unapproved drug.
Rule out the easy fix first — then deal with the real one
There is no documented platform route for food and beverages, so rule out the Attestation model entirely. What most merchants try first is connecting through Shopify Payments with generic category coding, hoping the underwriter will not notice the subscription model or the health claims. That approach works until the first chargeback spike, at which point the account is frozen pending a manual review. The honest path is to approach a high-risk acquirer openly with your full processing history, your chargeback data and your product claims, then build on their MID rather than Shopify Payments. You will pay more, carry a reserve, and wait longer — but you will not be surprised mid-month by a frozen account.
It only helps if all of these are true:
- No functional or health claims on any product page, email or social channel.
- Chargeback rate below 1% across your processing history.
- Subscription churn tracked and documented for the acquirer's review.
- Shipping and fulfillment partners capable of handling perishable goods.
- Products compliant with allergen labelling in all jurisdictions you ship to.
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
💊 Sold to be swallowed, inhaled or applied — health claims and product-liability risk
When you find a gateway that lists ingestible merchants as accepted, remember that the gateway is only the technical connection—the actual underwriting happens at the merchant account level. The acquirer will inspect your product claims, certificates of analysis, and dispute history as the real basis for acceptance or rejection. Processors in this space price for chargeback risk heavily, because 'it did not work' disputes are routine in consumables. You will likely face a higher percentage rate, mandatory reserve and volume cap than mainstream merchants—not because the gateway exists, but because the underwriter sees the category. Get your claims language reviewed before you apply anywhere. A gateway list is not a promise of approval.
🔁 Recurring billing is a large share of revenue
For a subscription business, the gateway is the pipe but the merchant account is the underwriting—and the underwriter will scrutinise your chargeback rate, refund rate, and whether your billing model is transparent at checkout. More importantly, any stored payment methods in your current processor are held there and cannot be exported to a new gateway; you will either have to arrange a processor-to-processor migration in advance or ask customers to re-enter cards, which crushes recovery rates. If you switch gateways without planning the migration, your entire recurring revenue book stops processing immediately. Deal with the stored payment problem before you approach anyone new. Expect worse terms—higher rate, reserve, lower volume cap. The gateway fee Shopify charges compounds monthly.
📦 Thousands of SKUs, deep variant matrices, distributor feeds
A large catalog with thousands of SKUs and variant matrices means you cannot hand-rebuild if you move gateways. The merchant account underwriter will want evidence that your system can reliably avoid selling prohibited items into prohibited jurisdictions—which matters most for weapons or age-restricted goods, but also for any category with geography-specific restrictions. Shopify's CSV export cannot carry videos, theme, metafields, discounts, redirects or orders, so a hand-migration is impossible anyway. When you approach a new acquirer, they will ask how you manage compliance at scale across your entire product range. A gateway that accepts your category means nothing if you cannot prove your SKU-level restrictions actually work. Plan the full migration—data structure, theme, image quality, SEO redirects—before you commit to a new processor. Underwriters want to see that you have already solved the operational problem, not that you are learning as you go.
What you actually have to fix
Underwriters do not change their minds because you asked. They change them because the facts changed. For packaged food, these are the facts that move the decision:
Remove all functional and health language from product pages and marketing
This is the single highest-yield fix. Any claim that your product treats, prevents, manages or cures a condition — or that it has a drug-like physiological effect — reads to an underwriter as an unapproved drug claim, which moves you from restricted to prohibited instantly. Scan your product descriptions, your homepage, your email campaigns, your blog and any customer reviews you display. Structure and function language is defensible; therapeutic claims are not. Rephrase 'supports immune function' as 'contains vitamin C' or leave the claim out entirely.
Document your subscription churn and establish a target refund rate below 1%
High-risk acquirers will ask for your retention cohorts and your monthly refund rate. If your subscription model loses more than a small fraction of customers to chargebacks and refund requests, the acquirer will either decline you outright or impose a punishing reserve. Calculate your actual churn for the past 12 months by cohort, your refund rate month-on-month, and the most common cancellation reasons. Be ready to show that you can deliver product reliably and handle customer objections before they escalate to chargebacks.
Audit your labels and ingredient statements against your shipping jurisdictions
Food safety and allergen labelling are not discretionary. Before you approach an acquirer, verify that every product label meets the regulatory requirements of every jurisdiction you ship to. That includes ingredient statements in the local language, accurate allergen declarations, and net weight or volume statements. A failed food safety audit or a customer report of undeclared allergens will end any merchant account immediately.
Gather your full chargeback and dispute log and be ready to explain every one
Acquirers will pull your processing history and scrutinise your disputes. If you have been declined or terminated before, the reason will be visible to the new acquirer. Go through the past 12 months of chargebacks and refunds and write down what happened: was it a customer complaint about freshness, an allergen issue, an unauthorised transaction, or someone who changed their mind about a subscription? Honesty here costs less than hiding it. A spike in disputes around a specific product or a seasonal issue is explainable; a pattern of refund requests you cannot account for will kill the application.
What underwriting will ask you for
- Complete product list with ingredient statements and allergen declarations for each SKU.
- Chargeback and dispute history for the past 12 months, itemised by reason.
- Subscription retention and cancellation data: cohort churn, refund rates, and average customer lifetime.
- Samples of your packaging, labels and product photography as they appear to customers.
- Bank statements and processing history for the past 6 months showing sales volume and refund patterns.
- Your shipping and fulfillment partner's credentials, including how they handle perishables and temperature control.
- Customer complaints log or support tickets from the past 12 months, noting refund requests and reasons.
Getting underwritten for packaged food
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite packaged food. 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 packaged food
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
- Separate the gateway from the merchant account in your mindThe Shopify integration list shows what can be plugged in technically. The processor's application is what actually evaluates you. Installing a gateway in Shopify does not skip the merchant account step. It is the setup you can do in parallel. Write down the processor's name — the company that will actually underwrite you — separately from the gateway name. That distinction will save you weeks of confusion. When you get declined, you will know whether to blame the gateway (which is rare) or the underwriting criteria (which is the reason 99 times out of 100).
- Research the processor's actual criteria, not the gateway's marketingThe gateway's website will say 'we support high-risk merchants'. The processor's underwriting criteria — the thing that matters — lives in their application form, their policies, or a conversation with their underwriting team. Find it before you apply. Call them. Ask what business types they actually underwrite, what volume they need to see, whether they want reserves, what your rate will be. Cheaper gateways often cost more once you factor in reserves, higher rates, and transaction fees. Shopify also charges an additional third-party-gateway transaction fee on top of the processor's rate — tiered by your plan. That fee exists. Budget for it.
- Prepare your application materials while applications are pendingWhile the merchant account is being underwritten, you are waiting. Use that time to collect what processors will ask for: business registration, tax ID, processing history, bank statements, identity verification. Different processors have different checklists. Some will ask for personal guarantees. Some will want to know about past declined accounts. If you have been through a payment processor decline before, have that story ready and honest. Many processors now ask about MATCH history — the card networks' list of terminated merchants — and the answer matters more than the story. If you are on it, disclose it. Lying will disqualify you faster than the truth.
- Apply to multiple processors in parallel, not sequentiallyDo not pick one gateway, apply, get declined, then pick another. Research and apply to three to five processors whose criteria match your business type, in the same week if possible. Each application goes into the processor's system, and a decline does not flag you across all of them. But time between applications is time your store makes no money. Applications take days to weeks to process, so start the stack now rather than one at a time. Keep notes on each processor's criteria, rate, timeline, and reserve requirement so you can compare approved offers.
- Plan for worse terms than Shopify Payments, and budget the cost inIf you move to a third-party gateway, expect higher transaction rates, volume caps, rolling reserves, or setup fees. These are not bugs — they are how high-risk underwriting works. The processor is taking on more chargeback risk or regulatory scrutiny, so the pricing reflects that. Shopify Payments was a flat rate with no reserve. Your new processor will likely have both a rate and a reserve — money held back against chargebacks, sometimes 10 to 25 percent of monthly volume. That is working capital you do not have. Factor it into your business plan. If you cannot operate with a reserve, that processor is not a fit, and you move to the next application.
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
A packaged food store's data is dangerous to move by hand because compliance and supply-chain metadata lives in metafields. Allergen declarations, ingredients, certifications, country of origin and batch-traceability codes are stored as metafield references or JSON that a CSV export cannot carry at all. If you move the catalog naively, those fields render blank, and a retailer selling allergen-undeclared food has a liability problem that no migration service can fix. The product descriptions and images will copy, but the food-safety metadata will not.
| What you own | How much of it | What breaks doing it by hand | What we do instead |
|---|---|---|---|
| Product images | 1,200images≈ 5 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 | 200descriptions≈ 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 | 800variants≈ 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,600metafields≈ 11 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 | 357records≈ 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 | 5videos≈ 20 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 | 8,000customers≈ 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 | 40discounts≈ 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 | 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?
You do not need a new legal entity to work with a high-risk acquirer, and creating one will not reset your payment history or your MATCH listing. If you have been terminated by Shopify Payments or another processor, that event stays attached to the person, not the business name — so a rebranded store under a new company is immediately visible to any underwriter running a MATCH search. Start your application with honest disclosure rather than a fresh company.
Frequently asked
Which gateway will actually approve a food and beverage brand?
Several high-risk acquirers publicly underwrite packaged food — Authorize.net on a high-risk MID, PaymentCloud, Soar Payments and Easy Pay Direct among them — but approval is not guaranteed and depends on your dispute history, your product claims and your subscription model. Rather than cold-email brokers, use the referral form on this page to get a qualified quote. The gateway itself is the easy part; the merchant account behind it is where the decision lives.
What reserve should I expect if I get approved?
Food and beverages on subscription typically carry a rolling reserve of 5–10% held for 90–180 days. The reserve protects the acquirer against chargeback spikes and refund surges during seasonal swings or if a shipment arrives damaged. Some acquirers will reduce the reserve after 6–12 months of clean processing; others will hold it for the life of the account. Ask the underwriter upfront what the reserve policy is and how you can earn a reduction.
Do my subscription data and customer retention records survive a store move?
Shopify's CSV export cannot carry subscription data, metafields, orders or customer records through a normal export. If you migrate to a new Shopify store, you will lose your subscription relationships and your historical order data unless you use a specialised migration tool that reads the API directly. A standard CSV move will show your customers and products, but the subscription state and the order history will be blank or broken, and you will need to rebuild your recurring revenue model from scratch.
What happens if I get declined again after applying with a new gateway?
If you are declined a second time, it usually means the same reason — disputes, health claims, or processing history — is still on file. Ask the underwriter for specific feedback in writing, fix only that issue, and wait at least 30 days before reapplying with a different acquirer. Do not apply to five processors at once; each application leaves a footprint in MATCH, and multiple hard declines make the next application harder. One fix, one application, one wait.
What is the difference between a payment gateway and a merchant account?
The gateway is the software bridge connecting your Shopify checkout to a payment processor — it handles the technical flow of card data. The merchant account is your commercial relationship with the processor, and it is where underwriting happens. You can have the gateway installed in Shopify and still not be approved for the merchant account. The gateway is necessary but not sufficient.
If Shopify integrates a third-party gateway, will it approve me?
No. Shopify's integration of a gateway means only that the technical connection is possible. The merchant account approval comes from the processor that owns the gateway, using their own underwriting criteria. Some of those processors are more liberal with high-risk categories than others, but none of them approve everyone. Integration and approval are separate decisions.
Will I have to pay Shopify a fee on top of the processor's rate?
Yes. Shopify charges an additional third-party-gateway transaction fee on top of what the processor charges. This fee is tiered by your plan. It is a real cost and should be factored into your rate comparison when you are deciding which processor to apply to. The processor's advertised rate is not your total rate.
Can I appeal if a processor declines my merchant account application?
You cannot appeal to force approval, but you can reapply later if your circumstances change meaningfully — higher volume, longer business history, reserves in place, or a shift in your business type toward lower-risk activity. Some merchants reapply after six months to a year. Most processors will consider a fresh application if your profile is different. Lying on the reapplication will disqualify you entirely.
If I get declined by one gateway processor, will other processors know about it?
Each processor screens applications against the card networks' MATCH file — the list of terminated merchants — but they do not automatically see declines from other processors. A decline itself is not instantly shared across the industry. However, multiple hard applications in a short time can raise flags for some processors, and if you are on MATCH, every processor will see it. Apply thoughtfully to a few good fits rather than scattering applications everywhere. If you have been declined before, disclose it in the new application.
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 →