The following list identifies where you can find more information about event-driven payments, the Payment Plug-in Controller, and payment plug-ins:
Administering
- Event-driven payments
- Event-driven payments architecture
- Relationship of payment instructions to WebSphere Commerce Payments orders
- Advantages of using event-driven payments and payment plug-ins
- DoPayment command versus plug-ins
- Relationship of WebSphere Commerce Payments commands to event-driven payments
- Payment rule relationship to trading agreements (Business Edition)
- Payment business policies for event-driven payments
- Relationship of standard orders to event-driven payments
- Using event-driven payments with WebSphere Commerce Payments
- Using event-driven payments with an external payment plug-in
- Event-driven payments in a clustered environment
- Event-driven payments rules
- Events associated with event-driven payment rules
- Event-driven payments examples
- Example: Credit card payment with single release
- Example: Credit card payment with multiple releases
- Example: Electronic check payment with multiple releases
- Example: Electronic check payment with multiple releases and price increase
- Example: Credit card payment with single release but payment fails
- Payment rules provided in WebSphere Commerce
- Payment rules used in starter stores
- Ticklers created by event-driven payments
- Address Verification Service (AVS) handling under event-driven payments
- Information to help troubleshoot event-driven payments
- Using payment plug-ins
- SimpleOffline payment plug-in
- Line of credit (LOC) payment plug-in
- WCPayments payment plug-in
Configuring
- Configuring payment processing (event-driven payments)
- Configuring XML files for event-driven payments processing
- Configuring payment methods
- Configuring refund methods
- Payment configuration IDs
- Payment system names
- Defining a payment configuration for event-driven payments
- Viewing available payment method and refund method configurations
- Associating a payment method or refund method configuration with a store
- Removing a payment method or refund method configuration from a store
- Creating a new payment method or refund method configuration
- Changing an existing payment method or refund method configuration
- Deleting a payment method or refund method configuration
- Reloading payment rules
- Configuring payment plug-ins for event-driven payments
- Using payment or refund methods not provided in WebSphere Commerce
- Using other payment protocol data to find orders
- Tuning event-driven payments performance
- Retention of payment information in the WebSphere Commerce database
- XML files supporting event-driven payments
- Configuring a payment plug-in
- Mapping a payment system to a payment plug-in
- Payment system plug-in mapping XML file
- Configuring the SimpleOffline payment plug-in
- Configuring the LOC payment plug-in
- Configuring the WCPayments payment plug-in
Developing
- Event-driven payments
- Using payment plug-ins
- Structure of a payment plug-in
- Supporting multiple payment protocols with a payment plug-in
- Payment plug-in specification
- Plug-in deployment descriptor XSD
- Plug-in deployment descriptor example
- Offline and online payment processing
- Pending and timeouts
- Standardized plug-in keywords for protocol name-value pairs
- Predefined keywords in extended data for payment instructions
- Payment system plug-in mapping XML file
- Payment plug-in containers class diagram
- Payment state machine
- Credit state machine
- Financial transaction execution flow
- Creating a payment plug-in
- Packaging a payment plug-in
- Installing a payment plug-in
- Using a payment plug-in provided in WebSphere Commerce
- Installing a payment plug-in written by a third party
- Installing a payment plug-in into a WebSphere Commerce Development Environment
- Uninstalling a payment plug-in
- Configuring a payment plug-in
- Mapping a payment system to a payment plug-in
- EDPDepositableAmountProcessCmd
- SimpleOffline payment plug-in
- How the SimpleOffline payment plug-in works
- SimpleOffline plug-in security
- SimpleOffline plug-in deployment descriptor
- Data required by the SimpleOffline plug-in
- SimpleOffline payment and credit state transition handling
- Configuring the SimpleOffline plug-in
- SimpleOffline plug-in financial transactions
- SimpleOffline plug-in messages
- Line of credit (LOC) payment plug-in
- WCPayments payment plug-in
- How the WCPayments payment plug-in works
- WCPayments plug-in security
- Risk of using Payment GUIs with the WCPayments plug-in
- WCPayments plug-in handling of offline transactions
- Mapping of WCPayments objects to WebSphere Commerce Payments objects
- Address Verification System (AVS) code processing with the WCPayments plug-in
- WCPayments plug-in and Cashier profiles
- Cashier profile for the Cassette for BankServACH (using the WCPayments plug-in)
- Cashier profile for CustomOfflineCassette - Bill Me (using the WCPayments plug-in)
- Cashier profile for CustomOffline cassette - COD (using the WCPayments plug-in)
- Cashier profile for OfflineCard cassette (using the WCPayments plug-in)
- Cashier profile for the Cassette for Paymentech (using the WCPayments plug-in)
- Cashier profile for the Cassette for VisaNet (using the WCPayments plug-in)
- WCPayments plug-in deployment descriptor
- Data required by the WCPayments plug-in
- WCPayments plug-in payment and credit state transition handling
- Configuring the WCPayments payment plug-in
- WCPayments plug-in financial transactions
- WCPayments plug-in exceptions
- WCPayments plug-in messages
Operating
Securing
- Payment plug-in security
- SimpleOffline plug-in security
- LOC plug-in security
- WCPayments plug-in security
Tuning
- Tuning event-driven payments performance
- Retention of payment information in the WebSphere Commerce database