# Step 11: Configure CC Admin settings

You need to override several settings to enable the custom payment methods and tax calculations.

{% hint style="info" %}
Download the **DR-CC-Config-Setting.xlsx** file for this task. It contains the information you need to perform this task.
{% endhint %}

{% file src="<https://2536014854-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MNZuPvN3iGOwRD0PjQh%2F-MO3f8vZ4-yP0NP3pqh_%2F-MO3gYjM8p2Ug4WjzJU0%2FDR-CC-Config-Settings.xlsx?alt=media&token=66e9ad83-5a45-4f3f-89e1-3a5b9f6a1114>" %}
DR-CC-Config-Settings.xlsx
{% endfile %}

## Step 11a: Create Configuration Modules for payment types <a href="#step-11a-create-configuration-modules-for-payment-types" id="step-11a-create-configuration-modules-for-payment-types"></a>

Create a Configuration Module for each payment type. You can find the payment type settings on the Config Modules tab in the DR CC Config Settings spreadsheet. Note that you perform this step at the Global Settings level. The changes you make here apply to all of your storefronts.

To create Configuration Modules for credit cards and PayPal:

1. Select the **CC Admin tab**.\ <img src="https://2536014854-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MNZuPvN3iGOwRD0PjQh%2F-MS_5jCKXdlKkq8-oYlt%2F-MS_5rKDXxqyhS_U81sm%2FCC-Admin-tab.png?alt=media&#x26;token=88ebcc98-d909-4de1-abfd-11c908752e77" alt="" data-size="original">
2. Select **Configuration Modules**, as shown below. \
   ![](https://2536014854-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MNZuPvN3iGOwRD0PjQh%2F-MS_5jCKXdlKkq8-oYlt%2F-MS_5wLV2uqpFHEKdrMD%2FConfiguration-Modules.png?alt=media\&token=e106d396-a754-45af-98de-62668e4f3256)
3. &#x20;Create a module for Credit Cards. \
   a. Click **New** in the **Configuration Module** pane. The Configuration Module dialog appears. \
   b. Type`Payment CC` in the **Name** field and `pmt_cc` in the **API Name** field. ![](https://firebasestorage.googleapis.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-MBAqKPiXugAQI_J5f3e%2F-MG5NPToT48eeXINMViO%2F-MCvgz5y0Fi3LyiYHuSS%2FConfiguration-Module-pmt_cc.png?alt=media\&token=904ca1f5-4046-422d-a981-4b3cce8c303e)
4. &#x20;Create a module for PayPal. \
   a. Click **New** in the **Configuration Module** pane. \
   b. Type `Payment PP` in the **Name** field and `pmt_pp` in the **API Name** field. \
   ![](https://2536014854-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MNZuPvN3iGOwRD0PjQh%2F-MS_5jCKXdlKkq8-oYlt%2F-MS_66jfHJMo1d56yV1a%2FConfiguration-Module-pmt_cc.png?alt=media\&token=d27d3176-1537-4839-a43a-1d50e3ed4791) \
   The new payment modules will appear under Configuration Modules.&#x20;

<div align="left"><img src="https://2536014854-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MNZuPvN3iGOwRD0PjQh%2F-MS_5jCKXdlKkq8-oYlt%2F-MS_6GrT275s8FkPSdHK%2FConfiguration-Metadata-Payment-PP.png?alt=media&#x26;token=0fcce872-0a24-492c-bc77-8de38abf51b6" alt=""></div>

## Step 11b: Create configuration metadata for the payment modules

Configure the following custom Digital River Salesforce B2B Commerce App pages in CC Admin for them to show up in Storefront: Edit Page, New Page, Pay Page, and Proc. Note that you perform this step at the Global Settings level. The changes you make here apply to all of your storefronts.

The following table lists the required settings for each field. You can also find these settings on the Configuration Metadata tab in the **DR CC Config Settings** spreadsheet.

| Module     | Name      | API Name | Description                                                                                             |
| ---------- | --------- | -------- | ------------------------------------------------------------------------------------------------------- |
| Payment CC | Edit Page | edit     | VisualForce Page leveraged for editing existing Credit Card payment information via the My Account page |
| Payment CC | New Page  | new      | VisualForce Page leveraged for saving new Credit Card payment information via the My Account page       |
| Payment CC | Pay Page  | pay      | VisualForce page for rendering the Enter New CC form in Checkout                                        |
| Payment CC | Proc      | proc     | Payment Processor for backend processing                                                                |
| Payment PP | Edit Page | edit     | VisualForce Page leveraged for editing existing PayPal payment information via the My Account page      |
| Payment PP | New Page  | new      | VisualForce Page leveraged for saving new PayPal payment information via the My Account page            |
| Payment PP | Pay Page  | pay      | VisualForce page leveraged for processing PayPal payments in the Checkout flow                          |
| Payment PP | Proc      | proc     | PayPal Payment Processor                                                                                |

In the case of Drop-in, we configure only the Payment DR module, which should pull in all payment types configured by Digital River.

To create configuration settings for the Payment CC and Payment PP configuration modules:

1. Under **Configuration Modules**, click the module name (for example, Payment CC).
2. Click **New** (highlighted in the image below) to create the **Edit Page** configuration metadata for the configuration module. \
   ![](https://2536014854-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MNZuPvN3iGOwRD0PjQh%2F-MS_5jCKXdlKkq8-oYlt%2F-MS_7ukeO5VuBm8KiTHa%2FPayment_CC-New-Metadata.png?alt=media\&token=2a9adee4-8a73-4c00-8b1f-5dfc6006e25e)
3. Use the information associated with the module in the table above to complete the Edit Page configuration metadata. \
   ![](https://2536014854-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MNZuPvN3iGOwRD0PjQh%2F-MS_5jCKXdlKkq8-oYlt%2F-MS_8FhKabFh47P_c1aX%2FEdit-Page-Configuration-Metadata.png?alt=media\&token=53b5169d-dea0-444a-9a9a-51a0c3e961aa) \
   **Note**: Don't select the **Externally Safe** check box.
4. Repeat steps 2 and 3 to create configuration metadata for New Page, Pay Page, and Proc.
5. Repeat steps 1 through 4 to create configuration metadata for Payment CC.

After adding the configuration metadata to both of the Payment Modules, the Configuration Module for both modules should look like:

<div align="left"><img src="https://2536014854-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MNZuPvN3iGOwRD0PjQh%2F-MS_5jCKXdlKkq8-oYlt%2F-MS_9X3QDUc40HSyVZ1A%2FPayment-Module-with-configuration-metadata.png?alt=media&#x26;token=f2749f33-768d-4b91-8f9a-a345efb4e454" alt=""></div>

![](https://2536014854-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MNZuPvN3iGOwRD0PjQh%2F-MS_5jCKXdlKkq8-oYlt%2F-MS_9b0NoEMjWxcCafdS%2FPayment-Module-with-configuration-metadata-2.png?alt=media\&token=179e0d6c-25e1-4386-9003-4cdc19eece34)

## Step 11c: Create a store's configuration settings <a href="#step-11c-create-a-stores-configuration-settings" id="step-11c-create-a-stores-configuration-settings"></a>

You need to create custom Salesforce B2B Commerce App Pages in CC Admin for them to show up in Storefront. Note that you perform this step at the storefront level. The changes you make here apply to a specific storefront. If you have more than one storefront, you should repeat this step for each storefront.

You can find these settings on the Configuration Settings tab in the **DR CC Config Settings** spreadsheet.

To create or update a store's configuration settings:

1. From **CC Admin**, click **Global Settings** in the upper-right corner and select your storefront (for example, **DefaultStore**). \
   ![](https://2536014854-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MNZuPvN3iGOwRD0PjQh%2F-MS_5jCKXdlKkq8-oYlt%2F-MS_9ze-kGftJNO43FbA%2Fglobal-settings.png?alt=media\&token=a5ed5488-5ce1-4a79-98e2-68f2a9f59788) \
   **Note**: After selecting the storefront, the select box will still display Global Settings. However, the left navigation pane will display <*storefront name*> SETTINGS and the options associated with the store.
2. Click **Configuration Settings** under **<*****storefront name*****> SETTINGS**.\
   &#x20;![](https://2536014854-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MNZuPvN3iGOwRD0PjQh%2F-MS_5jCKXdlKkq8-oYlt%2F-MS_A46u7Dpy5Ca6tNVd%2FConfiguration-Settings.png?alt=media\&token=c7858f9f-ae8c-4ec8-98a9-0c1bc18dd4d9)
3. Select the module name (for example, Body Includes Begin from the first row in the table above) from the **Module** dropdown list in the right pane. \
   ![](https://2536014854-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MNZuPvN3iGOwRD0PjQh%2F-MS_5jCKXdlKkq8-oYlt%2F-MS_AS7OWMjRSPPQeif7%2FBody-Includes-Begin.png?alt=media\&token=09c5b9ee-f354-4034-86dd-8dfca83cb801)
4. To create a new page setting for the module, click **New**. The New Page Setting dialog appears.\
   &#x20;![](https://2536014854-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MNZuPvN3iGOwRD0PjQh%2F-MS_5jCKXdlKkq8-oYlt%2F-MS_AYlIVfOJxNfkVyf7%2FNew-Page-Setting.png?alt=media\&token=c671e651-961d-4a0b-97e3-2070c4df71c0)
5. Complete the fields using the information from the first row in the table above.

   a. Select the module name from the **Module** dropdown list. \
   b. Select the configuration value from the **Configuration** dropdown list. \
   c. Type the page value in the **Page** field and select the corresponding value. Once you select it, the field shows a corresponding internal value. For example, if you type Order Confirmation and select **Order Confirmation** from the dropdown list, the field shows **OrdCnfm**. \
   d. Type the value in the **Value** field. \
   e. Click **Create**. When you click Create, the new module appears in the Configure Settings list and displays **Delete** in the ACTION column, and the name of the storefront appears in the **STOREFRONT** column.
6. Repeat steps 3 through 5 for each additional row in the table above.
7. Repeat steps 1 through 6 for each additional storefront.