A dispute is how a buyer stops a payout and gets a human involved. It is the reason the seller is not paid at checkout.
Your disputes: /account/disputes.
The window
14 days. Counted from the payment for an order, and from escrow funding or closing for a deal.
For a subscription listing, each paid month has its own window from its own payment date — a problem in month seven is disputable in month seven, not only in month one.
Reasons
NOT_AS_DESCRIBED, NOT_DELIVERED, QUALITY_ISSUE,
UNAUTHORIZED_CHARGE, DUPLICATE_CHARGE, ASSET_TRANSFER_FAILED,
OTHER.
ASSET_TRANSFER_FAILED is the store-acquisition case: the deal closed
and the assets never arrived.
What happens
- Open. You raise it. The seller is notified and can respond.
- Awaiting admin. Either the seller responded, or 7 days passed with no response and it escalated automatically. A seller who ignores a dispute does not run out the clock.
- Resolved. A mediator decides.
You can withdraw at any point before resolution.
The four outcomes
| Outcome | Means | |---|---| | Refund | Full refund issued | | Partial refund | Part of the amount returned | | No action | Resolved in the seller's favour | | Withdrawn | You withdrew it |
Refunds on a deal work differently
A full or partial refund reverses a Stripe payment intent, and an order carries one. A deal does not: the money moved through escrow, not through a payment intent BoostEcom can reverse.
So a deal dispute resolves as no-action with the settlement handled outside the automatic path. The alternative — announcing a refund in a resolution email that no code path would pay and no ledger would record — is the failure this rule exists to prevent.
For sellers
The vendor side is at /<org>/~/disputes, with the response flow and a
deadline highlight. An unanswered dispute escalates whether or not you
saw it.