The 60-Second Triage Rule
When a dispute lands, ask four questions in this order:
- Was the order obviously our mistake? Wrong item, missed refund, late pre-order communication, broken billing descriptor. If yes, refund or accept it.
- Can we prove delivery, use, or fulfillment with dated records? If no, your odds are weak.
- Does the evidence match the actual reason code? Networks do not care that you have “lots of documentation” if it does not answer the claim.
- Is the expected recovery worth the time and future risk? Fighting a $24 dispute with weak evidence is usually dumb. Fighting a $700 friendly-fraud claim on a high-AOV order is usually worth it.
Refund vs Fight: The Practical Matrix
| Situation | Best Move | Why |
|---|---|---|
| Duplicate charge, wrong amount, promised refund not issued | Refund / accept | Merchant error cases are easy losses and damage your ratio if you fight them. |
| Package shows delivered to exact address, customer goes straight to bank | Fight | Classic friendly fraud or household confusion. Tracking plus order history can win. |
| Card-not-present fraud with no 3DS, no usage proof, no delivery confidence | Accept | You are unlikely to beat a clean fraud claim without liability shift or strong fulfillment evidence. |
| Digital service or download clearly accessed from same account/device | Fight | Login logs, download records, and support conversations can matter. |
| Pre-order delayed and your communication was vague or sloppy | Refund early | “Merchandise not received” disputes are predictable when timelines drift. |
| Custom or made-to-order product with approved mockup/specs | Fight if documentation is complete | Approval trail is your whole case. Without it, you are exposed. |
| Low-value order under roughly $40 with messy facts | Usually accept | Staff time can cost more than the recovery. |
| High-AOV order with signature, ID checks, and delivery proof | Fight hard | These are expensive losses and the evidence stack is usually worth presenting. |
What Actually Moves Outcomes
Merchants lose chargebacks because they submit piles of irrelevant junk. The issuing bank is not grading your effort. It is checking whether your evidence cleanly defeats the cardholder's claim.
- Best evidence: delivery confirmation, signature, 3D Secure authentication, customer approval trail, service usage logs, refund/cancellation timestamps, clear recurring billing consent.
- Helpful but secondary: AVS/CVV match, IP address, device fingerprint, prior order history, customer emails, screenshots of the checkout flow.
- Usually weak on their own: generic terms and conditions, vague “all sales final” policies, internal notes, and giant PDFs nobody asked for.
If the claim is “merchandise not received,” the star exhibit is delivery proof. If the claim is “subscription cancelled,” the star exhibit is cancellation timing and rebill consent. Match the evidence to the claim or don't bother.
Evidence by Dispute Type
1. Fraud / Cardholder Does Not Recognize the Transaction
This is where 3D Secure matters. If you got liability shift, you are in much better shape. If you did not, your next best angle is proving this was the real customer or their household.
- 3DS authentication result / liability shift confirmation
- AVS and CVV match
- IP geolocation consistent with billing/shipping region
- Device fingerprint matching prior successful orders
- Signed delivery or photo proof for high-value shipments
- Email or SMS confirming the order, shipment, or support interaction
- Evidence of account login before purchase
Reality check: AVS and CVV alone rarely save a fraud dispute. They help, but they are not magic.
2. Merchandise Not Received
- Carrier tracking showing delivery date, city, and postal code match
- Signature on delivery for high-AOV orders
- Pickup confirmation if customer collected it in store
- Shipping timeline disclosed at purchase
- Delay notices and customer acknowledgements for backorders or pre-orders
If the shipment went to a freight forwarder, PO box, or an address the customer now claims is wrong, include the original order details exactly as submitted.
3. Not as Described / Defective / Quality Complaint
- Product page and variant description as shown at time of sale
- Photos used on the listing
- Approval records for custom work
- Support exchange offering replacement, return, troubleshooting, or partial refund
- Return policy shown before payment
These are harder than merchants think. If the product really looked different, arrived damaged, or your listing oversold it, take the L and fix your merchandising.
4. Cancelled Recurring Billing
- Signup page showing recurring terms, price, and billing frequency
- Checkbox or affirmative consent record
- Welcome email and renewal reminders
- Cancellation date/time and whether another rebill happened after that point
- Usage after the claimed cancellation date
This is a giant failure point for memberships, software, and subscription boxes. If cancellation was hard to find, support was slow, or you billed after the request, expect to lose.
5. Credit Not Processed
- Refund receipt with transaction reference
- Processor confirmation that the refund settled
- Email showing customer was told the refund timeline
- If partial refund: clear explanation of amount retained and policy basis
This one is mostly operational. If your team promised a refund and did not push it through, stop fighting and clean up the process.
Friendly Fraud: The Real Enemy
For many Canadian e-commerce merchants, friendly fraud is the bigger problem than pure stolen-card fraud. It includes:
- Buyer's remorse dressed up as “fraud”
- Family-member transactions the cardholder “didn't authorize”
- Customers who skip your return process and go straight to the bank
- Subscription buyers who forgot they signed up
- Impulse shoppers who regret a big purchase after delivery
You reduce friendly fraud with boring operational discipline:
- Use a billing descriptor customers will recognize
- Send order confirmations and shipping updates immediately
- Make refund and cancellation instructions painfully obvious
- Use signature delivery for expensive orders
- Proactively contact suspicious first-time high-AOV buyers
- Offer Interac online payment options where appropriate, especially for repeat or high-trust Canadian customers
Special Cases Canadian Merchants Mishandle
Pre-Orders and Backorders
Pre-orders are chargeback bait when the ship window moves and you go quiet. The fix is not clever legal wording. The fix is communication.
- Show expected ship timing before payment
- Send an immediate confirmation that it is a pre-order, not in-stock inventory
- Notify customers before a material delay, with a one-click cancellation path
- Do not hide behind “all pre-orders final” if the date slipped substantially
If the customer waited months and your update cadence was bad, refund them before they call the bank.
Custom Goods and Made-to-Order Work
Custom work is winnable if you document approvals. It is losable if you rely on verbal assumptions.
- Final proof or mockup approved in writing
- Dimensions, materials, spelling, and colour selections timestamped
- Production started notice
- Photos of the finished custom item before shipment
- Policy distinguishing “customized correctly” from “customer changed their mind”
Do not overreach. If the item was custom but objectively wrong, a “custom orders are non-refundable” policy will not rescue you.
High-AOV Orders
For expensive orders, the processor fee is not the main risk. The chargeback is. Your workflow should be different once the order crosses a threshold like $500, $1,000, or $2,500 depending on category.
- Use manual review for first-time customers
- Call or email to confirm suspicious orders
- Require signature delivery
- Avoid shipping high-risk orders to mail forwarding warehouses unless your fraud checks are excellent
- Store full evidence packets before the item ships
A lot of merchants will spend hours shaving 0.20% off processing fees, then ship a $2,400 order with no signature requirement. Completely backwards.
Shopify, Stripe, and WooCommerce: What Changes in Practice
Shopify Stores
Shopify merchants usually get burned in three places: vague pre-order messaging, weak descriptor recognition, and overconfidence in Shopify's fraud labels.
- Use Shopify's timeline tools properly: fulfillment updates, tracking emails, cancellation visibility.
- Do not treat “low fraud analysis” as insurance: it is a signal, not a guarantee.
- If you use Shopify Payments, understand when Shopify Protect applies and when it does not.
- For pre-orders, repeat the estimated ship window in the product page, cart, and confirmation email.
Shopify is great at operational visibility, but it does not save you from lazy merchant communication.
Stripe Merchants
Stripe gives you excellent evidence plumbing if you set it up.
- Use Radar rules, not just the defaults, if your category is fraud-heavy
- Turn on 3DS where risk justifies it
- Capture metadata that helps later: customer account ID, plan name, delivery method, fulfillment state
- Keep support conversations connected to order IDs so your dispute packet is easy to assemble
Stripe's dispute interface is good. That does not mean every case should be contested. It just means you have fewer excuses for sloppy submissions.
WooCommerce Stores
WooCommerce stores often lose on evidence quality because data lives in too many plugins.
- Make sure order notes, shipment events, email logs, and subscription actions are retained reliably
- If you sell subscriptions, audit the cancellation flow yourself on mobile
- Do not let a theme or checkout plugin strip clear billing descriptor or support info from the customer experience
- For custom products, store approved options in the order record, not only in email threads
WooCommerce gives you freedom. It also gives you more ways to build a messy paper trail.
Canadian-Specific Notes That Matter
- Interac helps. Card disputes are the problem child. If a meaningful slice of your customer base can use Interac online or e-transfer style flows supported by your stack, that can lower chargeback exposure materially. See our Interac guide.
- Domestic shipping proof still matters. Canada Post, UPS, Purolator, FedEx — whichever you use, make sure the address and delivery status are stored in a way your dispute team can retrieve quickly.
- Bilingual clarity can reduce disputes. If you sell nationally, sloppy English/French communication around returns, shipping timelines, or subscription renewals creates avoidable confusion.
- Cross-border orders are riskier. International shipments have longer timelines, more interception points, and weaker customer patience. Price for that risk.
Processor Chargeback Fees: Important, But Not the Main Story
| Processor | Typical Chargeback Fee | Usually Refunded if You Win? | Take |
|---|---|---|---|
| Helcim | $15 CAD | Usually yes | Reasonable. Better for merchants who want clearer economics. |
| Stripe | $15 CAD | Usually yes | Good tooling. Strong choice if your ops team is disciplined. |
| Square | $0 | Not applicable | Nice perk, but do not choose a processor on this alone. |
| Shopify Payments | $15 CAD | Usually yes | Convenient inside Shopify admin; prevention still matters more. |
| Moneris | Often $25 CAD | Often no | Painful if dispute volume rises. Negotiate if you have leverage. |
The fee matters, but the real cost is sale loss, product loss, staff time, reserve pressure, and a rising chargeback ratio. A “cheap” processor becomes expensive fast if its tooling and workflows let bad orders through.
How High Is Too High? Watch the Ratio Before the Processor Calls You
If your chargeback ratio starts drifting toward 0.75% or 1%, act before the processor acts for you. Networks have formal thresholds, but processors often intervene earlier with reserves, reviews, or account termination risk.
- Review disputes weekly, not quarterly
- Tag root causes: fraud, descriptor confusion, delivery issue, subscription cancellation, product dissatisfaction, merchant error
- Fix the bucket, not just the case
- If one SKU, campaign, traffic source, or province is causing most of the pain, isolate it fast
Chargebacks are usually not a “payments problem.” They are an operations, merchandising, and customer-communication problem that lands in payments.
A Simple Triage Workflow for Small Teams
- Classify the dispute within one business day.
- Pull the evidence packet from order system, shipping, support, and fraud tools.
- Score it: strong, medium, weak.
- Refund / accept weak merchant-error cases immediately.
- Fight only strong and selected medium cases above your value threshold.
- Document root cause so the next similar case is less likely.
🏆 Bottom Line
The merchants who handle chargebacks well are not the merchants who write the angriest rebuttals. They are the merchants who:
- refund obvious mistakes before they escalate,
- collect the right evidence before shipping or fulfillment,
- use 3DS and fraud controls selectively but seriously,
- communicate clearly on pre-orders, subscriptions, and custom work, and
- fight only the cases they can actually prove.
If you're still choosing infrastructure, compare processors with good fraud tooling and clean Canadian support paths in our main gateway comparison, then tighten your operational process before dispute volume tightens it for you.