Financial transaction execution flow

The following diagram illustrates how a financial transaction occurs and payment plug-ins are used to process transactions with payment back-end systems.

1. The external application, such as WebSphere Commerce, requests an approve transaction.
2. The WebSphere Commerce Payments looks up the Payment that the approve transaction will be executed against.
3. The WebSphere Commerce Payments looks up the PaymentInstruction that will service the request.
4. The WebSphere Commerce Payments creates a FinancialTransaction that describes the approve transaction.
5. The WebSphere Commerce Payments finds the target plug-in to process the financial transaction.
6. The WebSphere Commerce Payments creates a PluginContext object with the plug-in deployment descriptor data.
7. The WebSphere Commerce Payments invokes the Plugin.approve() method.
8. The plug-in returns the updated FinancialTransaction or throws an exception.
9. The WebSphere Commerce Payments returns the results to the external application.

Related concepts

• Payment rules architecture
• Payment Plug-in Controller

Related reference

• Payment state machine
• Payment plug-in specification

(C) Copyright IBM Corporation 1996, 2006. All Rights Reserved.