Advanced orders triggerActions business event

The triggerActions event usually occurs after a series of edits have been made. Because the system cannot predict how many edits will occur before it should balance amounts, the triggerActions event causes any required payment actions to be executed and puts payments in a consistent state. The triggerActions event is also invoked when temporary connectivity problems have disrupted transactions.

The possible payment actions associated with this event are: Validation, Approve, ReverseApproval, Deposit. Payment actions for this event are not configurable. This event is used internally by the event-driven payments component and is mentioned here only to provide a complete list of events. Developers do not need to consider this event or any other event-driven payments business event when writing payment plug-ins.

Feedback