Advanced orders Configuring a payment plug-in

Plug-ins provided in WebSphere Commerce

If you are using a payment plug-in provided by WebSphere Commerce, the configuration tasks you need to perform are as shown:

  1. Map the plug-in you want to use with a payment back-end system in the PaymentSystemPluginMapping.xml file. See Mapping a payment system to a payment plug-in for instructions.
  2. Ensure that the payment system name is reflected in the PaymentMethodConfiguration XML file and RefundMethodConfiguration XML file used by the event-driven payments subcomponent.
  3. Set up the payment configuration and refund configurations IDs for the payment methods/refund methods you intend to use. See Defining a payment configuration for event-driven payments for instructions.
  4. Ensure that event-driven payment rules are configured appropriately. See Configuring payment processing (event-driven payments).
  5. Restart WebSphere Commerce to make the payment plug-in active.

Other plug-ins

If you are using some other plug-in (such as a third-party plug-in), follow the same instructions as for plug-ins provided in WebSphere Commerce. If there are special properties that apply to the plug-in, ensure that the deployment descriptor includes those properties. Properties can also be set in the PaymentSystemPluginMapping.xml file. For more information about the deployment descriptor, refer to the Payment plug-in specification.

Address information

If you want to use the address information entered by customers through your online store, ensure that the address parameters (keywords or name-value pairs) as provided in WebSphere Commerce match the requirements of both your payment plug-in and any payment back-end system your plug-in communicates with. Address information requirements can vary by geography and not all payment back-end systems use the same address data. The payment plug-ins provided with WebSphere Commerce generally process commonly used address parameters.

Feedback