Task commands used in Payment Rules
The task commands used in Payment Rules include task commands relating to the order life cycle and also to task commands relating to refund situations. These task commands are called during the occurrences of significance to the system that can involve the storage and validation of payment information; the capture, release, and shipment of orders; and the return of orders or correction of payment information. Basically, when an occurrence occurs that involves having to know what a customer needs to pay for a purchase (or how the customer should be credited), the Payment Rules subcomponent is responsible for reading the payment rules that apply to the payment method involved and triggering the appropriate action.
Summarized, the Payment Rules task commands that are associated with order and returns processing are shown in the following list. These commands apply to all WebSphere Commerce business models.
- Pre-order authorization (store payment information and validate it) - StoreAndValidatePaymentCmd
- Order capture (when the Buy button is clicked) - PrimePaymentCmd
- Release to fulfillment (goods are ready to ship) - ReservePaymentCmd
- Fulfillment (goods have shipped and shipment is confirmed) - FinalizePaymentCmd
- Return merchandise authorization (RMA) capture - PrimeRefundCmd
- Credit release - FinalizeRefundCmd
- Edits (changes to payment amounts or payment methods, or late edits) - EditCmd
- Last chance edit - EditReleaseCmd
- Order cancellation - CancelOrderCmd
- Triggering actions - TriggerPaymentActionsCmd
The payment actions that are executed during the processing of each task command vary according to the payment methods involved and their matching payment rules. For example, the payment actions defined for a credit card during order capture will probably be different from the payment actions defined for an electronic check during the same order capture event. Also, all stores do not process payments the same way. Some stores might not accept a particular brand of credit card, for example. The advantage of using Payment Rules is that you can configure the payment behaviors that suit the commerce transaction needs of your store.
Customers can submit orders that have a zero total payment amount. The payment rules task command, PrimePaymentCmd, ReservePaymentCmd, and FinalizePaymentCmd will process the order without initiating a payment action or generating an error due to lack of payment information. The order must be a zero total amount, including shipping or other charges.
EditCmd happens in two ways: by adding, removing, or updating payment information, and through the TriggerPaymentActionsCmd.
For more information about specific task commands, refer to the following topics:
Order life-cycle related task command
- StoreAndValidatePaymentCmd command
- PrimPaymentCmd command
- EditCmd command
- ReservePaymentCmd command
- FinalizePaymentCmd task command
- CancelOrderCmd command
- TriggerPaymentActionsCmd command
Refund related task command
In addition to handling these events, the Payment rules subcomponent provides query facilities that enable Customer Service Representatives to respond to inquiries regarding the payment status of an order.
(C) Copyright IBM Corporation 1996, 2006. All Rights Reserved.