Commerce Payment Component Options

Options include standard and custom components for card payment or purchase order processing. For client-side implementations, you can also build a custom payment component, or adapt an existing one.

Required Editions
Available in: Enterprise, Unlimited, and Developer Editions
Available in: B2B Commerce and B2B2C Commerce

Choose the Payment or Dual Payment component for server-side B2B store implementations. The dual component processes both card payments and purchase orders.

After you set up your B2B server-side payment gateway and payment service provider, use Experience Builder to select your payment component. If you have a third-party payment provider, you use the Payment or Dual Payment component.

  • The Payment component includes a credit card option.
  • The Dual Payment component includes both a credit card option and a purchase order option and is for B2B implementations only.

To use either of these payment components see Customize Payments in Checkout.

The Salesforce Payments component accepts a variety of payment methods including digital wallets. Customizable in Experience Builder, the Salesforce Payments Component also supports B2B purchase order business models.

If you have Salesforce Payments:

  • Use the Salesforce Payments component. Adminstrators confgure the component payment keys and optionally enable saved payment methods. If you have a B2B store, you can also choose to show a purchase order option.

  • If you have Salesforce Payments and you want to provide digital wallet payment options, add and configure the Express Checkout component. Express Checkout supports Apple Pay, Google Pay, PayPal, and Venmo.

To implement the Salesforce Payments component, see Customize Payouts in Checkout and Add Salesforce Payments Features to Store Checkout.

A custom, client-side payment component interacts directly with a payment provider. Implementation requires creating a custom LWC checkout UI component that is provisioned to interact directly with the payment gateway.

For more on the architecture, flow, and advantages of a custom client-side component, see Set Up Client-Side Payment Processing.

The Purchase Order Component supports B2B stores that don’t require a payment gateway.

While not technically a payment, a purchase order in a B2B (LWR) store can β€œstand in” as a form of payment. Buyers enter a purchase order number and place an order. (If there is neither payment authorization nor purchase order for the cart, the order cannot be placed.) The purchase order number is used downstream system for invoicing and payment processing. Purchase orders do not trigger payment flows out of the box within the Salesforce system.

If you want your B2B store to accept purchase orders only, use the Purchase Order Component. To implement a Purchase Order component, see Customize Payments in Checkout.