Commerce Cloud Payments—the embedded payments processing capability inside the Commerce Cloud platform—has emerged as a distinct commercial dimension in the broader Commerce Cloud commitment. The capability spans payment method support, gateway integration, fraud and risk management, alternative payment methods, and the underlying payment processing economics. The commercial implications are material and frequently underestimated in the initial Commerce Cloud purchase discussion.
The Payments commercial structure is layered. The base payments capability—standard credit card processing, common gateway integration, basic fraud screening—is included in the standard Commerce Cloud commitment. Advanced payments capabilities—premium gateway integrations, alternative payment methods, advanced fraud and risk management, embedded payment processing, and the broader Salesforce Payments product surface—are positioned as add-on commercial commitments with explicit pricing implications.
What the Payments capability set includes
The Commerce Cloud Payments capability surface has expanded materially since the original launch. The 2026 capability set spans standard payment method support (credit card, debit card, common digital wallets), premium gateway integrations, alternative payment methods (BNPL, regional methods, account-to-account), embedded payment processing through Salesforce Payments, fraud and risk management (including advanced ML-based fraud screening), and chargeback and dispute management capabilities.
| Payments capability | Base | Standard add-on | Premium add-on |
|---|---|---|---|
| Standard payment methods | Included | Included | Included |
| Common gateway integration | Included | Included | Included |
| Premium gateway integrations | Limited | Standard | Standard |
| Alternative payment methods | Not available | Standard | Standard |
| Embedded Salesforce Payments | Not available | Available | Available |
| Basic fraud screening | Included | Included | Included |
| Advanced ML-based fraud | Not available | Limited | Standard |
| Chargeback management | Not available | Limited | Standard |
The Salesforce Payments embedded processing dimension
The most material commercial surface in the modern Commerce Cloud Payments discussion is the Salesforce Payments embedded processing capability. Salesforce Payments is an embedded payments capability that allows the customer to process payments through Salesforce's own payment processing relationships, rather than through a third-party gateway. The capability is positioned commercially as an integrated solution with simplified onboarding and unified reporting.
The economic decision involves three components. First, the per-transaction processing rates, which compete directly against the customer's existing payment processor rates. Second, the platform commitment associated with the Salesforce Payments capability, which may be priced as an add-on or bundled into the broader Commerce Cloud commitment. Third, the operational impact of the embedded processing—including the loss of payment processor optionality, the reduction in negotiating leverage against other payment processors, and the implications for the customer's broader payments strategy.
The four levers that move the price
1. Treat Salesforce Payments as a competitive payment processing decision
The Salesforce Payments commercial discussion should be framed as a competitive payment processing decision, not as an integrated platform capability. The customer should solicit competitive payment processing rates from at least two alternative processors before committing to Salesforce Payments. The competitive benchmarking is the foundation of the negotiation and prevents the default-integration overpay pattern.
2. Right-size the advanced payments capability set
The advanced payments capability set—premium gateway integrations, alternative payment methods, advanced fraud, chargeback management—should be scoped against the operational requirement, not against the maximum addressable capability surface. Customers with defined alternative payment method requirements (BNPL, regional methods) have a clear case for the capability. Customers without defined requirements should evaluate whether the operational value justifies the add-on cost.
3. Negotiate the per-transaction rates explicitly
The per-transaction processing rates are negotiable, particularly at the platform commitment phase. The customer should negotiate explicit rate tiers, with rates that are competitive with the customer's existing or alternative payment processor relationships. The negotiated rates produce material savings over the term, particularly for high-volume deployments.
4. Coordinate the Payments commitment with the broader Commerce Cloud commitment
The Payments commercial commitment should be coordinated with the broader Commerce Cloud commitment. The bundled negotiation captures volume leverage and prevents the negotiation-leverage dilution that occurs when payments capabilities are licensed sequentially. The bundling is particularly important when the Salesforce Payments capability is positioned as a strategic integrated platform decision.
The pitfalls that show up in the order form
Five patterns appear repeatedly in Commerce Cloud Payments order forms. First, Salesforce Payments is positioned as an integrated default rather than as a competitive payment processor decision. Second, the per-transaction rates are accepted at default vendor pricing without competitive benchmarking. Third, the advanced payments capability set is licensed at maximum scope without scoping against the use case. Fourth, the renewal mechanics are silent on the per-transaction rates, exposing the customer to discretionary repricing as transaction volume grows. Fifth, the order form does not preserve the customer's payment processor optionality, locking the customer into the Salesforce Payments capability for the contract term.
What a well-negotiated Payments commitment looks like
A well-negotiated Commerce Cloud Payments commitment has seven features. The Salesforce Payments decision is made against competitive payment processor benchmarking, not as a default integration. The per-transaction rates are explicitly negotiated with tier structures that protect against volume growth. The advanced payments capability scope is right-sized against the operational use case. The customer's payment processor optionality is preserved, with explicit terms for switching processors over the contract term. The renewal mechanics specify the per-transaction rate protections, with uplift on rates limited explicitly. The commitment is bundled into the broader Commerce Cloud commercial discussion. And the customer retains audit and reporting rights for the payments capability and processing volumes.
The fraud and risk management dimension
The advanced fraud and risk management capabilities deserve specific attention. Advanced ML-based fraud screening can produce material reductions in fraud losses and chargeback rates, with operational value that may meaningfully exceed the capability cost. The commercial discussion should incorporate the expected fraud loss reduction, the chargeback rate impact, and the operational value of the capability, not just the capability cost itself.
The negotiated approach is to frame the fraud capability commercial commitment against the fraud loss baseline. Customers with high fraud loss rates have a clear ROI case for the advanced capability; customers with low fraud loss rates should evaluate whether the operational value justifies the capability cost. The fraud capability is one of the few payments capabilities where the operational ROI math frequently justifies a maximum-scope commercial commitment.
Benchmark outcomes by deployment scale
For a mid-market Commerce Cloud customer with $20M-$80M annual GMV, the median annual Payments commercial commitment (including processing fees, advanced capability costs, and add-on capabilities) lands at $480,000-$1.8M. Top-quartile outcomes—achieved through competitive processor benchmarking and disciplined capability scoping—sit in the $320,000-$1.1M range. The bottom quartile lands at $720,000-$2.4M for equivalent deployments where Salesforce Payments was accepted as a default integration without competitive benchmarking.
For a large-enterprise Commerce Cloud customer with $200M-$800M annual GMV, the median annual Payments commercial commitment lands at $3.4M-$11.2M. Top-quartile outcomes reach $2.2M-$7.1M through disciplined negotiation. The bottom quartile lands at $5.6M-$14.4M for equivalent operational footprint.
Where to begin
If your Commerce Cloud Payments commitment is in scoping, the most useful first step is competitive payment processor benchmarking. Solicit per-transaction rates from at least two alternative payment processors, including the Salesforce Payments proposal. The benchmarking establishes the foundation for the per-transaction rate negotiation and prevents the default-integration overpay pattern.
If your Commerce Cloud Payments deployment is in production, the most useful first step is a payments-by-method analysis. Document which payment methods are actually used, which processing rates apply, and which advanced capabilities are operationally consumed. The analysis establishes the operational baseline for the next renewal negotiation and identifies capability cost that may not be operationally justified.
The renewal data that wins
The single most valuable artifact for a Commerce Cloud Payments renewal is a transaction-by-method usage report combined with a fraud-and-chargeback rate report: which payment methods are processing what volume, which rates apply, and what fraud and chargeback outcomes are being produced. The report establishes the operational baseline that supports the next renewal conversation and prevents the discretionary repricing that occurs when the customer arrives at renewal without operational data.
The strategic frame
The Commerce Cloud Payments commercial discussion is, ultimately, a strategic payments decision. The choice between Salesforce Payments and alternative processors has long-term implications for the customer's payments strategy, processor optionality, and cost trajectory. The commercial decision should be framed against that strategic question with explicit competitive benchmarking and disciplined capability scoping. Customers who treat the Payments decision as a strategic platform decision—with competitive benchmarking and disciplined scope—consistently outperform customers who treat it as a default integration that comes with Commerce Cloud.