Skip to main content
Welcome to the preview portal — This is an early release of the new Doc Hub experience, with more content coming soon.
Technology Partner

Configure the Salesforce B2C Commerce Cartridge


After installation, configure the cartridge through the Salesforce Business Manager to enable payment processing capabilities.

Minimum Configuration

Base Configuration

Set up the cartridge path in Salesforce Business Manager by going to Administration > Sites > Manage Sites > [yourSite] > Settings. For Cartridges, enter bm_cybs_sfra:int_cybs_sfra:int_cybs_sfra_base:app_storefront_base and click Apply.

Upload Metadata

  1. Go to the folder /metadata/payments_metadata/sites/.
  2. Rename the folder yourSiteID with your site ID from Salesforce Business Manager. This can be found by going to Administration > Sites > Manage Sites.
  3. Zip the payments_metadata folder.
  4. Go to Administration > Site Development > Site Import & Export and upload the payments_metadata.zip file.
  5. Import the uploaded zip file.

Upon successful import, this metadata is created:

  • Site Preferences: VisaAcceptance_Core, VisaAcceptance_SecureIntegrationConfiguration, VisaAcceptance_SalesforceDefaultAcceptance_Configuration, VisaAcceptance_ApplePay, VisaAcceptance_Tokenization, VisaAcceptance_DeviceFingerprint, VisaAcceptance_DeliveryAddressVerification, VisaAcceptance_TaxConfiguration, VisaAcceptance_MLE
  • Service: PaymentHttpService
  • Payment Processor
  • Payment Method
  • Jobs: Payment: Decision Manager Order Update, Payment: Refresh Payment Status

Minimum Configuration Settings

Configure the Visa Acceptance Core preferences by going to Merchant Tools > Site Preferences > Custom Preferences > Visa Acceptance Cartridge Configuration and setting these configuration parameters:

  • Enable Visa Acceptance Cartridge: enable the cartridge.
  • Merchant ID: the transacting merchant ID assigned to you.
  • REST Key Id: the key from your REST API shared secret key.
  • REST Secret Key: the shared secret from your REST API shared secret key.
  • Commerce Indicator:
    • For e-commerce transactions, use internet.
    • When you are using the store for call center transactions only, use MOTO.
  • Enable Visa Acceptance Test Endpoints: disabled by default. This enables the capture and authorization reversal endpoints (the ServiceFrameworkTest controller). Use only in a test environment.
  • Enable Meta Key: enable Meta Key for portfolio/account-level key management (optional).
  • Meta Key Portfolio Merchant ID: the portfolio/account merchant ID that owns the Meta Key (optional).

Services

The target endpoints need to be set in your Salesforce B2C Commerce environment.

Configure the services by going to Merchant Tools > Operations > Services > Payment Credentials and enter these URLs:

EnvironmentURL
Testhttps://apitest.visaacceptance.com
Productionhttps://api.visaacceptance.com

Payment Capture Method

  1. Go to Merchant Tools > Ordering > Payment Methods, select CREDIT_CARD, and verify that the payment processor is PAYMENTS_CREDIT.
  2. Go to Merchant Tools > Site Preferences > Custom Preferences > Secure Integration Configuration. Choose from:
    • Unified Checkout
    • Direct API (default Salesforce payment form)

Unified Checkout might qualify you for PCI-DSS SAQ:A because the card number is collected in secure fields and never resides on your server. If you need access to the card number, select Direct API. This option increases your PCI burden.

If you select Unified Checkout, see Unified Checkout Configuration.

Result: The cartridge is now configured with basic settings.

Optional Configuration

Additional optional configurations can be applied based on your specific requirements.

Unified Checkout Configuration

There are required and optional configuration options for Unified Checkout.

Additional transaction responses from Unified Checkout are delivered by webhook notifications and require a Message-Level Encryption Response Certificate. See Webhooks and Response MLE for setup steps.

Enable Digital Payment Methods

  1. Go to Merchant Tools > Site Preferences > Custom Preferences > Secure Integration Configuration.
  2. In the Digital Payment Methods in Unified Checkout field, select Apple Pay, Google Pay, or Click to Pay. You can choose any or all of the options.
  3. Enable Unified Checkout for Cart and Mini Cart to display digital payment methods for quick checkout on the cart and mini cart pages.

Unified Checkout Digital/Alternative Payment Methods Payment Processor Mapping

If you want to offer Digital or Alternative Payment Methods through Unified Checkout, ensure each payment method has the correct Payment Processor mapping. Go to Merchant Tools > Ordering > Payment Methods and verify these mappings:

  • DW_APPLE_PAY: Payment Processor PAYMENTS_APPLEPAY.
  • DW_GOOGLE_PAY: Payment Processor PAYMENTS_GOOGLEPAY.
  • DW_PAZE: Payment Processor PAYMENTS_PAZE.
  • PAYPAL: Payment Processor PAYMENTS_PAYPAL.
  • VENMO: Payment Processor PAYMENTS_VENMO.
  • CLICK_TO_PAY: Payment Processor PAYMENTS_CLICK_TO_PAY.
  • BANK_TRANSFER: Payment Processor BANK_TRANSFER (for echeck).

Unified Checkout Optional Configuration

To set these options, go to Merchant Tools > Site Preferences > Custom Preferences > Secure Integration Configuration.

  • Checkout Label: choose your own checkout page label. You can choose up to 60 characters, and the default value is "Secure Payments powered by ".
  • Enable Express Pay: separates digital wallet payment methods from the main card capture widget.
  • Unified Checkout Version: pin a specific Unified Checkout version. Available for version 1.0 onwards. Leave this field blank for the latest version (recommended).
  • Card Prefix (BIN) in Unified Checkout response:
    • None: the Card BIN is not returned.
    • Six-digit: the 6 digit BIN is returned.
    • Eight-digit: the 8 digit BIN is returned.
  • Non-Wallet Unified Checkout Display Mode: if Express Pay has been enabled, this applies to the non-express pay methods only.
    • Embedded: the payment widget is displayed within the checkout page.
    • Sidebar: the payment widget appears on the side of the customer's browser.

Apple Pay Standalone

To offer Apple Pay outside of Unified Checkout, enable Apple Pay in your Salesforce B2C Commerce store. Before you begin, complete Integrating Apple Pay into Your System.

  1. Configure Salesforce Business Manager.
    • From the menu, choose Merchant Tools > Site Preferences > Apple Pay.

    • Select the Apple Pay Enabled? check box.

    • Complete the Onboarding form:

      • Ensure that the Apple Merchant ID and the Apple Merchant Name values you enter match the settings in your Apple account.
      • Ensure that all other fields match your supported settings:
        • Country Code: enter the country code for the location of your site. The country code is a two letter ISO 3166 country code (for example, US).
        • Merchant Capabilities: check the box for 3-D Secure; leave the other fields unchecked.
        • Supported Networks: select the types of payment you support; Amex, Mastercard, and Visa are supported by .
        • Required Shipping Address Fields: select the fields that are required on the shipping form. recommends Email, Name, Phone, and Postal Address.
        • Required Billing Address Fields: select Name and Postal Address.
    • Complete the Storefront Injection form. Select where to display Apple Pay buttons on your site.

    • Complete the Payment Integration form:

      • Use Commerce Cloud Apple Pay Payment API? Checked.
      • Payment Provider URL:
        • Test: https://apitest.visaacceptance.com/partner/demandware/payments/v1/authorizations
        • Production: https://api.visaacceptance.com/partner/demandware/payments/v1/authorizations
      • Payment Provider Merchant ID: enter your merchant ID.
      • API Version: v1.
      • Use Basic Authorization? Unchecked.
      • Payment Provider User: —
      • Payment Provider Password: —
      • Use JWS? Set to Yes.
      • JWS Private Key Alias: Merchant.p12 Key Alias.

      The private key alias is generated when you upload your .p12 key file (from self-serve) to Salesforce Business Manager under Administration > Operations > Private Keys and Certificates.

    • Click Submit.

  2. Register your domain in Salesforce Business Manager.
    • Go to Merchant Tools > Site Preferences > Apple Pay.
    • Under the Domain Registration section, complete these fields:
      • In the Apple Sandbox section, click Register Apple Sandbox to register Salesforce B2C to the Apple Sandbox account.
      • In the Apple Production section, click Register Apple Production to register Salesforce B2C to the Apple Production account.
  3. Set the transaction type. Go to Merchant Tools > Site Preferences > Custom Preferences > Apple Pay and choose Authorization or Sale.

Payer Authentication and 3-D Secure

Configure Payer Authentication and 3-D Secure for enhanced transaction security.

  1. Go to Merchant Tools > Site Preferences > Custom Preferences > Salesforce Default Acceptance Configuration.
  2. In Payer Authentication Mode, choose one of these options:
    • Yes: all transactions process with 3-D Secure.
    • No: no transactions process with 3-D Secure.
    • Data Only + Yes: Data Only is used for Visa and Mastercard/Maestro. All other card brands process with 3-D Secure.
    • Data Only + No: Data Only is used for Visa and Mastercard/Maestro. All other card brands process without 3-D Secure.
  3. Enable the Enable SCA option to enforce Strong Customer Authentication.

Tokenization

Tokenization enables your customers to save their payment cards securely for future payments.

Follow these steps to enable tokenization:

  1. Go to Merchant Tools > Site Preferences > Custom Preferences > Tokenization Configuration.
  2. Enable the Enable Tokenization Services option to turn on Tokenization.
  3. Enable the Enable Limiting Saved Card option to set the limits associated to saving cards.
  4. In the Saved Cards Allowed option, enter the number of cards a customer can save in the defined time limit.
  5. In the Reset Interval option, specify the number of hours before the saved card limit resets.
  6. Enable the Network Token Updates option to prompt the cartridge to check for Token Life Cycle Updates prior to checkout. Your merchant ID needs to be configured for Network Tokens.

Fraud Screening

Enable Fraud Screening to alert the cartridge to look for fraud screening responses. Fraud Screening profiles must be set up in the .

Follow these steps to enable fraud screening:

  1. Go to Merchant Tools > Site Preferences > Custom Preferences > Salesforce Default Acceptance Configuration.
  2. Choose the Enable Decision Manager Services option. This setting applies for both Decision Manager and Fraud Management Essentials.

Updates to transactions marked as REVIEW are delivered through webhooks. The Update Job is available as a fallback option.

  1. Set the Conversion Detail Report Lookback Time value. If you are using REVIEW rules and configure the Decision Manager Update Job, set the number of hours to look back for updates to transactions in REVIEW status. The maximum value is 24 hours.
  2. To enable the Decision Manager Update Job to poll for updates to the reviewed transactions, go to Administration > Operations > Jobs and select Payment: Decision Manager Order Update. Set these values:
    • ID: enter a job ID.
    • Description: enter the job description.
    • ExecuteScriptModule.Module: int_cybs_sfra_base/cartridge/scripts/jobs/DMOrderStatusUpdate.js
    • ExecuteScriptModule.FunctionName: orderStatusUpdate
    • ExecuteScriptModule.Transactional:
      • True: all changes occur as a single atomic operation. If any error occurs during the job, the system rolls back all changes to maintain data consistency.
      • False: no automatic rollback is applied. Merchants must handle transaction logic manually. This is often preferred for large batch jobs.
    • ExecuteScriptModule.TimeoutInSeconds: set the function timeout value.

Device Fingerprint

Device fingerprinting collects information about the device used when paying for an order and can assist in fraud screening decisions.

  1. Go to Merchant Tools > Site Preferences > Custom Preferences > Device Fingerprint Configuration.
  2. Enable the Enable DeviceFingerprint Service option.
  3. In the Organization ID field, enter the Organization ID. Contact support if you do not know this value.
  4. In the ThreatMetrix URL field, enter the URL that points to the JavaScript that generates and retrieves the fingerprint of the device.
  5. In the TTL (Time to Live) field, enter the number of milliseconds to wait before generating a new fingerprint for any given customer session.

Delivery Address Verification

To verify the customer's shipping address during checkout, configure Delivery Address Verification services.

  1. Go to Merchant Tools > Site Preferences > Custom Preferences > Delivery Address Verification Configuration.
  2. Enable the Delivery Address Verification Services option.

Tax Calculation

To calculate local taxes once the customer enters their address at checkout, configure the Tax Calculation services.

  1. Go to Merchant Tools > Site Preferences > Custom Preferences > Tax Configuration and set these options.
  2. Enable the Enable Tax Calculation field.
  3. Configure these tax settings:
    • List of Nexus States: list the states to calculate tax for.
    • List of Nexus States to Exclude: list the states to not calculate tax for.
    • Merchants VAT Registration Number: enter your VAT registration number if you have one.
    • Default Product Tax Code: enter the default tax code to use for products in the basket without a tax code.
    • Purchase Order Acceptance City
    • Purchase Order Acceptance State Code
    • Purchase Order Acceptance Zip Code
    • Purchase Order Acceptance Country Code
    • Purchase Order Origin City
    • Purchase Order Origin State Code
    • Purchase Order Origin Zip Code
    • Purchase Order Origin Country Code
    • Ship From City
    • Ship From State Code
    • Ship From Zip Code
    • Ship From Country Code

Webhooks

Order updates, fraud screening review decisions, and Unified Checkout transaction responses are delivered through webhook notifications, configured and managed from the Webhook Manager page in Salesforce Business Manager. See Webhooks for subscription and payload details.

Message-Level Encryption

Message-Level Encryption (MLE) encrypts request and response payloads using a REST certificate, and includes a master MLE switch that is off by default. See Message-Level Encryption for certificate and configuration details.

Last published: November 18, 2026