Chargebacks in Cannabis and CBD: Where Disputes Actually Come From

The short answer

In cannabis and CBD, most disputes are not fraud. They come from unrecognised descriptors, subscription renewals customers forgot, delivery and fulfilment gaps, and product expectations set by marketing copy. Those causes are all addressable operationally, which is why dispute performance is treated as a proxy for how well a merchant is run.

That matters more here than in low-risk retail. A dispute rate that would be tolerated elsewhere can trigger a review, a reserve or an exit in a high-risk portfolio.

The common causes, in order

Work through these before buying dispute-management tooling; the tooling rarely fixes a cause that lives in checkout or fulfilment.

• Descriptor confusion: the name on the statement does not match the brand the customer bought from.
• Subscription renewals with no pre-billing notice.
• Delivery issues: late, partial or undelivered orders with no proof of delivery on file.
• Product expectation gaps driven by imprecise claims or unclear potency and quantity information.
• True fraud, which is usually the smallest bucket for established brands.

Evidence that actually helps a representment

Compelling evidence is specific and contemporaneous. Assemble the order record with timestamps, the checkout terms the customer accepted, age or eligibility verification where applicable, delivery confirmation with signature or geolocation, and the support thread showing any refund offered before the dispute.

Build this into fulfilment so it is retrievable in minutes. Evidence assembled weeks later is usually incomplete and rarely persuasive.

Prevention that moves the number

Change the descriptor to the trading name customers recognise and add a support phone number where the format allows. Send a renewal notice before every recurring charge. Confirm delivery windows and notify on delay. Make refunds easy enough that contacting you is faster than contacting the bank.

• Review your dispute reasons monthly and fix the top cause, not the top ten.
• Track disputes as a share of transactions and of volume; thresholds are read both ways.
• Tell your provider what you changed. A documented remediation plan is worth a great deal during a review.
• Pair the descriptor and refund changes with a short customer-facing note at checkout summarising the return and refund policy in plain language. Ambiguity at the point of sale about how a return works is a disproportionately common driver of disputes, because a customer who feels unsure about the refund process is more likely to contact their card issuer first and your business second.

Recordkeeping that shortens the response window

Most representment deadlines run to a matter of days, and the merchants who win consistently are the ones who never have to hunt for evidence. Build a standing folder structure, one per order, that automatically captures the confirmation email, the delivery record and any support messages the moment they are generated.

This is a fulfilment discipline as much as a payments one. If your delivery software and your support ticketing system are not already exporting into a single retrievable record per order, that gap is the first thing to close, well before you spend time on dispute-management software.

Assign clear ownership for evidence assembly rather than leaving it to whoever happens to be free when a dispute notice arrives. A named person who checks the dispute queue daily and pulls the relevant order file within hours, not days, is usually the single highest-leverage change a merchant can make to its win rate.

Reading your dispute report like a provider does

Providers and networks generally look at a dispute ratio, not a raw count, and they compare it against thresholds set for your risk category. A merchant doing modest volume can trip that ratio with a handful of disputes in a slow month, while a much larger merchant absorbs the same count without comment.

Pull your own ratio monthly using the same denominator your provider uses, typically prior-month transaction count, so you see a threshold breach coming before it appears in a review letter rather than after.

• Calculate dispute count divided by prior-month transaction count, matching your provider's method.
• Flag any month where the ratio approaches a commonly cited industry threshold.
• Segment the ratio by product line or fulfilment method to find where the real problem sits.
• Present this ratio proactively to your provider during any account review rather than waiting to be asked. A merchant who can show a declining or stable ratio with supporting detail is in a materially stronger position than one who only produces the number after a request, because it signals the dispute rate is being actively managed rather than merely tolerated.