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

# Stripe

### Authenticate <a href="#connect" id="connect"></a>

When you're setting up your first workflow with Stripe, you will need to connect Stripe with MESA. Click on the **Connect with Stripe** button.

![Screenshot of a MESA workflow Stripe authentication step. Spotlight the Connect with Stripe button.](https://3425906282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1H6u1HQc3Iew7ATmmiCi%2Fuploads%2FMuYtLzkeZ5VFpU0eeaIW%2FAS-STRIPE-CONNECT.png?alt=media\&token=7f3ff102-aeb1-4179-b1c7-b2f759942ed6)

Afterwards, you will be brought back to your current workflow and you are all set! MESA is now connected with your Stripe account.

### Configuration <a href="#configuring" id="configuring"></a>

#### Configure Stripe Triggers <a href="#triggers" id="triggers"></a>

When using any of Stripe's [triggers](/workflow-builder/triggers.md) (e.g. **Customer Updated**, **Customer Subscription Updated**), you will need to select the necessary variables

![Screenshot of a MESA Stripe trigger configuration, select the necessary variables. Spotlight the variable selection.](https://3425906282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1H6u1HQc3Iew7ATmmiCi%2Fuploads%2FY0dvaTw8wPmGiiRolwHj%2FAS-STRIPE-VARIABLE.png?alt=media\&token=dceb4db5-8316-4d6b-81f4-11a7e5534ba3)

Follow these instructions to set up your webhook in the Stripe Dashboard.

1\. In a new tab on your browser, visit the Stripe Dashboard: <https://dashboard.stripe.com/>

2\. Sign into your account.

3\. On the right hand side of the top navigation, click on **Developers**.

4\. Click on **Webhooks** under the **Developers** heading.

![Screenshot of the Stripe Dashboard top navigation, click Developers then Webhooks. Spotlight the Webhooks option under Developers.](https://3425906282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1H6u1HQc3Iew7ATmmiCi%2Fuploads%2FmTdXJG9daNvDcmlF4eA8%2Fas-stripe-webhooksdevs.png?alt=media\&token=9f2bc9c6-4719-4b23-82d5-8ff467535972)

5\. Click on the **Add an endpoint** button.

![Screenshot of the Stripe Dashboard Webhooks page. Spotlight the Add an endpoint button.](https://3425906282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1H6u1HQc3Iew7ATmmiCi%2Fuploads%2FMc7kijAUkwHPT31yuUtj%2Fas-stripe-addendpoint.png?alt=media\&token=6bc646d0-7172-45c7-8d31-827c62f150b6)

6\. Go back to the tab with your MESA workflow open. Locate your workflow's Stripe trigger and click on the Stripe trigger.

7\. Click on **configure**.

8\. Then, click on the Copy icon next to the **Webhook URL** field.

<figure><img src="https://3425906282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1H6u1HQc3Iew7ATmmiCi%2Fuploads%2FQ88Sl7O6FaBDWb4KFZN2%2Fimage.png?alt=media&amp;token=2f54cd4c-78de-4f19-a0dd-b27c1492d370" alt="Screenshot of a MESA Stripe trigger configuration, click the Copy icon next to the Webhook URL field. Spotlight the Copy icon next to the Webhook URL."><figcaption></figcaption></figure>

9\. Go back to the tab with the Stripe dashboard open. In the **Endpoint URL** field, paste the copied value.

10\. You can leave the **Description** field blank and leave the option **Events on your account** selected, under **Listen to**.

![Screenshot of the Stripe Add an endpoint page, paste the copied value into the Endpoint URL field with Events on your account selected. Spotlight the Endpoint URL field.](https://3425906282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1H6u1HQc3Iew7ATmmiCi%2Fuploads%2FzgIDngftueJPTciyLspr%2Fas-stripe-addwebhook.png?alt=media\&token=c5eea334-2693-4f76-8280-4f8853aa4d40)

11\. Next, click on the **Select Events** button under **Select events to listen to**.

12\. Select the event that is related to your trigger. For example, if your MESA workflow's trigger is **Customer Updated**, then you would select **Customer > customer.updated**

{% hint style="info" %}
Please do not select more than one event for your webhook.
{% endhint %}

13\. Once you have selected your single event for the webhook, click on **Add events**.

<figure><img src="https://3425906282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1H6u1HQc3Iew7ATmmiCi%2Fuploads%2FqZ9ho3GlA9QpTCQv8YS8%2Fas-stripe-addevents.png?alt=media&amp;token=aba874c2-5605-44ad-a6b9-cf3a531ff1c3" alt="Screenshot of the Stripe endpoint event selection, choose the single event related to your trigger. Spotlight the Add events button."><figcaption></figcaption></figure>

14\. Finally, click on the **Add endpoint** button. You are all set for that specific MESA workflow with the Stripe trigger. You will want to do this for every workflow that contains a Stripe trigger.

### Technical Notes

While our Stripe integration has extensive possibilities to achieve your workflow goals, there are a few important things to be aware of.

* Our integration **does not** allow you to use Stripe as a third-party payment provider in Shopify.


---

# 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.getmesa.com/connect/stripe.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.
