Technology Partner
Upgrade the Salesforce B2C Commerce Cartridge
- Download the code from the ISV Integration Toolkits section on GitHub.
- Zip the payments_metadata folder.
- Go to Administration > Site Development > Site Import & Export and upload the payments_metadata.zip file.
- Import the uploaded zip file.
- Check release notes for any configuration parameters that might have changed.
Result: The cartridge is successfully upgraded to the latest version.
Migrating to Version 2.0.0
Version 2.0.0 is a major release. When upgrading from an earlier release, review these changes:
- Add the new Business Manager cartridge. Add
bm_cybs_sfrato the Business Manager cartridge path (it provides the Webhook Manager page). See Configure Salesforce B2C Commerce. - Update the service endpoints. The endpoints have changed to
https://apitest.visaacceptance.com(test) andhttps://api.visaacceptance.com(production). - Update the Payment Credentials service URL under Administration > Operations > Services.
- Re-check site preferences. Preference groups were renamed to
VisaAcceptance_*and regrouped. Payer Authentication,SCA, Decision Manager, and Transaction Type are now under Salesforce Default Acceptance Configuration and apply to the Salesforce default card form (Direct API) only. For Unified Checkout, configure these controls in the . Confirm your settings after importing metadata. - Removed features:
- Flex Microform: card capture is now Unified Checkout or the Salesforce default payment form (Direct API).
- Standalone Google Pay: Google Pay is now offered through Unified Checkout. Standalone Apple Pay is still supported.
- Network Token webhook: token updates are now retrieved through the Token Management Service (
TMS) API.
- Set up webhooks. Order updates are now driven by webhook notifications. Subscribe using the new Webhook Manager. The Salesforce jobs remain as a fallback. See Webhooks.
- Authentication. API authentication continues to use your
RESTShared Secret and Key ID. Message-Level Encryption (MLE) uses a P12 certificate. - Message-Level Encryption. The Message-Level Encryption preference
VisaAcceptance_CertificateAliashas been renamedVisaAcceptance_RequestMLECertificateAlias, andVisaAcceptance_CertificateSerialNohas been removed. New configuration steps are available for Request and Response MLE, including a master MLE switch (off by default).
Was this page helpful?
Thanks for your feedback!
Last published: November 18, 2026