> For the complete documentation index, see [llms.txt](https://docs.digitalriver.com/salesforce-b2b/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalriver.com/salesforce-b2b/1.0-5/introduction/before-you-begin.md).

# Before you begin

Familiarity with Salesforce will help when integrating the Salesforce B2B Commerce App with Salesforce.

Salesforce has several sandboxes. When you integrate Digital River with the Salesforce B2B Commerce App, you need to complete the instructions provided here for each Salesforce Org (production, sandbox, UAT (user acceptance testing), or FULL), and each Digital River site within a Salesforce Org. You can link your developer sandbox to one Digital River site.

## Integration points

### 1. Tax estimations

1. The app extends the global extension point `ccrz.cc_hk_TaxCalculation`.
2. The extension creates a Digital River cart based on the Salesforce B2B Commerce cart with product information, prices, and quantity. This cart is serialized as a JSON object, encrypted, and posted to a Digital River web service.
3. The response contains the cart tax amount.

### 2. Payment processing

You can integrate payment in multiple locations and flows.

#### **During checkout**

In the standard checkout flow, you can apply the payment against the order using one of the following methods:

* Credit Card
* PayPal
* Purchase Order
* Previously stored payment method

#### **My Wallet page**

* You can add new payment methods and update existing payment methods.
* Only credit card payment methods support saved payment options.

### 3. Disclosures

Digital River requires that you display certain disclosures and related links on the checkout pages and shopper notifications (transactional emails). You can use [DigitalRiver object](https://docs.digitalriver.com/digital-river-api/payments/payment-integrations-1/digitalriver.js/reference/digitalriver-object) provided by [DigitalRiver.js](https://docs.digitalriver.com/digital-river-api/payments/payment-integrations-1/digitalriver.js) to create various disclosures, Terms of Sale, warranty information, and California Privacy Rights required by Digital River.

### 4. Selling entities <a href="#id-4-selling-entities" id="id-4-selling-entities"></a>

The Salesforce B2B Commerce App relies on the Hosted Commerce platform via the Commerce API. See [Selling entities](https://docs.digitalriver.com/digital-river-api/integration-options/checkouts/creating-checkouts/selling-entities) for more information.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.digitalriver.com/salesforce-b2b/1.0-5/introduction/before-you-begin.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.