WebSphere Commerce Payments Cassette plug-in
The WebSphere Commerce Payments plug-in implements the Payment plug-in specification and supports the payment transactions.
When a request is sent from Payment Rules to the WebSphere Commerce Payments, the WebSphere Commerce Payments forwards the request to a specific payment plug-in. If the request is for the WebSphere Commerce Payments plug-in, it gets the information and creates the appropriate request for WebSphere Commerce Payments (for example, an APPROVE request). The plug-in analyzes the response from WebSphere Commerce Payments and returns information. If the response from WebSphere Commerce Payments is an error, the plug-in produces an error.
The WebSphere Commerce Payments plug-in does not externalize all the functions of WebSphere Commerce Payments. It does, however, provide APIs to process different payment actions. The plug-in maps the APIs for payments and queries that are defined in the payment plug-in specification to a subset of the WebSphere Commerce Payments APIs. The APIs that are not supported by the component and the plug-in are provided by WebSphere Commerce Payments.
The WebSphere Commerce Payments plug-in is a payment plug-in provided in WebSphere Commerce for use with the traditional WebSphere Commerce Payments component. WebSphere Commerce Payments is an optional component that can be selected during WebSphere Commerce installation. For this plug-in to work, have selected WebSphere Commerce Payments at installation.
The WebSphere Commerce Payments plug-in acts as a bridge to the traditional multipayment framework of WebSphere Commerce Payments and the use of payment cassettes. The plug-in follows the Payment plug-in specification to process payment actions (financial transactions) with WebSphere Commerce Payments. WebSphere Commerce Payments acts as a payment back-end system to the WebSphere Commerce Payments.
The WebSphere Commerce Payments plug-in enables the following types of payment transactions to take place. By supporting these transactions, the WebSphere Commerce Payments plug-in provides backwards compatibility for functions used by existing WebSphere Commerce Payments users.
- Offline payment transactions
Merchants can choose to record activity about payments that are handled in an offline fashion. (However, for the sake of simplicy, the SimpleOffline plug-in should be used to perform offline processing.) When payments are handled offline, there is no direct connection with a payment back-end system and therefore no automatic recording of activity. The WebSphere Commerce Payments plug-in enables such transactions to be recorded through the use of traditional payment cassettes called the OfflineCard Cassette and the CustomOffline Cassette. The OfflineCard cassette is used for payment card transactions. For example, it can be used to record a payment approval made when a credit card is swiped through a swipe box. A custom offline payment transaction is a form of offline payment that supports manual payment transactions, such as "collect on delivery" and "bill me later" transactions or some other form of customized offline payment as defined by the merchant.
- Transactions involving the VisaNet financial processing system
The WebSphere Commerce Payments plug-in enables merchants to send Internet credit card transactions to the VisaNet system for processing, through use of the traditional payment cassette called the Cassette for VisaNet. The Cassette for VisaNet supports credit card processing through the Vital Processing Services or First Horizon Merchant Services networks.
- Transactions using the BankServ payment gateway to interface with the Automated Clearing House (ACH) Network
The WebSphere Commerce Payments plug-in supports the processing of online electronic checks through the traditional payment cassette called the Cassette for BankServACH.
- Transactions involving a Paymentech payment gateway to process credit and debit card transactions
The WebSphere Commerce Payments plug-in supports the processing and recording of credit card and non-PIN based debit card payments through the Cassette for Paymentech. The Cassette for Paymentech enables real-time transactions to be sent to the Paymentech system for processing.
Important! To provide compatibility with WebSphere Commerce Payments, the WebSphere Commerce Payments plug-in is intended to be used as is and should not be modified. You can, however, modify supporting configuration files to select which functions to use, and provide your own Cashier profiles for use with WebSphere Commerce Payments and third-party cassettes.
Location
The WebSphere Commerce Payments plug-in package contains:
- A stateless session bean:
- com.ibm.commerce.payments.plugin.wcpayments.bean.WCPaymentsPluginBean
- com.ibm.commerce.payments.plugin.wcpayments.bean.WCPaymentsPlugin
- com.ibm.commerce.payments.plugin.wcpayments.bean.WCPaymentsPluginBeanHome
- PluginDeployment.xml - the payment plug-in deployment descriptor for the WebSphere Commerce Payments plug-in which defines the plug-in to the WebSphere Commerce Payments.
- A resource bundle for the WebSphere Commerce Payments plug-in error messages.
- Cashier profiles used by the WebSphere Commerce Payments plug-in. Unlike the SimpleOffline plug-in, there is no special side file like SimpleOfflinePlugin.xml that is used to describe the various payment methods supported by the plug-in. Instead, the WebSphere Commerce Payments plug-in uses the following Cashier profiles (located in the same directory as the PluginDeployment.xml file):
- WCPPlugin_BankServACH.profile
- WCPPlugin_CustomOffline_BillMe.profile
- WCPPlugin_CustomOffline_COD.profile
- WCPPlugin_OfflineCard.profile
- WCPPlugin_Paymentech.profile
- WCPPlugin_VisaNet.profile
The JAR file for the plug-in and plug-in deployment descriptor are located in the following directories:
WC_eardir/Payments_Plugin_WebSphere Commerce Payments.jar- WC_eardir/xml/config/payments/ppc/plugins/WebSphere Commerce Payments/PluginDeployment.xml
WC_eardir/Payments_Plugin_WebSphere Commerce Payments.jar- WC_eardir/xml/config/payments/ppc/plugins/WebSphere Commerce Payments/PluginDeployment.xml
WebSphere Commerce Payments plug-in security
The WebSphere Commerce Payments plug-in delegates the encryption and storage of sensitive data in the database to the WebSphere Commerce Payments.
The plug-in does not have any access control. It grants the accesses permitted by the Payment Rules subcomponent and the WebSphere Commerce Payments. The plug-in uses the WebSphere Commerce user ID and encrypted password to connect to WebSphere Commerce Payments. The user ID is defined in the WebSphere Commerce Payments plug-in deployment descriptor.
The plug-in can be configured to use a secure (SSL) or non-secure connection to WebSphere Commerce Payments. You can configure usage of SSL in the WebSphere Commerce Payments plug-in deployment descriptor.
(C) Copyright IBM Corporation 1996, 2006. All Rights Reserved.