# Stripe

![2560px-Stripe_Logo__revised_2016.svg.png](https://assets.relyanceuat.xyz/images/docs/34563383860237/34563415125133.png)
Stripe is a developer-oriented commerce company helping small and large companies accept web and mobile payments.

In order to integrate Stripe with Relyance AI you will need an API key.

#### **In Stripe:**

![stripe_API_Key_page.png](https://assets.relyanceuat.xyz/images/docs/34563383860237/34563415125389.png)
1. Login to your Stripe account and click **Developers** on the bottom left > open **[API keys](https://dashboard.stripe.com/test/apikeys)** page.
2. Click **+ Create restricted key** button under **Restricted keys** section > select **Building your own integration**> this opens up the **Create restricted API key** page.
3. In the **Key Name** field of the above page, enter a meaningful name (e.g. Relyance Scan).
4. In the same page, setup the following permissions for the API Key,
    - Under **All core resources** section enable **Read** permission for the following resources,
        - **Charges**
        - **Customers**
        - **Disputes**
        - **PaymentIntents**
        - **PaymentMethods**
    - Under **All Checkout resources** section enable **Read** permission for the resource,
        - **Checkout** **Sessions**
    - Under **All Billing resources** section enable **Read** permission for the following resources,
        - **Credit** **notes**
    - Enable **Read** permission for the section **All Connect resources**
    - Under **All Issuing resources** section enable **Read** permission for the following resources,
        - **Authorizations**
        - **Cardholders**
    - Under **Radar** section enable Read permission for the resource
        - **Reviews**
5. Click on **Create Key** button on the bottom right.
6. Copy and save the **TOKEN** value in a secure location as this needs to be used as the **API Key** in the following steps.

![stripe_Create_API_Key.png](https://assets.relyanceuat.xyz/images/docs/34563383860237/34563415125773.png)

![stripe_create_key.png](https://assets.relyanceuat.xyz/images/docs/34563383860237/34563415126413.png)

#### **In the Relyance AI application:**

1. Login to your Relyance AI account.
2. Navigate to the **Settings** (bottom-left corner).
3. Select **Integrations**.
4. Search and locate the **Stripe** integration card and click on it.
5. Click on the **Add Connection** button on the top right.
6. Provide a meaningful name for the integration and click on the **Add** button.
7. In the **Overview** section, select the integration features you wish to enable for the integration, review the **Scope and Permission**, and **Endpoint** details and click on **Continue**. For more details, see[Integration Features](/docs/introduction-to-relyance-ai/integration-features/).
8. In the **Connection** section, provide the appropriate values and click on **Continue**,
    - **Connection Name**: This property allows you to update the integration specified in Step 6. If you have multiple integrations for the same vendor, you may want to assign distinct names to each. This helps streamline filtering by **Discovery Source** across the **Inventory**, **Visual** **Maps**, **Assets**, and **Data Flow Analysis** pages.
    - **Rescan Frequency**: This property allows you to configure how often Relyance executes scans against this Vendor connection.
    - **Business Atlas Associations** (required): the business entities or products that newly discovered third parties, services and assets from this integration are attributed to. Choose at least one from the **Select Associations** dropdown — the wizard will not advance past this step without one. For more details, see [Business Atlas](/docs/other-settings/business-atlas-overview/).
9. In the **Authentication** section, provide the **API Key** information retrieved from the **Stripe** section and click on **Continue**.
10. This step applies only if the **Data Inspection** check box was enabled in Step 7. In the Data Inspection section, provide the appropriate values and click on **Continue**,
    - **Minimum Confidence Level:** This property adjusts the sensitivity of the Data Inspection feature. Lower likelihoods (e.g., unlikely) offer more coverage but may produce false positives, while higher sensitivity (e.g., very likely) provides greater accuracy but less coverage.
11. Review the configuration summary from the **Completion** section and click on **Finish.**
12. Confirm the integration Status reflects **Connected.**

![Screenshot](https://assets.relyanceuat.xyz/images/docs/34563383860237/34643556811405.png)

![Screenshot](https://assets.relyanceuat.xyz/images/docs/34563383860237/34563383858829.png)

![Screenshot](https://assets.relyanceuat.xyz/images/docs/34563383860237/34563415127181.png)

![Screenshot](https://assets.relyanceuat.xyz/images/docs/34563383860237/34563383859213.png)

![Screenshot](https://assets.relyanceuat.xyz/images/docs/34563383860237/34563383859597.png)

![Screenshot](https://assets.relyanceuat.xyz/images/docs/34563383860237/34684152496269.png)

<!-- terraform-examples:begin (generated from the integration catalog; do not hand-edit) -->

## Manage this integration with Terraform

Connections for this integration can be managed as code with the [Relyance Terraform provider](https://registry.terraform.io/providers/Relyance/relyance/latest). Non-secret fields go in `auth.params`; secret fields go in `auth.secrets_wo`, which is write-only — never stored in Terraform state. Rotate secrets by bumping `auth.secrets_wo_version`.

```hcl
resource "relyance_integration_connection" "stripe" {
  vendor = "stripe"
  name   = "<your connection name>"

  auth = {
    method = "api-key"
    params = {
      data_storage_location = "us"
    }
    # Secret fields are write-only: sent to Relyance, never stored in state.
    secrets_wo = {
      API_KEY = var.stripe_api_key
    }
    secrets_wo_version = 1
  }

  scans = { "data-inspection" = { enabled = true } }
}
```

<!-- terraform-examples:end -->