WebSphere Commerce Payments 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 WebSphere Commerce Payments calls the WebSphere Commerce Payments plug-in to approve API with offline transaction configuration (that is, the PaymentSystemPluginMapping.xml file for the WebSphere Commerce Payments plug-in has the property SupportsOnlineTransaction with a value of "no"), WebSphere Commerce Payments sets the approve transaction to PENDING state rather than SUCCEED state.
After the payment is manually approved in the WebSphere Commerce Payments GUI, WebSphere Commerce Payments can query the payment to get the exact state of the payment.
The WebSphere Commerce Payments plug-in will not issue the approve command for WebSphere Commerce Payments in the WebSphere Commerce Payments plug-in approve API. It only creates an order in the WebSphere Commerce Payments multipayment framework and sets the 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 WebSphere Commerce Payments plug-in can determine the exact state of the offline payment by querying the WebSphere Commerce Payments 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.
(C) Copyright IBM Corporation 1996, 2006. All Rights Reserved.