Dispute flow is the fixed sequence a challenged card payment follows, from the cardholder's complaint at their bank to a final ruling on who absorbs the loss, with a scheme deadline on every step. The issuer assigns a reason code that decides which evidence counts, then pushes the transaction back through the network so the acquirer debits the merchant, adding a fee and a mark on the chargeback ratio. The merchant can accept or represent with evidence such as delivery confirmation, AVS and 3-D Secure results. Rejected representments escalate to pre-arbitration and scheme arbitration, where fees can exceed a 40 EUR order. Response windows run from network notification, so unread notices lose cases.
It starts with a reason code
The cardholder tells the issuer that something is wrong: not authorized, goods never arrived, item not as described, subscription cancelled and billed anyway. The issuer picks a reason code, and that code fixes everything downstream, including which evidence counts, how many days each side gets, and whether the merchant can defend at all. Reading the code before writing a response is the difference between a considered defense and a wasted one.
The debit lands before anyone judges the merits
The issuer pushes the transaction back through the card network to the acquirer, which debits the merchant at once. A dispute fee is added, and the case counts toward the merchant's chargeback ratio whether or not the merchant later wins. On the merchant's statement the movement appears as an adjustment, and a second entry arrives if the money comes back.
Representment: specific evidence or none at all
The merchant either accepts the loss or represents the transaction with evidence that the charge was valid. What works is transaction-specific: delivery confirmation to the billing address, AVS and 3-D Secure results, IP and device data, the customer's own messages, the exact terms they accepted. Screenshots of a general policy page lose. Businesses selling something intangible need usage and login records, because there is no parcel to point at.
Pre-arbitration, arbitration and the point of giving up
An issuer that rejects the representment can escalate to pre-arbitration, and unresolved cases go to the scheme itself for arbitration. The loser pays the disputed amount plus an arbitration fee that frequently exceeds it. On a 40 EUR order the arithmetic says stop; on a 4,000 EUR order it usually does not. Setting that threshold once, in advance, keeps the decision out of case-by-case arguments.
The deadlines that quietly decide most cases
Response windows run from the network's notification, not from when the merchant noticed it. Cases are lost by inbox far more often than by argument, typically a notification sitting unread in a mailbox belonging to someone who left. Give the flow an owner, a queue and a calendar.
Cheaper than winning
The controls that cut dispute volume sit before the flow starts: a payment descriptor customers recognize, support that answers before the bank does, and a fast refund when the case is genuinely lost. Money returned voluntarily costs the sale. A lost dispute costs the sale, the fee and a point on the ratio.