Advanced orders WCPayments plug-in handling of offline transactions

Payment transactions that are handled offline (through use of the OfflineCard or CustomOffline cassette, for instance) are set to "ING" state. After the Payment Plug-in Controller calls the WCPayments plug-in approve API with offline transaction configuration (that is, the PaymentSystemPluginMapping.xml file for the WCPayments plug-in has the property SupportsOnlineTransaction with a value of "no"), the Payment Plug-in Controller sets the approve transaction to PENDING state rather than SUCCEED state.

After the payment is manually approved in the WebSphere Commerce Payments GUI, the Payment Plug-in Controller can query the payment to get the exact state of the payment.

The WCPayments plug-in will not issue the approve command for WebSphere Commerce Payments in the WCPayments plug-in approve API. It only creates an order in the WebSphere Commerce Payments multipayment framework and sets the Payment Plug-in Controller approve transaction state to PENDING.

A Customer Service Representative is expected to use the administration user interface provided in WebSphere Commerce Payments to manually approve the order in WebSphere Commerce Payments. The WCPayments plug-in can determine the exact state of the offline payment by querying the Payment Plug-in Controller for the state of the payment.

For more information about approving pending transactions with payment cassettes, refer to the online help available in the WebSphere Commerce Payments user interface or see the WebSphere Commerce Payment tutorial topic on "Approving tasks" below.

Feedback