Chargeback

\<font color="#b6c7cb">\</font> topic type concept purpose chargeback event overview and guidance on when to send the event audience developers implementing post transaction or dispute tracking workflows applies to integrations capturing confirmed chargeback outcomes for completed transactions does not apply to management module product workflows, as that is a separate offering the chargeback call is intended to inform us when a user denies a charge and their issuer cancels payment clients using 's management product can submit chargebacks through that product instead of coding this event directly timing the api call should come to the after a user claims a chargeback after the acquirer sends you the chargeback after you decide to stop fighting the chargeback win or lose flow chargeback flow diagram user calls their card issuer to dispute a transaction the issuer processes the chargeback the aquirer processes the chargeback client attempts to fight the chargeback or accepts it client loses or wins the chargeback client calls with end status of the chargeback see also chargeback fields https //atlas accertify com/public apis/chargeback fields