Scope limits of checkout payment processing
Key Takeaway
Checkout payment processing only authorizes the card before order placement and doesn't support sale transactions, so capturing the charge must be handled downstream of checkout.
Checkout payment processing in Salesforce B2B Commerce connects a store's checkout to a payment gateway so buyers can pay by credit card. The scope is narrow. The checkout flow only authorizes payments. Paying for one order with several credit cards works only in a tightly constrained setup. These limits decide which design fits a store's payment requirements.
How checkout connects to a payment gateway
The Commerce payment architecture combines checkout APIs, the Payment Gateway, and an integrated payment package for B2B and B2C stores. The architecture is built on the Commerce payment framework, which other Salesforce products such as Revenue Cloud and Order Management also use.
In this framework, you write an Apex class that acts as a Payment Adapter between Salesforce and the payment gateway. The framework handles the rest:
- Creating payment-specific records in Salesforce
- Logging gateway calls for auditing
- Handling idempotency
The framework is also secure and PCI compliant.
To collect credit card payments, you create a payment gateway and connect it to your checkout. The adapter you build to talk to the gateway depends on whether you implement a server-side or a client-side payment process.