Disputes and Chargebacks
When a consumer contests a transaction, Nopan tracks the case through two phases:
- Pre-dispute: the consumer raises a complaint, and the merchant can resolve it directly.
- Chargeback: if the pre-dispute is escalated and the consumer PSP accepts the request, the case moves into a formal chargeback. From there it can go through representment, pre-arbitration and arbitration.
Nopan sends a webhook when a case opens, when it changes and when it closes, so you can track each case without polling.
Reading the diagrams
Each phase below has its own state diagram. The colours mean:
Pre-dispute
A pre-dispute opens when the consumer raises a complaint about a transaction. While it is open, the consumer and the merchant can exchange messages, and the case ends in one of these ways:
- Refunded: the merchant refunds the consumer.
- Closed: the consumer closes the case.
- Chargeback Request Accepted / Declined: the consumer escalates the case (Chargeback Requested) and the consumer PSP decides whether it becomes a chargeback. If it is accepted, a chargeback case opens.
Chargeback
A chargeback opens after the consumer PSP accepts a chargeback request. Chargeback webhooks include the original preDisputeId inside the chargeback object, which links the chargeback to the pre-dispute it came from.
The acceptor PSP can either accept the chargeback (Accepted), which closes the case, or contest it (Represented). After a representment, the case can escalate in stages:
- Representment: the consumer PSP accepts the representment, or escalates to pre-arbitration.
- Pre-arbitration: the acceptor PSP accepts or declines it, or the consumer PSP withdraws it. If it is declined, the consumer PSP accepts the decline or escalates to arbitration.
- Arbitration: the case ends when either party withdraws or accepts, or when the arbitrator decides in favour of one of the PSPs.
Not every payment method supports disputes. Check the feature matrix on each payment method page.