Payment plugins

PaymentPlugin is available when you build solutions with the payment processing components of Optimizely Commerce Connect. A payment type is passed to the payment plugin, which executes the transaction against the payment system. Each payment plugin is associated with a specific payment type.

Classes in this topic are available in the following namespace:

• EPiServer.Commerce.Order — Contains IPaymentPlugin.

IPaymentPlugin is an improvement over IPaymentGateway. It supports the abstraction APIs and serializable carts. The following activities work the same as in Payment gateways:

• Payment plugin properties
• Using a built-in payment type
• Creating a custom payment plugin

One important difference: IPaymentPlugin takes IPayment as a parameter, while IPaymentGateway takes Payment.

PaymentProcessingResult ProcessPayment(IOrderGroup orderGroup, IPayment payment);

A sample implementation of the Adyen payment gateway is available in the Quicksilver Commerce reference sample project on GitHub.