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

# Connect the Stripe App

> Install Biqli in Stripe, connect a workspace, and manage the connection safely.

The Biqli Stripe App connects one Stripe account and environment to one Biqli workspace. After your website registers an attributed Stripe Checkout Session, the app turns supported Stripe events into Biqli trials, sales, renewals, and refunds.

The managed app does not require you to copy a Stripe secret key into Biqli. Stripe grants the app read-only access to the payment resources it needs, and Biqli uses signed events to process conversions.

## Before you connect

You need all of the following:

* owner access to the Biqli workspace;
* permission to install and authorize apps in the Stripe account;
* conversion tracking enabled in that workspace;
* at least one allowed website hostname and an active Biqli publishable key;
* the Biqli browser SDK on the website that starts Stripe Checkout;
* a conversion-enabled Biqli link for the campaign you want to test.

<Note>
  A Stripe administrator installs and connects the app. A Biqli workspace owner manages or disconnects the workspace authorization.
</Note>

## Install and connect

<Steps>
  <Step title="Open the official install link">
    In Biqli, open **Workspace settings → Integrations → Stripe** and select **Enable**. Use only the install link shown by Biqli.
  </Step>

  <Step title="Choose the intended Stripe environment">
    Confirm the Stripe account and whether you are installing in live mode, test mode, or a sandbox. These environments are isolated from one another.
  </Step>

  <Step title="Review Stripe permissions">
    Stripe shows read-only access for account information, Checkout Sessions, invoices, subscriptions, events, and charges and refunds. Install the app only if the displayed app is **Biqli** by **Biqli LLC**.
  </Step>

  <Step title="Connect a Biqli workspace">
    Open **Biqli** from the Stripe sidebar and select **Connect Biqli workspace**. Sign in to Biqli if needed, review the authorization screen, choose the workspace, and approve access.
  </Step>

  <Step title="Confirm both sides">
    Stripe should show **Connected**, the chosen workspace, the Stripe account name, and the current environment. In Biqli, the Stripe integration action changes from **Enable** to **Manage**.
  </Step>
</Steps>

If Biqli asks for an email verification code after you sign in from a new browser or private window, enter the code. Biqli returns you to the pending authorization request. If the browser discarded the private session, reopen **Connect Biqli workspace** from Stripe and approve the same workspace.

## Understand the permissions

The app requests only the Stripe resources used by the conversion pipeline:

| Permission                   | Why Biqli needs it                                                                                  |
| :--------------------------- | :-------------------------------------------------------------------------------------------------- |
| Account and user information | Bind the signed app request to the correct Stripe account and authorized administrator.             |
| Checkout Sessions            | Read the completed Checkout object and its payment, customer, subscription, and invoice references. |
| Invoices                     | Record paid subscription invoices and recurring renewals.                                           |
| Subscriptions                | Detect attributed free trials and preserve the subscription relationship for future invoices.       |
| Charges and refunds          | Match a refund to its original attributed sale.                                                     |
| Events                       | Receive only the selected lifecycle and conversion events.                                          |
| External access              | Call Biqli's connection API from the Stripe App interface.                                          |

These permissions are read-only. Biqli does not create charges, issue refunds, change subscriptions, or transfer money.

## Environment rules

Treat every Stripe environment as a separate connection:

| Environment | Stripe data                                | Recommended use                                           |
| :---------- | :----------------------------------------- | :-------------------------------------------------------- |
| Sandbox     | Isolated sandbox objects and test payments | Development and repeatable lifecycle testing              |
| Test mode   | Test objects in a Stripe account           | Prelaunch testing when your account uses Stripe test mode |
| Live mode   | Real customers and payments                | Production attribution after sandbox validation           |

A `cs_test_...` Checkout Session cannot be registered against a live connection. A `cs_live_...` session cannot be registered against a test or sandbox connection.

One Stripe account in one environment can have only one active Biqli workspace connection. A workspace can list multiple Stripe connections when you intentionally connect different accounts or environments.

## Manage an existing connection

Open **Workspace settings → Integrations → Stripe** and select **Manage**. Biqli shows each active connection, including:

* Stripe account name and masked account identifier;
* live, test, or sandbox mode;
* who connected it;
* the most recent event or connection time.

Workspace members can see that Stripe is connected. Only the workspace owner can disconnect it.

## Disconnect versus uninstall

These actions have different effects:

* **Disconnect in Biqli** revokes the app's authorization for that workspace and stops new Stripe attribution for that connection. Existing clicks, customers, leads, sales, and refund records remain in reports.
* **Uninstall in Stripe** removes the app from the Stripe account. Use Stripe's app settings when you no longer want the app installed.

For a complete removal, disconnect in Biqli and uninstall in Stripe. If Stripe sends a deauthorization event first, Biqli also revokes the workspace mapping automatically.

## Next steps

Connecting the app alone does not create conversions. Your site must preserve the Biqli click and register each Stripe Checkout Session before redirecting the customer.

* Read [Implement Stripe attribution](/developers/integrations/stripe/checkout) for the website flow.
* Read [Understand Stripe conversions](/help/links/integrations/stripe/conversions) for report behavior.
* Read [Troubleshoot the Stripe App](/help/links/integrations/stripe/troubleshooting) when a conversion is missing.