Processing orders with WebSphere Commerce Payments enabled

WebSphere Commerce provides an optional component called WebSphere Commerce Payments (formerly known as Payment Manager). WebSphere Commerce Payments is a protocol-independent payment transaction server for online merchants. It provides cash register-like functionality to a site, supporting multiple payment methods using protocol-specific cassettes. These cassettes are software components that can be attached to the WebSphere Commerce Payments framework to interpret generic payment and administrative commands into payment protocol-specific requests, which are then forwarded to the appropriate recipient, such as the payment gateway of an Acquirer institution. The end result is similar to when a cashier swipes a payment card at the checkout counter in a traditional store.

WebSphere Commerce Payments handles all the background details of Internet payments for the merchant (or a group of merchants, such as a store group), and provides a graphical interface to simplify transaction management. WebSphere Commerce Payments performs the following functions:

The merchant server interacts with WebSphere Commerce Payments by using APIs. Payments APIs are general enough to support other payment technologies.

WebSphere Commerce provides the following WebSphere Commerce Payments cassettes:

OfflineCard
Supports the processing of payment transactions that are made outside of WebSphere Commerce Payments (the payments require manual processing but information about the payments is stored in the WebSphere Commerce Payments database).
CustomOffline
Supports processing of custom payment transactions such as cash on delivery or COD, Bill-Me-Later, or coupons that are often executed outside of WebSphere Commerce Payments.
BankServACH
Supports processing of online electronic check payments using the BankServ payment gateway that interfaces with the Automated Clearing House Network (ACH).
Paymentech
Supports online authorization and settlement of credit card and non-PIN based debit card payments.
VisaNet
Supports processing of credit card transactions using the Vital Processing Services or First Horizon Merchant Services (FHMS) financial network including support for a purchasing card.

Installing and enabling WebSphere Commerce Payments

To use WebSphere Commerce Payments:

  1. AIXSun Solaris Operating EnvironmentiSeriesLinuxWindows If you have not already installed WebSphere Commerce Payments, install it now. Installation directions are provided in the Installation Guide for your platform. Your payments instance must be set up properly in order to connect the payment server to WebSphere Commerce.
  2. Start WebSphere Commerce Payments.
  3. Enable WebSphere Commerce Payments using the Change Flow notebook in the WebSphere Commerce Accelerator.
    1. Open the WebSphere Commerce Accelerator.
    2. From the Store menu, select Change Flow. Then select Payments.
    3. Select Enable WebSphere Commerce Payments, and click OK.
  4. To enable the cassettes in the WebSphere Commerce Accelerator, use the Configuration Manager:
    1. Open the Configuration Manager.
    2. Expand the hostname.
    3. Expand Payments.
    4. Expand Instance List.
    5. Expand instance_name.
    6. Expand Instance Properties.
    7. Click Cassettes.
    8. For each cassette you want to enable, select it, and click >
    9. Click Apply.

    You need to enable these cassettes for the merchant that corresponds to the store, and then create the accounts. Doing so will cause the cassettes to be displayed in the WebSphere Commerce Accelerator.

  5. Configure WebSphere Commerce Payments.

    1. Access the WebSphere Commerce Payments user interface from a browser by typing the following URL:
       http://host_name:port/webapp/PaymentManager
      

      where:

      host_name
      The domain-qualified host name of the machine where Payments is installed.
      port
      The SSL port used by WebSphere Commerce Payments. The default SSL port is 5433.
    2. Type your Payments user ID and password. Click Logon.
    3. If one was not created when you published the store, add a merchant. From the Merchant Settings menu, select Add a merchant. Provide the appropriate information, making sure that the Merchant Number you enter is identical to the Store ID number of the store that you are connecting to WebSphere Commerce Payments.
    4. Return to Merchant Settings, and click on the cassette icon next to the merchant. Select an appropriate cassette.
    5. Add accounts:
      1. If one was not created when you published the store, add an account. From Accounts, select Add an account, and provide the appropriate information for the account (for example, currency, account number). For more details on creating the accounts, refer to the appropriate cassette guide listed below. For the BankServ cassette, you should create two accounts: one with the value of BillMe and another one with COD. Once you complete this step for each of the accounts, the payment methods should be available in the WebSphere Commerce Accelerator without having to do any changes to the JSP files.
      2. Repeat the previous step for every currency you would like to support; each currency requires its own account.
    6. Add brands (for offline card cassette only)
      1. Click on the link for the account name you created.
      2. Click Brands on the next page.
    7. Select Add a brand, type a brand name and click Create brand.
    8. Repeat the previous step for every brand you would like to support for that account (for example, Visa, MasterCard).
  6. Log off WebSphere Commerce Payments.

to:

Edit this file so that any Java code using the resource bundle is eliminated. For example, replace all the (String)resourceBundle.get("xxxxxxx") calls with hard coded strings, such as "XXXXXXXX".

ShoppingArea/CheckoutSection/StandardCheckout/StandardCreditCard.jsp

Cassette for VisaNet:

<option value="VisaNet">VisaNet</option

or

Cassette for Paymentech

<option value="Paymentech"</option>

Modify only the line of the cassette you want to use for the store. This line is added after the following line:

<select name="cardBrand">

Feedback