Configure `Cybersource` for Salesforce B2C Commerce {#salesforce-b2c-configuration}
===================================================================================

Configure the `Cybersource` cartridge in `Salesforce` B2C Commerce `Salesforce` Business Manager.
After installation, configure the cartridge through the `Salesforce` Business Manager to enable payment processing capabilities.

1. Base Configuration

   1. Set up the cartridge path.

      #### ADDITIONAL INFORMATION

      In `Salesforce` Business Manager, go to Administration \> Sites \> Manage Sites \> \[yourSite\] \> Settings.

      #### Step Result

      For Cartridges, enter int_cybs_sfra:int_cybs_sfra_base:app_storefront_base and click Apply.

   2. Upload metadata

      #### ADDITIONAL INFORMATION

      Go to the folder *`Cybersource`/metadata/payments_metadata/sites/*.

      #### ADDITIONAL INFORMATION

      1. Rename the folder `yourSiteID` with your site ID from `Salesforce` Business Manager (this can be found by looking up Administration-\>Sites-\>Manage Sites).
      2. Zip the *payments_metadata* folder.
      3. Go to Administration-\>Site Development-\>Site Import \& Export and upload the *payments_metadata.zip* file.
      4. Import the uploaded zip file.

      #### Step Result

      Upon successful import, this metadata is created:

      * Site Preferences: `Cybersource`_Core, `Cybersource`_DeliveryAddressVerification, `Cybersource`_DeviceFingerprint, `Cybersource`_PayerAuthentication, `Cybersource`_TaxConfiguration, `Cybersource`_Tokenization, `Cybersource`_DecisionManager, `Cybersource`_MLE, `Cybersource`_ApplePay, `Cybersource`_GooglePay, VisaAcceptance_SecureIntegrationConfiguration
      * Service: PaymentHttpService
      * Payment Processor
      * Payment Method
      * Job: Payment :Decision Manager Order Update
2. Minimum Configuration

   1. `Cybersource` Core

      #### ADDITIONAL INFORMATION

      Go to Merchant Tools \> Site Preferences \> Custom Preferences \> `Cybersource` Core and set these configuration parameters:

      * Enable `Cybersource` Cartridge: Enable the cartridge.
      * `Cybersource` Merchant ID: The transacting Merchant ID (MID) assigned to you.
      * `Cybersource` REST KeyId: The Key from your REST API Shared Secret Key.
      * `Cybersource` REST Secret Key: The Shared Secret from your REST API Shared Secret Key.
      * Commerce Indicator:
        * Use `internet` for eCommerce transactions.
        * Use `MOTO` if you are using the store for call center transactions only.
          {#salesforce-b2c-configuration_ul_rjz_zkn_yhc}
   2. Services

      #### ADDITIONAL INFORMATION

      The target endpoint must be set to send transactions to test or production (live).

      #### ADDITIONAL INFORMATION

      Go to Administration \> Operations \> Services \> Payment Credentials and enter the appropriate URL:

      * Test: `https://apitest.cybersource.com`
      * Production (live): `https://api.cybersource.com`
3. Accept Payment Cards

   #### ADDITIONAL INFORMATION

   Prerequisite: Go to Merchant Tools \> Ordering \> Payment Methods, select `CREDIT_CARD` and verify that the payment processor is `PAYMENTS_CREDIT`.

   1. Select Card Capture Method

      #### ADDITIONAL INFORMATION

      Our cartridge supports these card capture methods: `Unified Checkout`, Microform, and Direct API.

      #### ADDITIONAL INFORMATION

      If you enable Apple Pay, Google Pay, and/or `Click to Pay` in `Unified Checkout`, these payment methods are displayed in a single widget.  
      `Unified Checkout` and Microform might qualify you for PCI-DSS SAQ:A as 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.

      #### ADDITIONAL INFORMATION

      To select the card capture method, go to Merchant Tools \> Site Preferences \> Custom Preferences \> Secure Integration Configuration.

#### RESULT

The `Cybersource` cartridge is now configured with basic settings. Additional optional configurations can be applied based on your specific requirements.