This event happens when the customer wants to cancel an order.
The only possible payment action is ReverseApproval. Payment actions for this event are not configurable.
Example: A customer chooses to cancel an order. The system verifies that the order has not been released to fulfillment. The system does a reverse approval of the payment, order items are deallocated, and the order is marked as canceled.
If a deposit has already happened, the order cancellation will fail unless the cancellation is forced. Forcing the cancellation will cancel the order even if deposits have already happened. When a cancellation is forced and deposits have already taken place, a tickler is created to notify a Customer Support Representative that an amount needs to be refunded to the customer.
If a payment action with the payment back-end system fails, a tickler is created to notify a Customer Service Representative.