Handle chargebacks and disputes
A chargeback or dispute means a payment is being challenged after the original sale was approved. This is different from a refund initiated by the seller and different from a card decline at checkout.
Use this guide when finance notices a balance change, support receives a dispute-related buyer message, or Financial Overview shows rising chargeback activity.
Chargeback vs refund vs decline
| Event | Who initiates it | When it happens |
|---|---|---|
| Card decline | Payment method or issuer | During checkout |
| Refund | Seller or authorized support workflow | After an approved sale |
| Chargeback or dispute | Buyer through payment provider | After an approved sale |
Treat each event with a different workflow. Do not use refund steps alone when a chargeback case also needs finance and evidence review.
What chargebacks can affect
| Area | Possible impact |
|---|---|
| Net revenue | Chargebacks can reduce realized revenue in Financial Overview. |
| Available or pending balance | Funds may move or be held while the case is processed. See fees and payout delay. |
| Risk reporting | Rising chargebacks may signal checkout, delivery, or subscription problems. |
| Support workload | Buyers may contact support before or after disputing with their bank. |
| Product access | Access may need review depending on product policy and subscription status. |
| Campaign decisions | A campaign can look profitable on gross sales but weak after disputes and refunds. |
Investigation workflow
- Confirm the correct business workspace.
[Screenshot: App header — correct business workspace selected.]
- Open the sale in Sales.
[Screenshot: Sales search — disputed sale located by buyer email.]
- Confirm buyer, product, offer, payment method, and purchase date.
[Screenshot: Sale detail — buyer, product, offer, and card payment visible.]
- Review customer history and any prior refund activity.
[Screenshot: Customer history — prior refunds or purchases for same buyer.]
- Check Financial Overview and Finance for revenue and balance impact.
[Screenshot: Financial Overview chargeback tab — dispute reflected in reporting.]
- Review whether delivery or access was granted correctly.
[Screenshot: Delivery evidence — access granted per checkout promise.]
- Check subscription status if the dispute involves recurring billing.
[Screenshot: Subscription detail — renewal dates for disputed recurring sale.]
- Collect evidence: checkout link, buyer email, delivery proof, support transcript, and sale IDs.
[Screenshot: Evidence folder — sale ID, checkout link, and support transcript collected.]
- Decide whether access should remain active while the case is reviewed.
[Screenshot: Internal decision note — access policy during dispute documented.]
- Document the case for finance and support follow-up.
[Screenshot: Case log — dispute documented for finance and support teams.]
Prevention habits
- Keep checkout copy aligned with the real product and delivery promise.
- Make subscription, trial, and renewal timing clear before payment.
- Resolve buyer access issues quickly before buyers dispute with their bank.
- Monitor refund and chargeback trends in Financial Overview.
- Train support to distinguish refund processing issues from bank-initiated disputes.
- Review affiliate or campaign promises that may create expectation gaps.
What to verify after a dispute appears
| Check | Why it matters |
|---|---|
| Sale and subscription records match | Recurring billing disputes often involve renewal confusion. |
| Delivery matched checkout promise | Reduces repeat disputes on digital products. |
| Refund was not already processed | Avoid duplicate financial actions. |
| Balance change is understood | Finance may need reconciliation with stakeholders. |
| Similar cases are grouped | A spike may indicate a broken checkout or funnel path. |
Best practices
- Treat chargebacks as both a finance issue and a customer-trust issue.
- Collect evidence early while logs and buyer context are fresh.
- Review access decisions against written product policy.
- Compare dispute trends by product, offer, and payment method.
- Fix the upstream promise or delivery issue, not only the individual case.
Common mistakes
- Confusing chargebacks with card declines.
- Removing access automatically without reviewing subscription context.
- Ignoring a dispute spike in Financial Overview.
- Refunding and disputing without documenting which action was taken.
- Blaming campaign traffic before checking checkout and delivery alignment.
FAQ
Is a chargeback the same as a refund?
No. A refund is initiated by the seller or support workflow. A chargeback is initiated by the buyer through the payment method provider and should be reviewed as a separate case.
Should buyer access be removed after a chargeback?
Follow your product policy and review the sale, subscription, and support context before changing access.
Where do chargebacks appear in reporting?
Review the chargeback tab in Financial Overview and compare with Sales for the underlying transactions.
Can unclear subscription terms cause disputes?
Yes. Review trial periods, billing periods, and checkout copy before relaunching recurring offers.