Payments tutorials

The following tutorials demonstrate how to use the Payments subsystem for WebSphere Commerce and WebSphere Commerce Payments.
Tutorial Learning objectives Description
Tutorial: Configuring the SimpleOffline plug-in with two payment methods
After completing this tutorial you will understand how to:
  • Configure your payment system to use synchronous event
  • Create a payment configuration group for your store
  • Configure each XML configuration file in the payment configuration group for two payment methods
  • Configure the XML configuration files for the payment plug-in controller
  • Configure the XML configuration files for the SimpleOffline payment plug-in
  • Configure two payment business policies for your store
 This tutorial demonstrates how to configure a payment system for your store. This tutorial uses two payment methods: myVISA and PayInStore as examples to show how to setup the payment methods using the SimpleOffline plug-in.
Tutorial: Developing a payment plug-in A payment plug-in is required when WebSphere Commerce needs to integrate with a payment service provider to process electronic payments and refunds. This tutorial demonstrates how to write a payment plug-in to integrate with the Payment Service Provider Simulator, a sample application that mimics the services offered by a real payment service provider. This tutorial shows the steps involved in developing and deploying a new payment plug-in.
Tutorial: Passing sensitive payment data to back-end processes when the data is not persisted
By completing this tutorial, you can understand how to complete the following tasks:
  • Update store pages to retrieve and send sensitive payment information such as card verification code data
  • Update OrderProcess functions to receive card verification code data as parameters for payment authorization when a customer submits an order
 In this tutorial, you learn how to customize a WebSphere Commerce starter store to pass sensitive payment data to back-end processes. Specifically, to send card verification code information to the order process for payment authorization when your site does not temporarily store the card verification code for payment authorization purposes.