> 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/getting-started/starter-kits/stripe/installation.md).

# Installation

Installing the UmbCheckout Stripe Starter Kit

The UmbCheckout Stripe Starter Kit makes use of [dotnet templates](https://learn.microsoft.com/en-us/dotnet/core/tools/custom-templates) and is installed using the NuGet package manager using the below command:

```
dotnet new install UmbCheckout.StarterKit.Stripe
```

Once installed you will need to create a new folder on your machine, within this folder you will need to open a command prompt, terminal, or PowerShell and run the following:

```
dotnet new umbcheckout.starterkit.stripe
```

Once installed you need to run the following command to build and run the site:

```
dotnet run
```

Next is to install Umbraco in the normal way following the prompts within the installer.

On the first run of the site after the installer has completed uSync will import all of the demo content, images, and configurations.

Next, you are required to configure the [UmbracoApplicationUrl](https://docs.umbraco.com/umbraco-cms/reference/configuration/webroutingsettings#umbraco-application-url) within the [Web routing settings](https://docs.umbraco.com/umbraco-cms/reference/configuration/webroutingsettings) within your appsettings.json file

```json
"Umbraco": {
  "CMS": {
    "WebRouting": {
      "UmbracoApplicationUrl": "http://www.mysite.com/"
    }
  }
}
```

The final step is to add your [Stripe API keys](/v17/payment-providers/payment-providers/stripe/configuration.md), for example with user secrets:

```
dotnet user-secrets set "UmbCheckout:Stripe:Test:ApiKey" "sk_test_..."
dotnet user-secrets set "UmbCheckout:Stripe:Test:WebHookSecret" "whsec_..."
```


---

# 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/getting-started/starter-kits/stripe/installation.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.