Payments (dev)

Optimizely Commerce Connect provides interfaces and abstractions that let partners build their own payment solutions. It does not include default payment methods. The Commerce Connect Quicksilver project contains a basic Adyen payment gateway integration as a sample.

Classes in this topic are available in the following namespaces:

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

When creating and configuring payment methods, three components must be created, reused, and configured: payment types, payment gateways, and payment methods.

Payment types

Payment type classes contain the properties of a specific payment type. For example, a credit card payment type typically includes a credit card number, expiration date, and card type. All payment types inherit from the abstract class Payment.

Commerce Connect includes the following common payment types:

• Credit card (deprecated for PCI compliance).
• Cash card.
• Gift card.
• Invoice.
• OtherPayment — a generic fallback type.

Payment types are meta-classes within MetaDataPlus.

Payment gateways

Payment gateways expose a payment-processing system to Commerce Connect. The gateway receives a payment type, then executes the transaction against the underlying payment system (for example, PayPal). Each payment gateway is associated with a specific payment type. For details, see Payment gateways.

Payment methods

Payment methods are the means by which customers settle purchases — each payment method routes the transaction through a specific payment gateway.