> For the complete documentation index, see [llms.txt](https://docs.n8n.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.n8n.io/integrations/builtin/credentials/stripe.md).

# Stripe credentials

You can use these credentials to authenticate the following nodes:

* [Stripe Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.stripetrigger.md)
* [Stripe](/integrations/builtin/app-nodes/n8n-nodes-base.stripe.md)

## Supported authentication methods <a href="#supported-authentication-methods" id="supported-authentication-methods"></a>

* Secret key

You'll also need a Stripe **Signature Secret** or endpoint secret, which is a unique key for each webhook endpoint used to verify incoming requests, ensuring they truly came from Stripe.

## Related resources <a href="#related-resources" id="related-resources"></a>

To configure this credential, you'll need a Stripe admin or developer account. Refer to [Stripe's API documentation](https://docs.stripe.com/api) for more information about the service.

Before you generate an API key, decide whether to generate it in live mode or test mode. Refer to [Test mode and live mode](#test-mode-and-live-mode) for more information about the two modes.

### Live mode Secret key <a href="#live-mode-secret-key" id="live-mode-secret-key"></a>

To generate a Secret key in live mode:

1. Open the [Stripe developer dashboard](https://dashboard.stripe.com/developers) and select [**API Keys**](https://dashboard.stripe.com/apikeys).
2. In the **Standard Keys** section, select **Create secret key**.
3. Enter a **Key name**, like `n8n integration`.
4. Select **Create**. The new API key displays.
5. Copy the key and enter it in your n8n credential as the **Secret Key**.

Refer to Stripe's [Create a secret API key](https://docs.stripe.com/keys#create-api-secret-key) for more information.

### Test mode Secret key <a href="#test-mode-secret-key" id="test-mode-secret-key"></a>

To use a Secret key in test mode, you must copy the existing one:

1. Go to your [Stripe test mode developer dashboard](https://dashboard.stripe.com/test/developers) and select [**API Keys**](https://dashboard.stripe.com/test/apikeys).
2. In the **Standard Keys** section, select **Reveal test key** for the **Secret key**.
3. Copy the key and enter it in your n8n credential as the **Secret Key**.

Refer to Stripe's [Create a secret API key](https://docs.stripe.com/keys#create-api-secret-key) for more information.

## Test mode and live mode <a href="#test-mode-and-live-mode" id="test-mode-and-live-mode"></a>

All Stripe API requests happen within either [test mode](https://docs.stripe.com/test-mode) or live mode. Each mode has its own API key.

Use test mode to access simulated test data and live mode to access actual account data. Objects in one mode aren’t accessible to the other.

Refer to [API keys | Test mode versus live mode](https://docs.stripe.com/keys#test-live-modes) for more information about what's available in each mode and guidance on when to use each.

{% hint style="info" %}
**n8n credentials for both modes**

If you want to work with both live mode and test mode keys, store each mode's key in a separate n8n credential.
{% endhint %}

## Key prefixes <a href="#key-prefixes" id="key-prefixes"></a>

Stripes' Secret keys always begin with `sk_`:

* Live keys begin with `sk_live_`.
* Test keys begin with `sk_test_`.

n8n hasn't tested these credentials with Restricted keys (prefixed `rk_`).

{% hint style="warning" %}
**Publishable keys**

Don't use the Publishable keys (prefixed `pk_`) with your n8n credential.
{% endhint %}


---

# 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.n8n.io/integrations/builtin/credentials/stripe.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.