High chargeback rate, and you sell cannabis seeds. 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 cannabis seeds
Stripe, which underwrites Shopify Payments, lists cannabis and its derivatives as prohibited. Cannabis seeds fall into that category by association: even though seeds themselves contain no active cannabinoids, they are inherently intended for cultivation into a controlled substance. The secondary trigger is your jurisdiction. Some US states allow seed sales as collectibles or agricultural stock; others ban them outright. A processor reviewing your store sees the category risk first and your local legality second—or doesn't look at it at all.
Rule out the easy fix first — then deal with the real one
There is no documented Shopify route for cannabis seeds. What merchants typically try first is either hiding the category under 'botanical supplies' or applying to Shopify Payments and hoping the reviewer misses what you sell. Both fail. The honest path is that you need an acquirer who has explicitly chosen to underwrite seed banks—and that means going outside the Shopify Payments rails entirely to a third-party high-risk provider who can front you through Shopify using a standalone gateway integration. Those providers exist, but they are not hidden in a settings menu; you will need to contact them directly with your store details and jurisdiction, and they will run their own underwriting.
It only helps if all of these are true:
- You must operate in a jurisdiction where seed sales are explicitly legal or tolerated
- Your store must not imply or state that seeds are for human consumption
- You must be able to document the legality of your specific business in your specific location
- You cannot use Shopify Payments—you must connect a third-party high-risk gateway
- You must accept a substantially higher rate and a rolling reserve of 10–25% held 180+ days
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
⚖️ Legal status is genuinely contested or actively changing
When your legal status is contested, processors already price legislative uncertainty into your rates and reserve requirements. A high chargeback rate on top of that legislative risk is the trigger for account termination, not just rate increases. The card networks' dispute-monitoring programmes enrol you at roughly 0.9%–1.5% of transactions, adding per-dispute penalties that compound your exposure. You cannot escape this by hiding the nature of your business or using obscure billing descriptors; that accelerates account closure. Billing descriptor accuracy and delivery confirmation are your foundation. After that, responsive customer support before disputes network is essential—handle refund requests and shipping concerns immediately. Your next processor will see the chargeback history regardless; the fix is real, not cosmetic.
📦 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 cannabis seeds, these are the facts that move the decision:
Rewrite every product description to remove cultivation language and intent signals
This is the single highest-yield fix. Any text that frames seeds as inputs for growing cannabis—'ready to cultivate', 'yields', 'ideal for outdoor growing', 'high THC genetics'—signals to an underwriter that you are knowingly facilitating drug production. Reframe as collectibles, souvenirs, or breeding stock. Audit product names, variant labels, descriptions, blog posts, email templates and any customer-facing graphics. A reviewer will read everything.
Obtain written legal confirmation that your jurisdiction permits seed sales in your category
Most acquirers will not touch you without this. You need either state or local legislation that explicitly permits seed sales, a regulatory ruling from your state's agriculture or cannabis board, or a written opinion from a lawyer licensed in your jurisdiction confirming that your specific business model is legal. This is not optional—it is the document that separates a merchant with a legal business from one that is guessing. Email a copy to the acquirer before they even request it.
Verify your business is registered correctly and matches all legal paperwork
Use your legal name consistently across your business registration, tax ID, bank account, domain registrant information and store admin account. Mismatches flag you as a shell entity or a deliberate obfuscation, which kills underwriting. Check that your stated location matches where you are actually operating and selling. If you have moved or rebranded recently, document the chain of continuity so you are not mistaken for a fresh entity trying to evade history.
Document your customer verification and prevent high-risk patterns
Do not sell to addresses in states or countries where cannabis cultivation is prohibited. Implement age verification if your jurisdiction requires it. Monitor for bulk orders, reseller patterns or shipments to states with stricter laws—these trigger compliance reviews mid-relationship. Keep records of customer communications so you can show you made a good-faith effort to prevent misuse. An acquirer reviewing you six months in will look at your transaction patterns as proof that you are managing the category responsibly.
What underwriting will ask you for
- Articles of incorporation or business registration showing your legal entity name and formation date
- Proof of your jurisdiction's legality for seed sales—legislation, regulatory guidance, or attorney opinion letter specific to your state or country
- Your store's product descriptions and any marketing materials that detail how you describe the intended use of seeds
- Bank statements from the past 6 months showing transaction history and average monthly volume
- Copies of your terms of service and any customer agreements that disclaim responsibility for end-use
- Your processing history with any previous acquirer, including the reason for any termination
- Identity documents for all beneficial owners and signatories
Getting underwritten for cannabis seeds
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite cannabis seeds. 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 cannabis seeds
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 seed bank's data breaks in a very specific way during a manual migration: the genetics matrix. Cannabis seeds are sold in deep variant structures—dozens of strains crossed with auto-flower vs. photoperiod timing, male vs. female, seed count per pack—and these relationships live in metafields, not in standard Shopify variant naming. When you move by hand or via CSV, metafield connections snap silently. A customer looking for 'feminized auto-flower Northern Lights' sees the products exist but the filtering logic is broken. On a catalog-heavy site this creates cascading returns and support work. Automated migration re-links them correctly.
| What you own | How much of it | What breaks doing it by hand | What we do instead |
|---|---|---|---|
| Product images | 5,200images≈ 22 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 | 650descriptions≈ 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 | 11,700variants≈ 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 | 9,100metafields≈ 61 hrsonly the reference, JSON and metaobject fields, ~1 min each | By handthe product CSV carries simple text and number metafields — but not metaobjects, and not reference or JSON types, which is exactly where app data and theme content live. Reference fields are the real trap: copy the value and it still points at objects in the OLD store, so the page renders and the custom block is silently empty | Automatedwritten in dependency order after their targets exist, with embedded references re-pointed at the new store's objects — and any value whose reference cannot be resolved is dropped rather than written broken |
| SEO data & redirects | 1,072records≈ 7 hrsredirects one at a time, plus a handle audit | By handany handle that changes becomes a dead URL with no redirect, and existing 301s are not in the product CSV at all. Years of accumulated ranking and backlinks end up pointing at pages that no longer resolve — the most expensive thing on this page to get wrong, and the slowest to notice | AutomatedSEO titles, meta descriptions and handles carried across, and every existing 301 recreated, so nothing that used to rank starts 404ing |
| Your custom theme | 1theme≈ 6 hrs2–10 hrs depending on how customised it is | By handa theme is not just its files. The settings, section content and block ordering are stored against the store, so a file copy gives you the layout and none of the content. Hardcoded asset URLs and tracking snippets also still point at the old store | Automatedyour live theme pulled and pushed as-is, then scanned for tracking snippets and hardcoded URLs that need re-pointing |
| Product videos | 12videos≈ 48 minre-upload and re-attach, ~4 min each | By handthe product CSV does not carry video or 3D media, so every one is a manual re-upload. They also cannot be pulled straight from a remote URL — the bytes have to be downloaded and staged first, and a wrong content type lands the file as a generic attachment that media-restricted fields then reject | Automatedvideo bytes downloaded, staged through a proper upload target, re-attached to the right product, and verified as processed rather than silently failed |
| Customers | 8,400customers≈ 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 | 19,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 | 52discounts≈ 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 | 42articles & pages≈ 3 hrsrecreated one at a time, ~4 min each | By handno CSV route for either. Articles also have no SEO fields of their own — their title and description tags live in metafields — so a hand-rebuilt blog loses its SEO even when every word of the text is right | Automatedarticles and pages recreated with authors, tags and publish dates, their SEO written to the metafields Shopify actually stores it in, and inline image URLs rewritten |
| Apps & app data | 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 reset your underwriting history. If your seed business has previously been declined or terminated by a processor, the beneficial owners behind it will be flagged under MATCH for five years, regardless of whether you incorporate under a new name. Underwriters will find the connection. Your best move is not a new company—it is finding an acquirer who accepts seed merchants and being transparent about your history from the start.
Frequently asked
Can I use Shopify Payments for a seed bank?
No. Stripe, which powers Shopify Payments, prohibits cannabis and cannabis-related products, and seeds fall under that category. You must use a third-party gateway provider who specializes in high-risk businesses and explicitly accepts seed merchants. This requires a separate merchant account with that acquirer and integration into Shopify via a standalone gateway, not Shopify Payments. The setup is straightforward but it is not a checkbox—you have to apply and be approved.
Which gateway should I connect?
Multiple acquirers publicly advertise cannabis seed merchants, including Bankful, DigiPay, PaymentCloud, Corepay, Easy Pay Direct and Durango, among others. Each has different underwriting, rates and reserve terms. Rather than cold-email a dozen providers, we maintain a live referral form on this page—fill it with your store details and jurisdiction, and qualified providers will contact you directly. This cuts months of back-and-forth rejection.
What happens to my existing orders and customer list during a migration?
Order history and customer data can be fully migrated to your new store. Your payment processing history does not move—your new acquirer will have no record of your old transactions. This is actually useful: you are starting your underwriting relationship with a processor who has chosen to accept seed merchants, rather than carrying a decline notice forward. Your customer list remains yours to use for reactivation email and retargeting.
Will my product variants and genetics data survive the move?
Standard product data—names, descriptions, prices, images—transfers cleanly. But if your strain genetics, cannabinoid profiles, growing characteristics or breeding notes live in metafields, a hand migration or CSV export loses them. Automated migration captures metafields correctly. That is why a seed bank catalog move is higher-risk than a standard ecommerce move: a broken genetics matrix means lost filtering, broken search and a degraded browsing experience for customers. We run the migration twice and compare counts to catch it.
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 →