Deprecated feature

Customizing the environment for a payment cassette

For a store to use an IBM payment cassette, you must first have selected the WebSphere Commerce Payments component for installation. The WebSphere Commerce installation program installs both the WebSphere Commerce Payments framework and the cassette software. You must then use the Configuration Manager to perform necessary post-installation tasks, such as creating a Payments instance and adding a cassette to an instance.

About this task

To make the included cassettes available for use, you can open Configuration Manager, expand the Instance Properties for your Payments instance, and use the Cassettes panel to select cassettes.

After adding a payment cassette to a Payments instance, check the following customization steps to ensure that your starter store can process payments by using the payment cassette you have selected.

Procedure

Modify the store .jsp file to specify the payment cassette.

You must modify the store .jsp file to use a particular cassette.

For a list of .jsp files to review for possible modification, see Table 1.

To modify the .jsp file, follow these steps:

Create a store in WebSphere Commerce using a starter store.
Go to the following directory:
- WC_eardir/Stores.war/
The store you created has its own directory within the war directory.
From your store's directory, open the OrderSubmitForm.jsp file in a text editor.
The Contract Tools in the WebSphere Commerce Accelerator supports all payment cassettes. The OrderSubmitForm.jsp file must honor the payment terms and conditions of the contract that was set up between the Buyer organization and the Seller.
Search for the following text in the OrderSubmitForm.jsp file:
```
 if (info[i].getPolicyName().trim().equals("OfflineCard"))
```
Change the name of the payment policy from OfflineCard to one of the following as appropriate:
```
CustomOffline
BankServACH
Paymentech
VisaNet
VisaNet_PCard
```
For more information about policies, see the POLICY database table in the WebSphere Commerce Development online help.

The policy for CustomOffline supports processing of custom payment transactions such as cash on delivery or COD, Bill-Me-Later or coupons that are often run outside of WebSphere Commerce Payments.

The policy for BankServACH supports processing of online electronic check payments using the BankServ payment gateway that interfaces with the Automated Clearing House Network (ACH).

The policy for Paymentech supports online authorization and settlement of credit card and non-PIN based debit card payments.

The policy for VisaNet supports processing of credit card transactions using the Vital Processing Services or First Horizon Merchant Services (FHMS) financial network.

Note: If you are using the Cassette for VisaNet with purchasing card support, select VisaNet_PCard rather than VisaNet.

If your store uses the Quick Checkout function, you should also change the name of the payment policy in these other files:
```
ShoppingArea\CheckoutSection\QuickCheckoutSubsection\QuickCheckoutForm.jsp
UserArea\AccountSection\QuickCheckoutProfileSubsection\QuickCheckoutProfileForm.jsp
```
If you are using the credit card method of payment and need to add additional fields in the user interface to collect additional information from the user, review the /Snippets/EDP/PaymentMethods/StandardCreditCard.jsp file also for possible modifications. See Table 1 for path information.
To enable credit card brands to be displayed when doing a purchase with a particular payment method that involves the use of credit cards, be sure that an option value exists in the .jsp file for the payment method. For example, to enable credit card brands to be displayed when doing a purchase with the Paymentech payment method, search for <select name="cardBrand">. Add the following code:
```
<option value="Paymentech">Paymentech</option>.
```


JSP file	Business model/sample	Purpose of change
`/ShoppingArea/CheckoutSection/StandardCheckoutSubsection/ OrderSubmitForm.jsp`	Consumer direct , hosted reseller	change payment policy name from OfflineCard
`/ShoppingArea/CheckoutSection/QuickCheckoutSubsection/ QuickCheckoutForm.jsp /UserArea/AccountSection/QuickCheckoutProfileSubsection/ QuickCheckoutProfileForm.jsp`	Consumer direct	change payment policy name from OfflineCard
`/Snippets/EDP/PaymentMethods/StandardCreditCard.jsp`	Consumer direct	enable credit card brand to display
`/ShoppingArea/CheckoutSection/StandardCheckoutSubsection/ StandardCreditCardDisplay.jsp`	Advanced B2B direct, B2B indirect - supply	enable credit card brand to display

Check the cassette's Cashier profile.
A WebSphere Commerce Payments Cashier profile should be available for any IBM payment cassette provided with WebSphere Commerce. The Cashier profile is used to create orders in the Payments component.

You may want to edit the Cashier profile to set certain parameters, such as the APPROVEFLAG and DEPOSITFLAG parameters.

Cashier profiles associated with IBM-provided payment cassettes include:
```
WC51_BankServACH.profile
WC51_CustomOffline_BillMe.profile
WC51_CustomOffline_COD.profile
WC51_OfflineCard.profile
WC51_VisaNet.profile
WC51_VisaNet_PCard.profile
WC_Paymentech.profile
```
The cassette profile should be stored in the WebSphere Commerce instances profile directory.

To locate the directory in which the profile is stored:
1. Open the WebSphere Commerce configuration file
2. Look at the directory specified by the ProfilePath attribute of the Payment Manager element in the configuration file. This attribute specifies where the profile should be located.
If you edit the cassette's Cashier profile to set parameters, be sure to save the profile in the following directory:
- WC_eardir /xml/payment
The actual cashier profile used by a payment business policy is specified by the profileName property value in the Properties field of the payment business policy. Refer to the POLICY database table.
Check the cassette's .jsp file that supports the clerk order (guest order) placement page.
If an order clerk places a guest order on behalf of a customer, payments are processed using WebSphere Commerce Accelerator. The payment data for the cassette is gathered using the cassette's .jsp file.

The cassette .jsp file is called the "payment attribute page" in WebSphere Commerce. The actual page used is specified by the attrPageName property value in the Properties field of the payment business policy. For more information see the POLICY database table in the WebSphere Commerce Development online help. Both the store flow and WebSphere Commerce Accelerator flow should make use of the payments attribute page.

The cassette's .jsp file should already be located in the following directory:
- WC_eardir/CommerceAccelerator.war/ tools/order/buypages
If you want to customize the "buy page" information, modify the .jsp file accordingly.
Configure the Merchant Settings.
To configure the merchant for the IBM payment cassette, follow the instructions provided in the cassette. Use the Administration Console or the Payments user interface (http://host_name:port/webapp/PaymentManager) to change merchant settings. You must have Payment Administrator or Merchant Administrator authority in WebSphere Commerce Payments to configure merchant settings.