Payments

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

Classes in this topic are available in the following namespaces:

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 classes contain the properties of a particular payment type. For example, a credit card payment type typically includes a credit card number, expiration date, and card type, among other details. All payment types inherit from the abstract class Payment. The most common payment types are built into Commerce Connect: 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 within MetaDataPlus.

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. Each payment gateway is associated with a specific payment type. See also: Payment Gateways.

Payment methods refer to the methods by which customers settle purchases by processing payments through a payment gateway.

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