Registering with the payment back-end system
Since there is no direct communication with a payment back-end system with the SimpleOffline plug-in, this plug-in does not require registration with a payment service provider for operation.
Configuring the plug-in
The SimpleOffline plug-in requires that a store be enabled for advanced orders processing.
To configure this plug-in for use in WebSphere Commerce
- Refer to the instructions in Configuring a payment plug-in.
The Payment system plug-in mapping XML file would show the following, for example:
<PaymentSystemName name="OfflineCard" > <Mapping paymentConfigurationId="default" PluginName="SimpleOffline" > </Mapping> </PaymentSystemName>
- Ensure that the payment system name of OfflineCard is reflected in the PaymentMethodConfiguration XML file and RefundMethodConfiguration XML file used by event-driven payments.
Pending status: Transactions are kept in pending status as defined by the SimpleOfflinePlugin.xml file. After the total amount of the payment instruction is approved, sensitive data will be removed from the extended data automatically. The sensitive data can be configured in the Payment Plug-in Controller configuration file PaymentSystemPluginMapping.xml.
A CSR can change the payment state from APPROVING (pending) to APPROVED in the WebSphere Commerce Accelerator by navigating through the Payments menu to editing the pending payment transaction. To manually remove sensitive data associated with pending transactions, users with the proper access can edit the extended data associated with the payment (or credit) by navigating through the Payments menu in the WebSphere Commerce Accelerator.
Special configuration information
In addition, you must do the following configuration steps to configure the plug-in properly:
- Set the supported payment methods for the SimpleOffline plug-in. For a list of the payment methods already supported by this plug-in, and the required data for each, see How the SimpleOffline plug-in works. By default, WebSphere Commerce collects this required data for the plug-in.
- Specify whether the payment method should keep transactions in a pending state for manual intervention. (Refer to the keepPendingStatus attribute for the payment method in the SimpleOfflinePlugin.xml file.)
- Specify the required protocol parameter names and length limitations for each payment method in the SimpleOfflinePlugin.xml file.
No JSP code snippets are required by the SimpleOffline plug-in if you are using the predefined payment methods provided with WebSphere Commerce. If you require the SimpleOffline plug-in to support a new payment method, you must include the corresponding JSP code snippets in the storefront page to collect the required protocol data for the new payment method.
Restart WebSphere Commerce after you have completed your configuration changes to load the configurations for use.
A WebSphere Commerce trace component for the plug-in is provided for you to perform tracing of the plug-in when necessary. Refer to Trace components for more information.