Salesforce B2B LWR: Cybersource package v1.8.0 fails to render Flex Microform fields

[mashkon]

Hello,

Has anyone successfully implemented Cybersource Payments for Salesforce B2B and D2C managed package v1.8.0 in a Salesforce B2B Commerce LWR storefront?

We are using the standard packaged components with no custom development. The payment form renders, but the Cybersource-hosted Card Number and CVV fields remain blank.

We see these errors:

cybsb2b.getFlexKey
HTTP 400
{"error":[{"message":"The Apex request is invalid."}]}

cybsb2b__PTS_FlexMicroformHostD2C
HTTP 503

The 503 response contains Salesforce’s site_down/maintenance.html page. We have verified:

• Package version 1.8.0
• Correct TEST payment configuration and store association
• Cybersource endpoints in Experience Builder Trusted Sites
• Salesforce Trusted URLs and applicable CSP directives
• All Classes permission set assigned to the buyer
• Access to PTS_FlexMicroformController and PTS_KeyGenerationApi
• PTS_FlexMicroformHostD2C Visualforce page access
• Experience site is active and published
• Logout/login and browser cache clearing

We have also seen a CSP refusal involving the packaged Microform host. We are investigating whether Flex Microform SDK v2.11/2.12 and its use of globalThis is incompatible with legacy Lightning Locker, but we have not confirmed that this explains the Apex 400 or Visualforce 503.

Questions:

1. Has anyone encountered these errors with package v1.8.0 on B2B LWR?
2. Does this package require Lightning Web Security rather than legacy Lightning Locker?
3. Are any additional Salesforce Site, Visualforce, package-license, or buyer-profile permissions required?
4. Is there a known patch or newer package build?
5. What should PTS_FlexMicroformHostD2C return when opened through the underlying Salesforce Site URL?

Any working configuration details or troubleshooting guidance would be appreciated. 

[Karen85]

I’d also check the Site and Visualforce permissions carefully, as the 400 and 503 errors suggest the packaged components may not be accessible correctly through the Experience site.

[mashkon]

Thank you both, this was resolved. Apparently some buyer permissions were missing in the package, but now we experience Salesforce Commerce checkout failure.

The authorization itself is successful. CyberSource reviewed the transaction and confirmed it was processed successfully by both CyberSource and the Vital/TSYS processor with reason_code=0000 and “Request was processed successfully.”

We also tested the recommended by Cybersource amount of $2,102 to generate a normal TSYS/Vital sandbox response. That transaction returned:
* Successful authorization
* AVS Y / Raw AVS Y
* Approval code present
* Successful transaction in Business Center

However, Salesforce still receives:
* HTTP 500
* SYSTEM_ERROR

Cybersource support center isnt helpful at all, they just bouncing me between some random people. Anyone knows how to get to team responsible for the CyberSource Salesforce managed package?