Help & Support

Elevate Your Agents with AgentExchange Solutions
Easily enhance Agentforce with pre-built AI solutions from AgentExchange. Browse, install, and deploy agents, actions, and apps directly into your environment. Tell Me More

Have Questions?

Cybersource Payments for Commerce on Core (B2B/D2C)

Cybersource and B2B or D2C Commerce on Lightning/Core

Free  

Never requires payment

Try It
Industries
Retail
Business Need
Payments Processing
Requires
B2B Commerce
D2C Commerce

Rating

Reputation

MVP
Recognized by Salesforce for their leadership, expertise, and generosity
Top Reviewer
Contribute reviews that encourage conversation and help others make informed decisions
Ranger
Lifelong learners who have earned the Ranger rank or higher on Trailhead
2
Lifetime average
Showing 1 of 1 Review
Sort by

B2B LWR integration blocked and unable to reach appropriate support team

We are implementing version 1.8.0 of this managed package in a Salesforce B2B Commerce LWR storefront using the standard packaged components with no custom development. The payment form loads, but the hosted Card Number and CVV fields do not render. The package produces errors from its getFlexKey Apex method and PTS_FlexMicroformHostD2C page, completely blocking credit-card checkout. We followed the technical guide and verified the payment configuration, trusted URLs, permission sets, packaged Apex access, Visualforce access, and site publication. The support case was reportedly escalated to Level 2, but it appears to have returned to Level 1. We are now receiving troubleshooting instructions for Salesforce B2C Commerce/SFCC Business Manager, which is a different product and does not exist in our Salesforce B2B LWR environment. We would appreciate contact from the Cybersource team responsible for the Salesforce B2B/D2C Core managed package. At this stage, we need product-specific engineering assistance, confirmation of compatibility with the current LWR security model, and clarification on whether a patched package version is available. The package may meet our requirements once operational, but the current technical issue and difficulty reaching the correct support team have left our implementation blocked.