Payments system integration

Integrate a payments system with the store to process shopper payments for the site. We can also integrate with pricing and tax service providers to manage the pricing and tax calculations for the store.

Important: Your payment system must support an interface that can record and send all card-holder data directly from the store to the payment system. WebSphere Commerce supports two main payment integration methods:

1. Punch-out payment, where payment information is submitted in a form that is hosted by the external payments system.We can integrate punch-out payment into the Digital Commerce store checkout flow through:

   • A JavaScript call directly to an external payments system, and then retrieve the authorization through an integration call.

   • An iFrame where the contents in the iFrame come from the external payments system.

   • A redirect to a page that is hosted by the external payments system. When the payment is complete, the shopper is redirected back to the store.

   • A pop-up window where the contents in the pop-up window come from the external payments system. For an example on implementing a pop-up window integration, see Enable punch-out payment.

   See Punch-out payment overview.

2. Payment tokenization, where payment information is submitted in a form that is hosted by WebSphere Commerce. Digital Commerce calls the payment service provider to replace sensitive payment information such as credit card number with a surrogate value (token).

   See Payment tokenization overview

• Punch-out payment overview
  We can integrate WebSphere Commerce with a payment service provider through punch-out payment. With punch-out payment, the shopper enters payment information through a third-party payment form. The payment form can be integrated into the WebSphere Commerce store through iFrame, pop-up window, or redirect. In this model, WebSphere Commerce never receives or saves any sensitive data such as credit card information.

• Payment tokenization overview
  We can integrate WebSphere Commerce with a payment service provider through payment tokenization. With payment tokenization, the shopper enters payment information through WebSphere Commerce, and WebSphere Commerce calls the payment service provider to replace sensitive payment information such as credit card number with a surrogate value (token). In this model, WebSphere Commerce only saves the token for payment processing, and non-sensitive data such as masked credit card number for display purposes.