WebSphere Commerce Payments
WebSphere Commerce provides an optional component called WebSphere Commerce Payments (formerly known as IBM Payment Manager).
If you wish to use WebSphere Commerce Payments with your store, you must include a payment asset file in your store archive. Before publishing your store archive, ensure that your Payments instance is started, then, when the store archive is published, the payment asset file (included as part of the starter store archives) sets up the following information in WebSphere Commerce Payments:
- The merchant_ID in the WebSphere Commerce Payments database.
- The type of cassette used in the store.
- An account in the WebSphere Commerce Payments database for each currency specified as supported by the store in the payment asset file. If your store does not support the currency specified in the payment asset file, the account will not be created.
- A brand, or brands, for each account.
To set up a payment asset file and set up your store to use WebSphere Commerce Payments, do the following:
- Create payment data in the form of an XML file (paymentinfo.xml) that is loaded during store publish using the Administration Console. This configures WebSphere Commerce Payments with the merchant and the brand types specified for the store being published.
Note: paymentinfo.xml does not populate tables in the WebSphere Commerce Server database. It configures WebSphere Commerce Payments. paymentinfo.xml is only applicable if you are using offline credit card as the payment method.
After the store archive has been published, you can place orders using the payment information set up in the starter store archive. If you want to add new brands, you must configure WebSphere Commerce Payments to work with each brand.
If you will use an IBM payment cassette other than the OfflineCard or CustomOffline cassette, modify the starter store Web assets as described in Customize environment for a payment cassette.
- Complete the set up of WebSphere Commerce Payments for your store using the Administration Console or the WebSphere Commerce Payments user interface. If you use the Administration Console, menu items appear on the Payments menu. If you use the WebSphere Commerce Payments user interface, menu items appear under Administration in the navigation frame. For more information on setup tasks, see the topic "Setting up WebSphere Commerce Payments for your store".
If you intend to use a payment mechanism other than WebSphere Commerce Payments, the steps to follow to use your payment mechanism are similar.
Advanced orders Event-driven payments
WebSphere Commerce provides an advanced orders processing option as an enhanced alternative to standard orders processing. The advanced orders processing environment uses:
- Payment plug-ins
- Payment Plug-in Controller
Payment assets required to process event-driven payments are:
- XML configuration files for event-driven payments. These files define the payment rules used and payment/refund method configuration.
- Deployment descriptor. This XML file defines the plug-in to the Payment Plug-in Controller
A paymentinfo.xml file is considered a payment asset in an advanced orders environment only if the WCPayments plug-in is used.