> For the complete documentation index, see [llms.txt](https://docs.umbcheckout.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbcheckout.net/v17/configuration/configuration-options.md).

# Configuration Options

There are a number of settings which can be configured within the backoffice on the configuration screen found here:

Settings -> UmbCheckout -> Configuration

Only users with access to the Settings section can see or change it. The screen also shows a **Help & Support** box and, on the right, the **License Details** (see [Licensing](/v17/getting-started/licensing.md)).

The configuration options and their possible options are as below:

| Name                           | Type    | Options                                                                                                                                                                                        |
| ------------------------------ | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Fallback Currency Code         | Text    | The 3-letter ISO currency code used when neither the product's currency node nor the site root sets `umbCheckoutCurrencyCode` (see [Currency](/v17/getting-started/configuration.md#currency)) |
| Success Page URL               | Picker  | Select either a content node or enter an external URL                                                                                                                                          |
| Cancel Page URL                | Picker  | Select either a content node or enter an external URL                                                                                                                                          |
| Enable Shipping                | Boolean | <p><strong>True:</strong> The shipping rates are passed to the payment provider<br><br><strong>False:</strong> No shipping rates are passed to the payment provider</p>                        |
| \*Store Basket In a Cookie     | Boolean | <p><strong>True:</strong> A cookie is set which stores the users current Basket<br><br><strong>False:</strong> No cookie is set</p>                                                            |
| \*Basket Expiry (Cookie)       | Integer | The number of days in the future the cookie expires (30 by default)                                                                                                                            |
| \*Store Basket In The Database | Boolean | <p><strong>True:</strong> The users current Basket is stored in the database<br><br><strong>False:</strong> The Basket is not stored</p>                                                       |
| \*Basket Expiry (Database)     | Integer | The maximum number of days the Basket is stored in the database                                                                                                                                |

{% hint style="info" %}
Features marked with \* require a paid license. Without one, they aren't shown and are always off.
{% endhint %}

{% hint style="warning" %}
The screen shows a warning while `Umbraco:CMS:WebRouting:UmbracoApplicationUrl` isn't set. Licensing and the success page need it (see [Installing a License](/v17/getting-started/installation.md#installing-a-license)).
{% endhint %}

Storing the Basket in the database also turns on storing it in a cookie: the cookie is how a returning visitor's Basket is found again. A Basket is stored in the database only when **Store Basket In The Database** is on, and viewing it doesn't extend its expiry.

Saving shows a success toast. If a [Saving notification handler](/v17/core-services/extending-umbcheckout.md) refuses the change, nothing is saved and the toast shows the handler's message.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.umbcheckout.net/v17/configuration/configuration-options.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.