---
schema_version: "1"
id: a83f1fc78e1ae884c356cfd88d3892b7476648c3af26c5f1bf3886dfc9d4a224
title: SiteGenesis Configuration for Salesforce Payments
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/cc/264-0-0/b2c_add_salesforce_payments_functionality_to_site_genesis.md
canonical_url: https://help.salesforce.com/s/articleView?id=cc.b2c_add_salesforce_payments_functionality_to_site_genesis.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 0e1c3467c2eef04079087a3f47f58fca29dd8bdccbfc60c312dc17490baa93cf
description: With some limitations, add Salesforce Payments to SiteGenesis on your B2C Commerce site.
products:
  - Commerce
  - B2C Commerce
release: "264"
---
# SiteGenesis Configuration for Salesforce Payments

With some limitations, add Salesforce Payments to SiteGenesis on your B2C Commerce site.

Adding Salesforce Payments to your SiteGenesis instance:

- Adds the Salesforce Payments multi-step checkout functionality to the SiteGenesis Checkout page
- Adds PayPal express checkout to the SiteGenesis Checkout page
- Adds Salesforce Payments express checkout to the SiteGenesis cart
- Adds PayPal express checkout to the SiteGenesis mini-cart

To integrate Salesforce Payments with SiteGenesis, you modify the following B2C SiteGenesis instance components.

- **[SiteGenesis Cartridges](https://help.salesforce.com/s/articleView?id=cc.b2c_cartridges.htm&release=264.0.0&type=5)**  
    A cartridge is a mechanism for packaging and deploying program code and data in B2C Commerce. You use cartridges to extend business functionality or integrate with external systems. A cartridge can deliver generic or application-specific functionality.
- **[SiteGenesis Controllers](https://help.salesforce.com/s/articleView?id=cc.b2c_controlers.htm&release=264.0.0&type=5)**  
    Controllers are server-side scripts that handle B2C Commerce storefront requests. Controllers manage the flow of data in your application, and create ViewModels to process each storefront request as a route and generate an appropriate response. For example, in a storefront application, clicking a category menu item or entering a search term triggers a controller that renders a page.
- **[SiteGenesis Models and Views](https://help.salesforce.com/s/articleView?id=cc.b2c_models_and_views.htm&release=264.0.0&type=5)**  
    In B2C Commerce SiteGenesis, the controllers integrate into Models and Views. All scripts are Common JS modules with defined and documented exports to avoid polluting the global namespace.
- **[SiteGenesis Server-Side Scripts](https://help.salesforce.com/s/articleView?id=cc.b2c_server_side_scripts.htm&release=264.0.0&type=5)**  
    Server-side scripts in B2C Commerce SiteGenesis handle client-side requests. All scripts are CommonJA modules with defined exports.
- **[SiteGenesis Client-Side Scripts](https://help.salesforce.com/s/articleView?id=cc.b2c_client_side_scripts.htm&release=264.0.0&type=5)**  
    Client-side js in B2C Commerce SiteGenesis performs functions that don't require information from the server.
- **[SiteGenesis Templates, Forms, and CSS for Salesforce Payments](https://help.salesforce.com/s/articleView?id=cc.b2c_sitegenesis_templates_forms_and_css_for_salesforce_payments.htm&release=264.0.0&type=5)**  
    Developers create Salesforce B2C Commerce storefront pages using Internet Store Markup Language (ISML) templates, CSS, and B2C Commerce forms, resulting in HTML that renders on the browser. Use these technologies to customize the look and feel of your storefront.