High chargeback rate, and you sell packaged food. Migrate everything to a new Shopify store.
The warning comes from your processor, not your customers: your chargeback or dispute rate has climbed above their threshold, and they are putting your account under review. This is not a suspension yet. It is a formal notice that you have entered a monitoring programme run by the card networks themselves—Visa and Mastercard track dispute rates at every merchant, and when the rate hits a certain point, the networks impose fines on the acquiring bank, not on you directly, but the bank passes that cost down. The acquirer acts before the threshold bites because the alternative is to hemorrhage money on your account. But here is what almost nobody explains: a high chargeback rate is almost never a processor problem or a Shopify problem. It is a real pattern in your orders. Customers are not recognizing the charge, or they ordered something that did not arrive, or the description on their bank statement is so unclear they assume fraud. Until you fix what actually happened in those orders, you will carry this pattern to the next processor. So the move is not to hunt for a more lenient gateway. It is to find and fix what your customers are disputing.
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 account is enrolled in a card network dispute-monitoring programme" — with a rate percentage but no clear explanation of what changed
- A notice of financial penalties per dispute, or a mandatory reserve holding back a percentage of payouts
- Support refusing to process refunds for customers who have already filed chargebacks, citing policy
- A timeline: "Reduce your dispute rate to X% within 90 days or your account will be escalated"
- Email language citing your billing descriptor, delivery confirmation or customer communication as a risk factor
The clock that matters is the one the card networks set: roughly 0.9%–1.5% of transactions. Once your rate hits that, the networks themselves penalize the acquiring bank per dispute, which forces fast action. You cannot negotiate a network threshold, so the real deadline is proof that you have fixed the underlying problem—clear billing, trackable delivery, and responsive support before customers dispute.
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
For anything people swallow, inhale or apply, disputes almost always centre on claimed effect, not defect. A customer who believes the product did not work files a chargeback as a refund attempt, not fraud. The card networks' dispute-monitoring programmes trigger at roughly 0.9%–1.5% of transactions, and ingestibles hit those thresholds fastest because refund-rate disputes are hard to defend. Before approaching a new processor, fix your billing descriptor to match exactly what appears on the customer's statement, collect delivery confirmation for every order, and respond to support requests before they become disputes. Tooling matters too: use your gateway's dispute-deflection features to catch refund requests before they network.
🔁 Recurring billing is a large share of revenue
A high chargeback rate is catastrophic for a subscription business because stored payment methods decline at scale the moment your dispute ratio climbs. The card networks enrol you in monitoring programmes at roughly 0.9%–1.5% of transactions, which triggers processor action before it feels urgent to you. Every subscription renewal that fails becomes a chargeback candidate, accelerating the cycle. Your existing subscribers' payment methods are held by the processor and cannot be migrated pre-emptively; you must fix the rate before switching gateways or lose the entire renewal engine. Start with billing descriptor clarity and delivery confirmation. Then deploy dispute-deflection tooling and respond to every support request before it becomes a chargeback. Speed is survival here.
📦 Thousands of SKUs, deep variant matrices, distributor feeds
A high chargeback rate across thousands of SKUs is almost impossible to debug because you cannot isolate which products or variants are generating disputes. The card networks' dispute-monitoring programmes trigger at roughly 0.9%–1.5% of transactions, and once enrolled you pay per-dispute penalties. Your scale works against you: rebuilding your catalog in a new system is expensive and time-consuming, so you cannot afford to migrate twice. Start with the basics: billing descriptor clarity, delivery confirmation, responsive support. Then segment your dispute data by category, variant, and fulfillment type to find the pattern. Deploy dispute-deflection tooling immediately. A catalog migration is not the fix—understanding which part of your offering is driving the rate is. Only then should you move gateways.
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
- Audit every recent chargeback and dispute reasonPull the last 30–90 days of disputes from your processor's dashboard and sort them by reason code. Customers are telling you what went wrong with their language: unrecognized charge, item not received, item significantly not as described, unauthorized transaction. This is not guesswork—it is the pattern. Do not assume the reasons are distributed evenly. One root cause often drives most of them. A billing descriptor that does not match your store name, for example, will spike unrecognized-charge disputes across all customers. Delivery confirmation gaps will create a cluster of not-received disputes. Once you have mapped the pattern, you know what to fix.
- Get a verified copy of your store while you still have access — todayA high-chargeback review does not always end in suspension, but the risk is real. If your account closes, you lose admin access and with it every way to extract your catalog, orders, customer history and theme data. You cannot get your gift card codes back through any API—if the store closes, the codes are locked away and the only option is re-issuing. Shopify's own CSV export cannot carry metafields, metaobjects, orders, videos, themes, menus, discounts or redirects. Migration to a new store and processor requires all of that. Create a full backup now: a migration service can move your complete store—catalog, images, SEO, theme, customer data, order history, and configuration—to a new build running a gateway that will underwrite you, then verify the counts match before going live. That backup is worthless if you wait.
- Fix your billing descriptor immediatelyThe billing descriptor is the text that appears on a customer's bank statement when they charge from you. It must be your actual business name or a widely known trading name, short enough to fit on a statement line (typically 20–30 characters). If it says something cryptic, generic or unrelated to what your customer ordered, they will assume fraud and file a chargeback before contacting you. Check your processor's dashboard for what descriptor is actually running. If it is unclear, vague or does not match your business, change it today. This alone often drops dispute rates measurably because you have made every transaction recognizable.
- Add tracking and delivery confirmation to every orderA significant portion of chargebacks claim the item never arrived. Whether or not that is true, trackable shipment with signature or proof of delivery removes the customer's incentive to dispute. If you ship physical goods, every parcel needs tracking in your fulfillment. If you use a carrier or fulfillment partner, verify their system sends tracking automatically. For digital goods or services, document delivery in your system immediately at point of sale—a link, a download, a confirmation email with a timestamp. The processor needs to see that you can prove delivery, and the customer needs to see proof that discourages them from filing a dispute after they receive the goods.
- Set up responsive customer support before they disputeA customer who gets a quick refund never files a chargeback. A customer ignored for a week will dispute instead. Set up a support channel—email, chat, help desk—and monitor it actively. When a customer contacts you with a problem, resolve it within 24 hours if you can, and always respond within that window. Train support to offer refunds generously on genuine problems before the customer has to go to their bank. This is cheaper than dispute fees and processor penalties. Once a dispute is filed with a card network, you cannot reverse it through support—you can only fight it with evidence. Prevention is the only move that actually works.
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 a chargeback threshold and why does my processor care?
The card networks—Visa and Mastercard—monitor chargeback and dispute rates at every merchant account. When a merchant's rate climbs to roughly 0.9%–1.5% of transactions, the networks impose financial penalties on the acquiring bank per dispute. Your processor acts before that threshold because the alternative is losing money on your account. The threshold is not negotiable and it applies to every merchant. Once you are flagged, the only way out is to prove your rate has fallen.
Can I appeal my account being put in a dispute-monitoring programme?
No. The card networks' thresholds are automatic and non-discretionary. There is no appeal process because the programme is not a judgment—it is a network rule that triggers when a rate hits a set point. What you can do is demonstrate that you have fixed the root cause of the disputes. The processor needs to see your rate fall below the threshold within the given timeline, typically 60–90 days. That is the only way out.
Will moving to a different processor solve this problem?
Not unless you fix what caused the disputes in the first place. A high chargeback rate reflects a real pattern in your orders—unclear billing, missing delivery confirmation, poor customer communication, or genuinely unmet expectations. Every processor screens for high-risk merchants, and if you carry the same dispute pattern to a new acquirer, you will be flagged again. The processor is not the problem. The fix is the root cause: clear billing, trackable delivery, and responsive support.
How do I actually lower my chargeback rate?
Start by mapping the reasons behind your recent disputes—unrecognized charge, item not received, not as described. One or two reasons usually dominate. Then fix that specific problem: a clearer billing descriptor, delivery confirmation on every order, or faster customer support that resolves issues before they become disputes. The fixes are operational, not financial or technical. A customer who recognizes the charge, receives the goods with proof, or gets a quick refund does not dispute. Prevention is far more effective than fighting disputes after they are filed.
Can you turn my payments back on if I get flagged?
We cannot turn payments back on—only your processor and the card networks control that. What we can do is move your complete store to a new build running a different gateway that may have different underwriting criteria and will accept your category. We migrate your catalog, images, SEO data, theme, customer records, order history, metafields, and configuration, then verify the counts match. But the actual fix—the one that keeps you from being flagged again—is addressing what caused the disputes: clear billing, trackable delivery, and genuinely responsive support before customers dispute.
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 →