The following diagram depicts the overall relationship of event-driven payments to the Order Management subsystem and payments-related functions in WebSphere Commerce.
The Order Management subsystem and Customer Service Representatives (CSRs) interact with the event-driven payments subcomponent. The Order Management subsystem delegates any payment processing (and payment decisions) to the event-driven payments subcomponent. CSRs use event-driven payments for queries and edits.
The event-driven payments subcomponent uses configurable rules to determine what payment actions to take for the order. Payment rules can vary by payment configuration ID, payment method, and by the business event or phase of the order.
The event-driven payments subcomponent interacts with payment back-end systems through the Payments Plug-in Controller. The Payments Plug-in Controller provides support of financial operations while hiding the complexity of multiple payment back-end systems and the selection of those systems. The Payments Plug-in Controller, event-driven payments, and plug-ins make up the payment subsystem.
The Payment Plug-in Controller is a software layer that handles interaction with payment plug-ins and the traditional multipayment framework of WebSphere Commerce Payments (and its payment cassettes) for backward compatibility. The Payment Plug-in Controller selects which payment plug-in to use to process the financial request and handles payment management services for plug-ins. Plug-ins handle payment protocol details. The WebSphere Commerce Payments plug-in interacts with the WebSphere Commerce Payments multipayment framework. The system can be extended through the addition of third-party and in-house payment plug-ins to interact with other payment applications.