UAT·Ops About UAT-Ops

Payment gateways for Salesforce Commerce Cloud (B2C)

Gateway pages

About Salesforce Commerce Cloud (B2C)

Salesforce Commerce Cloud B2C (the former Demandware platform, currently sold under the Agentforce Commerce for B2C name) is a hosted storefront platform for larger retailers and brands. Salesforce runs the infrastructure; merchants configure sites in Business Manager and ship code in cartridges, or build a separate React front end.

There are two storefront models. The Storefront Reference Architecture (SFRA) is a server-rendered site where features are added by placing cartridges on a site's cartridge path. Headless storefronts use PWA Kit, a BSD-licensed React framework that talks to the Commerce API and deploys to Salesforce's Managed Runtime.

Payments follow the same split. Salesforce Payments is the native option: a plugin_commercepayments cartridge for SFRA, backed by a Stripe or PayPal merchant account connected in Business Manager, covering cards, Apple Pay, Google Pay, PayPal, Venmo, Klarna, Afterpay and several European bank methods, with a test mode that takes Stripe test cards. Third-party processors arrive as LINK cartridges on SFRA (Stripe, Adyen, Worldpay and others are free downloads on AppExchange; the processor bills its own fees) or as npm packages that carry the provider's front-end and server components inside a PWA Kit app. Salesforce's B2C pricing is quote-only and the pages fetched name no surcharge for using an outside gateway.

For integration testing there is no local runtime. Work happens against an On-Demand Sandbox created through the Sandbox API, billed in credits per minute and deleted automatically at its time-to-live, so a cartridge or headless payment integration is exercised on a hosted instance, with webhooks such as Stripe's signed events landing on that sandbox's hostname.

How payments work on Salesforce Commerce Cloud (B2C)

Built-in payments
Salesforce Payments, installed on SFRA storefronts as the plugin_commercepayments cartridge. Merchants connect a Stripe or PayPal merchant account in Business Manager; card, wallet and local methods run through Stripe, with PayPal and Venmo through PayPal. Test mode accepts Stripe test cards.1
Third-party gateways
Outside gateways integrate as LINK cartridges on SFRA or SiteGenesis (Stripe, Adyen, Worldpay and others are listed on AppExchange as free downloads; the processor's own fees apply) or as npm packages on PWA Kit / Managed Runtime for headless storefronts. Salesforce's published B2C pricing page lists no per-transaction surcharge for using an outside gateway, and no such fee was found in the sources fetched; edition pricing is quote-only.2
Checkout extensibility
SFRA checkout is customised by adding cartridges to a site's cartridge path and registering payment processors and payment methods in Business Manager; controller endpoints such as CheckoutServices.js can be extended or replaced. Headless storefronts on PWA Kit are React apps that talk to the Commerce API and carry the payment provider's front-end and back-end components in the app itself.1

What we checked

  • Salesforce Payments is delivered to SFRA storefronts as the plugin_commercepayments cartridge, after which admins configure payment methods, zones and site settings in Business Manager.1
  • Salesforce Payments uses Stripe and PayPal merchant accounts and covers credit cards, PayPal, Venmo (US only), Apple Pay, SEPA debit, iDEAL, EPS, Bancontact, Klarna and Afterpay, plus express checkout buttons on product pages.1
  • Salesforce Payments is configured under Administration > Global Preferences > Salesforce Payments in Business Manager; Test Mode verifies the setup with Stripe test card numbers and Live Mode is used on production instances.3
  • The B2C script API class dw.extensions.payments.SalesforcePaymentRequest exposes element types for card, Apple Pay, payment request (Google Pay), PayPal, Venmo, Afterpay/Clearpay, SEPA debit, iDEAL, Bancontact and EPS, and configures Stripe Elements options.4
  • Stripe's integration is a LINK cartridge with separate SFRA and controller cartridges; for SFRA the site cartridge path is set to app_stripe_sfra:int_stripe_sfra:int_stripe_core and STRIPE_CREDIT and STRIPE_APM payment processors are created in Business Manager.2
  • The Stripe cartridge validates signed webhooks using a signing secret stored as a site preference, and its install guide shows SFRA controllers such as CheckoutServices.js and RedirectURL.js being extended or replaced.2
  • The Stripe app for Salesforce B2C Commerce is listed on AppExchange as free to download with a Stripe account required, supports SFRA 4.0 and above and SiteGenesis, and Stripe's own product fees apply to usage.5
  • The Worldpay Payments Cartridge for B2C Commerce is an AppExchange listing that never requires payment and targets B2C Commerce.6
  • AppExchange's Commerce Cloud collection lists payment integrations for B2C Commerce including PayPal Complete Payments, Adyen and Cybersource alongside search, fulfillment and ERP connectors.7
  • Salesforce describes two kinds of B2C Commerce solution on AppExchange - cartridges (generic or application-specific code containers) and headless integrations (API-only, or composable storefronts on PWA Kit combining Commerce and third-party APIs).8
  • Adyen ships an SFRA cartridge (SFRA 5, 6 and 7, available on AppExchange) and a separate Composable Storefront npm package for PWA Kit that uses Adyen Web Drop-in and is deployed through Managed Runtime.9
  • The @adyen/adyen-salesforce-pwa package is MIT-licensed, installed from npm, needs an Adyen test account with API and client keys, and ships with a reference React app not meant for production.10
  • PWA Kit is a BSD 3-Clause React framework for B2C Commerce storefronts on the Commerce API; a project starts with npx @salesforce/pwa-kit-create-app (Node 18+), runs locally with npm start and deploys to Managed Runtime with npm run push.11
  • In the headless model the PWA Kit front end is separated from the commerce engine and bridged by the B2C Commerce API, with Managed Runtime hosting and monitoring the storefront while B2C Commerce supplies pricing, promotions and search.12
  • An On-Demand Sandbox is created with the Sandbox API's POST /sandboxes method, specifying TTL in hours, start/stop schedulers and a resource profile; status and lifecycle operations use GET /sandboxes/{id} and POST /sandboxes/{id}/operations, and a new sandbox contains no storefront data.13
  • On-Demand Sandboxes need the Sandbox API User or Business Manager Admin role in Account Manager; the default Medium profile (1 CPU, 10 GB) consumes 1 credit per minute running and 0.3 credits per minute stopped, and a realm-level TTL deletes sandboxes automatically.14
  • On-Demand Sandboxes are provisioned through the Developer Sandbox REST API, Control Center or CLI tools such as sfcc-ci, use usage-based pricing with credits consumed for uptime and downtime, and replace slower POD-based sandboxes.15
  • Salesforce's B2C Commerce pricing page lists Growth, Plus and Premium editions as contact-for-pricing in every currency and says nothing about payment processing fees or third-party gateway surcharges.16

Sources

  1. https://trailhead.salesforce.com/content/learn/modules/cc-commerce-payments/cc-explore-commerce-paymentsofficial documentation · checked 2026-09-11
  2. https://docs.stripe.com/connectors/salesforce-commerce-cloud/implementation-guideofficial documentation · checked 2026-09-11
  3. https://trailhead.salesforce.com/content/learn/modules/cc-commerce-payments/cc-set-up-and-testofficial documentation · checked 2026-09-11
  4. https://salesforcecommercecloud.github.io/b2c-dev-doc/docs/current/scriptapi/html/api/class_dw_extensions_payments_SalesforcePaymentRequest.htmlofficial documentation · checked 2026-09-11
  5. https://appexchange.salesforce.com/appxListingDetail?listingId=a0N4V00000J61BeUAJ&tab=emarketplace listing · checked 2026-09-11
  6. https://appexchange.salesforce.com/appxListingDetail?listingId=b84e930e-9eb7-49b6-9868-cfc251a0a7b7marketplace listing · checked 2026-09-11
  7. https://appexchange.salesforce.com/mktcollections/curated/commercecloudmarketplace listing · checked 2026-09-11
  8. https://trailhead.salesforce.com/content/learn/modules/b2c-commerce-solutions-on-appexchange-quick-look/discover-b2c-commerce-solutions-appexchangeofficial documentation · checked 2026-09-11
  9. https://docs.adyen.com/plugins/salesforce-commerce-cloudofficial documentation · checked 2026-09-11
  10. https://github.com/Adyen/adyen-salesforce-headless-commerce-pwacode repository · checked 2026-09-11
  11. https://github.com/SalesforceCommerceCloud/pwa-kitcode repository · checked 2026-09-11
  12. https://trailhead.salesforce.com/content/learn/modules/commerce-pwa-kit-and-managed-runtime/discover-commerce-pwa-kit-and-commerce-managed-runtimeofficial documentation · checked 2026-09-11
  13. https://trailhead.salesforce.com/content/learn/modules/b2c-on-demand-sandbox/b2c-create-monitor-on-demand-sandboxofficial documentation · checked 2026-09-11
  14. https://trailhead.salesforce.com/content/learn/modules/b2c-on-demand-sandbox/b2c-configure-on-demand-sandboxofficial documentation · checked 2026-09-11
  15. https://trailhead.salesforce.com/content/learn/modules/b2c-on-demand-sandbox/b2c-explore-on-demand-sandboxesofficial documentation · checked 2026-09-11
  16. https://www.salesforce.com/commerce/b2c-ecommerce/pricing/vendor pricing page · checked 2026-09-11

Last verified 2026-09-12 · Reviewed by a person 2026-09-25

Integration capabilities, requirements, pricing, availability, and vendor policies may change over time. UAT-Ops documents information based on the authoritative sources and testing available at the time of review.

Where newer information, testing, or vendor documentation materially changes a published claim, UAT-Ops may revise the page to reflect the most current verified information. Readers should confirm time-sensitive requirements with the relevant vendor before making production or purchasing decisions.