Custom payment component for LWR checkout
Key Takeaway
Sensitive payment data stays in the provider's UI component, and your Apex payment gateway adapter verifies the transaction with a PostAuth request.
A custom payment component is a Lightning web component that you build for an LWR store's checkout page, so shoppers can pay through a payment provider you choose. The component follows a client-side model: it sends payment details straight to the provider, and an Apex payment gateway adapter in Salesforce then validates the transaction on its own. The main benefit is PCI compliance and security. Sensitive payment data stays in a cross-domain UI component owned by the provider, so the provider carries much of the PCI burden.
Payment component options
There are several payment component options.
| Component | For |
|---|---|
| Standard Payment and Dual Payment components | Server-side B2B implementations |
| Salesforce Payments component | Orgs that have Salesforce Payments |
| Custom payment component | Client-side implementations, where you build a custom component or adapt an existing one |