> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tess.im/llms.txt
> Use this file to discover all available pages before exploring further.

# Stripe

> Connect Stripe to Tess to look up customers, payments, and billing context from chat and agents.

The **Stripe** connector integrates Tess with Stripe. Once connected, the AI can help consult customers, payments, and billing-related context inside chats and agents, within the permissions of the connected Stripe account.

Stripe is part of the Tess [Connectors](/en/connectors) ecosystem and uses **OAuth** authentication for Apps connectors.

## Prerequisites

<Info>
  * Access to a Stripe account with the data you need.
  * Permission to authorize the Stripe connection for that account.
</Info>

## How to connect

<Tip>
  On some Apps connectors, the OAuth consent screen may show a third-party connection bridge name rather than Tess. That is normal—review the requested permissions and continue if they match what you expect.
</Tip>

<Steps>
  <Step title="Open the Connectors panel">
    In chat, click the **+** next to the message box and select **Connectors**.
    You can also manage connectors while editing an agent in Agent Studio.

    <Frame>
      <img src="https://mintlify.s3.us-west-1.amazonaws.com/tess-dfe1edf0/images/connectors/stripe/01-connect-panel.png" alt="PRINT: (Connectors panel with Stripe highlighted and the Connect button visible)" />
    </Frame>
  </Step>

  <Step title="Find Stripe and click Connect">
    Under **Apps**, locate **Stripe** and click **Connect** to start authentication.

    <Frame>
      <img src="https://mintlify.s3.us-west-1.amazonaws.com/tess-dfe1edf0/images/connectors/stripe/02-oauth-consent.png" alt="PRINT: (Provider authorization / consent screen for Stripe)" />
    </Frame>
  </Step>

  <Step title="Authorize access">
    Sign in with the account you want to use and review the requested permissions before confirming.
  </Step>

  <Step title="Confirm it is active">
    Back in Tess, **Stripe** should appear under **Connected**, ready for chats and agents.

    <Frame>
      <img src="https://mintlify.s3.us-west-1.amazonaws.com/tess-dfe1edf0/images/connectors/stripe/03-connected.png" alt="PRINT: (Tess callback or Connectors list showing Stripe as Connected with a success state)" />
    </Frame>
  </Step>
</Steps>

## What you can do

* **Look up customers and payment status** for support or finance routines
* **Summarize billing context** around invoices, subscriptions, or recent charges when available
* **Support operational follow-ups** with clearer payment signals
* **Help teams answer billing questions faster** without leaving Tess
* **Keep sensitive actions cautious** by asking for confirmation before changes

## Example prompts

> 1. Find the Stripe customer for Ana Silva and summarize her latest payment status.
> 2. Which open invoices are overdue by more than 7 days?
> 3. Summarize subscription changes from the last 24 hours.
> 4. Draft a support reply explaining a failed card charge for customer cus\_123.

## Best practices

* Prefer customer IDs, emails, or invoice IDs when you have them.
* Ask for confirmation before refunds or subscription changes.
* In agents, define whether Stripe is for lookup, reporting, or billing actions.

## Troubleshooting

<AccordionGroup>
  <Accordion icon="circle-question" title="Authorization fails">
    Reconnect with a Stripe account/user that can access the needed mode (test/live) and data.
  </Accordion>

  <Accordion icon="circle-question" title="401 / connection dropped">
    Reconnect Stripe in Connectors after key/permission changes.
  </Accordion>

  <Accordion icon="circle-question" title="Customer or invoice not found">
    Confirm you are looking in the correct Stripe account/mode and that the connected user can access that object.
  </Accordion>
</AccordionGroup>

<Note>
  Tess uses the permissions of the connected account. It does not expand access beyond what that account can already do.

  Connectors involve access to external systems. Only connect accounts that fit the usage context, and review permissions carefully.
</Note>