Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
| 1 | ## How do I set up custom OAuth credentials for Stripe? |
| 2 | |
| 3 | Use your own Stripe Connect OAuth app when you want users to see your platform's name on the consent screen and control the credentials yourself. If you only need to connect your own Stripe account, an API key is simpler; see the next question. |
| 4 | |
| 5 | ### Create the Stripe OAuth app |
| 6 | |
| 7 | 1. In the [Stripe Dashboard](https://dashboard.stripe.com/), go to **Settings** → **Connect**. |
| 8 | 2. Under **Integration settings**, click **+ Add Integration** and fill in the form: |
| 9 | - **Name**: something recognizable, for example `Composio-Integration`. |
| 10 | - **Redirect URL**: `https://backend.composio.dev/api/v1/auth-apps/add`. It must use `https`, have no trailing slash, and exactly match the `oauth_redirect_uri` field in your Composio auth config. |
| 11 | - **Website**, **Privacy Policy**, and **EULA** are optional. |
| 12 | 3. Save the integration and copy the **Client ID** (starts with `ca_`). |
| 13 | 4. For the client secret, Stripe Connect OAuth uses your platform account's secret API key. Copy it from **Developers** → **API keys** (`sk_live_`, or `sk_test_` in test mode). |
| 14 | |
| 15 | ### Create the auth config in Composio |
| 16 | |
| 17 | 1. In the Composio dashboard, go to **Auth Configs**, click **Create Auth Config**, and select **Stripe**. |
| 18 | |
| 19 |  |
| 20 | |
| 21 |  |
| 22 | 2. Set the authentication type to **OAuth2** and choose **Use your own developer authentication**. |
| 23 | |
| 24 |  |
| 25 | 3. Paste the **Client ID** and the secret key as the **Client Secret**, then click **Create Stripe Auth Config**. |
| 26 | 4. Click **Connect Account**, approve access in Stripe, and confirm the account shows as **Active**. |
| 27 | |
| 28 | See [Custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow. |
| 29 | |
| 30 | ### Scopes |
| 31 | |
| 32 | Stripe OAuth has two scopes: `read_only` and `read_write`. The default auth config requests `read_write`. Use `read_only` if your tools only read data. |
| 33 | |
| 34 | ## How do I connect Stripe with an API key? |
| 35 | |
| 36 | 1. In the [Stripe Dashboard](https://dashboard.stripe.com/apikeys), go to **Developers** → **API keys**. |
| 37 | 2. Under **Standard keys**, copy the **Secret key**. It starts with `sk_live_`, or `sk_test_` in test mode. Don't use the publishable `pk_` key. |
| 38 | |
| 39 |  |
| 40 | 3. In Composio, go to **Auth Configs**, click **Create Auth Config**, select **Stripe**, and choose **API Key** as the authentication type. Click **Create Stripe Auth Config**. |
| 41 | |
| 42 |  |
| 43 | 4. Click **Connect Account**, paste the secret key, and confirm the account shows as **Active**. |
| 44 | |
| 45 | Keep the secret key out of client-side code. |
| 46 | |
| 47 | ## Why is my Stripe trigger enabled but not receiving events? |
| 48 | |
| 49 | One possible cause is that the Stripe webhook destination was deleted in Stripe while the trigger still appears enabled. In that state, the trigger can look active, but Stripe has no active destination to send matching events to. |
| 50 | |
| 51 | Check the Stripe Dashboard for the webhook destination associated with the trigger. If it is missing or disabled, recreate the trigger so the Stripe webhook destination is created again, then verify new Stripe events are delivered. |