> For the complete documentation index, see [llms.txt](https://integrations.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://integrations.impact.com/integration-guides/for-brands/plugin-integrations/subscriptions-and-payments/integrate-with-stripe/integrate-via-the-stripe-app.md).
# Integrate via the Stripe App
1. [Log in](https://marketplace.stripe.com/apps/impactcom-affiliate) to your Stripe account to install the Stripe App.
2. On the *Stripe Apps* page, select **Continue**.
3. Select your account name.
4. Review and confirm your access rights, then select **Install**.
5. Once the app is successfully installed, select **Continue to app settings**.
6. Enter your impact.com *Settings* details.
* Refer to the *impact.com account information reference* below.
7. Select **Save settings** to complete the setup.
#### **impact.com account information reference**
| Account Data | Description |
| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **URL\*** | The URL of the site where your integration will be implemented. |
| **Account SID\*** | In the impact.com platform, from the top navigation bar, select  **\[User profile] → Settings →** [**API**](https://app.impact.com/secure/advertiser/api/fr/api-access-tokens-ui.ihtml) and copy your Account SID. |
| **Auth Token\*** | In the impact.com platform, from the top navigation bar, select  **\[User profile] → Settings →** [**API**](https://app.impact.com/secure/advertiser/api/fr/api-access-tokens-ui.ihtml) and copy your Auth Token. |
| **Program ID\*** | In the impact.com platform, select your brand name in the top-left corner. Your Program ID is the numerical value under the program name.
|
| **Event Type ID\*** | In the impact.com platform, from the top navigation bar, select  **\[User profile] → Settings →** [**Event Types**](https://app.impact.com/secure/advertiser/tracking-settings/actiontracker/view-actiontracker-flow.ihtml). Copy the number in parenthesis next to the name of the event type. |
| **Recurring Tracker ID\*** | Your impact.com recurring subscription Event tracking identifier. In impact.com, navigate to
\[User profile] → Settings → Event Type. This event type must be linked as a child event to your first subscription event type. For help with creating and linking event types, contact support
|
Once you have fully integrated the impact.com API, you can begin end-to-end testing to ensure everything is working properly. Learn how to proceed with [End-to-End Testing](/integration-guides/end-to-end-tests.md).
---
# 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://integrations.impact.com/integration-guides/for-brands/plugin-integrations/subscriptions-and-payments/integrate-with-stripe/integrate-via-the-stripe-app.md?ask=&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.
