Payments

Optimizely Customized Commerce provides interfaces and abstractions that let partners create their payment solutions; it does not provide default payment methods. Basic integration of Adyen payment gateway is provided as a sample in Customized Commerce Quicksilver project.

Classes in this topic are available in the following namespaces:

• Mediachase.Commerce.Orders
• Mediachase.Commerce.Orders.Dto

When creating and configuring payment methods in ECF, three components must be created, re-used, and configured: Payment Types, Payment Gateways and Payment Methods.

Payment types

Payment types classes contain the properties of a particular payment type. For example, a credit card payment type contains a credit card number, expiration date, and type, among others. All payment types inherit from the abstract class Payment. The most common payment types are built into Customized Commerce: Credit card (Obsoleted for PCI compliance), cash card, gift card, and invoice. In addition, a generic OtherPayment type is included. Payment types are meta-classes as part of MetaDataPlus.

Payment gateways

Payment gateways provide an interface to a system that provides payment processing. A payment type is passed to the payment gateway, and the gateway executes the payment transaction with the payment system, for instance, PayPal. One payment type is associated with each payment gateway. See also: Payment Gateways.

Payment methods

Payment methods represent the way the customer settles a purchase by processing a payment using a payment gateway.

To learn more about headless APIs for Customized Commerce, see the Content Delivery Guide or API reference.