When a dispute enters the Pulse recovery strategy, this is the first flow that is executed. In this step, a dispute will be submitted to the Pulse Network either via the Pulse API service, or by a user, via an external system. Before the dispute is submitted, the system will check to see if the chargeback dependencies are satisfied. These dependencies are referenced in each of the recovery options. If the dependencies are not satisfied, or the Pulse API is not enabled, a Process Chargeback assignment is created and prompts a user to review the details and submit the chargeback. If the Pulse API is enabled, the system will attempt to create the dispute with the Pulse Network. If that attempt fails multiple times, a Pulse Dispute Service Failed assignment is generated and a user is prompted to review the details, make any necessary changes and process the chargeback again. Once processed, the Dispute Response flow is executed. If Pulse rejects the dispute, the Dispute Rejected flow is executed.

Referenced From

Technical Details

Rule(s)

PulseExecuteDispute

Browser not supported