Payments instruments

 

WebSphere Commerce Payments

WebSphere Commerce provides two implementations for WebSphere Commerce Payments in this release. The deprecated implementation (formerly known as IBM Payment Manager) supports WebSphere Commerce Payments cassettes to connect to the backend payment service provider. The brand new implementation uses WebSphere Commerce Payments plug-ins to connect to the backend payment service provider. These two implementations can coexist in WebSphere Commerce but the deprecated implementation is an optional component. The deprecated implementation can be optionally installed using custom installation and a Payment instance must be created using Configuration Manager. The WebSphere Commerce Payments instance can be started or stopped separately from WebSphere Commerce instance. The new implementation is one of mandatory components of the WebSphere Commerce instance.

The starter stores use the new implementation of WebSphere Commerce Payments. If you want to use the new implementation of WebSphere Commerce Payments with your own store, include the available Payment business policy registries (These Payment policy registries are configured to use the new implementation.) in your store archive.

If you want to use the deprecated implementation of WebSphere Commerce Payments with your own store, also include the available Payment business policy registries and a Payment asset file in your store archive. See the "Setting up WebSphere Commerce Payments for your own store" topic for more details. This topic also includes information about setting up the new implementation of Payments with your own (not starter store) store.

Menus for the new implementation of WebSphere Commerce Payments are available in WebSphere Commerce Accelerator. Menus for the old implementation of WebSphere Commerce Payments are available in WebSphere Commerce Administration Console. For more information on how to manually set up the old implementation of WebSphere Commerce Payments to work with your store, see the topic "Setting up WebSphere Commerce Payments for your store" and the topic "Configuring the starter stores to use the old Payments".

 

Configure the starter stores to use the old Payments

The old Payments is no longer configured by default when a starter store is published. All published starter stores are configured with the new Payments by default.

The old Payments must be manually configured to work with the published starter stores. In order to get the old Payments to work with the published starter stores...

  1. Old Payments must be installed using the custom install option of the WebSphere Commerce installation wizard.

  2. An old Payments instance must be created using WebSphere Commerce Configuration Manager.

  3. Before the starter store is published, the old Payments instance must be started

  4. After the starter store is published, the old Payments must be manually configured to work with the published starter store using the instructions in the topic "Setting up WebSphere Commerce Payments for your store".

Related concepts

Related tasks