Skip to main content
Stripe is a technology company that builds economic infrastructure for the internet, primarily focused on payment processing for online businesses. It provides APIs and tools for accepting payments, managing subscriptions, and handling financial transactions securely.

Configuring Stripe as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Stripe option from the list of connectors. Click Next and you’ll be prompted to add your access.

1. Add account access

You’ll need to provide your Stripe API credentials to allow Nekt to access your data. The following configurations are available:
  • Client Secret: Your Stripe secret API key. You can find it in your Stripe Dashboard under Developers > API keys.
  • Account ID: (Optional) Your Stripe account ID. Required when authenticating on behalf of a connected account.
  • Start Date: The earliest date from which records will be synced.
  • Stripe Connect: (Default: false) Enable this if your Stripe account is a platform account that uses Stripe Connect features. When enabled, the following additional streams become available: Connect Accounts, Connect Application Fees, Connect Transfers, and Connect Subaccount Transfers.
  • Credit Balance: (Default: false) Enable this to retrieve Credit Balance data. When enabled, the Credit Balance Summary and Credit Balance Transaction streams become available.
Once you’re done, click Next.

2. Select streams

Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis. You can select entire groups of streams or pick specific ones.
Tip: The stream can be found more easily by typing its name.
Select the streams and click Next.

3. Configure data streams

Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.
  • Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
  • Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
  • Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
  • Sync Type: you can choose between INCREMENTAL and FULL_TABLE.
    • Incremental: every time the extraction happens, we’ll get only the new data - which is good if, for example, you want to keep every record ever fetched.
    • Full table: every time the extraction happens, we’ll get the current state of the data - which is good if, for example, you don’t want to have deleted data in your catalog.
Once you are done configuring, click Next.

4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can define some additional settings:
  • Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here.
  • Determine when to execute an Additional Full Sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while.
Once you are ready, click Next to finalize the setup.

5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your Catalog, you need at least one successful source run.

Streams and Fields

Below you’ll find all available data streams from Stripe and their corresponding fields:
Stream for managing customer profiles and their associated data.
Stream for retrieving tax identification numbers associated with a customer. This stream is a child of Customers and requires the Customers stream to be enabled.
Stream for managing recurring subscription data, including billing cycles, statuses, and associated items.
Stream for individual line items within subscriptions. This stream is a child of Subscriptions and requires the Subscriptions stream to be enabled.
Stream for managing the lifecycle of subscriptions through multiple phases, allowing for future pricing changes and plan transitions.
Stream for billing invoices generated for subscriptions and one-time charges.
Stream for individual line items within invoices. This stream is a child of Invoices and requires the Invoices stream to be enabled.
Stream for pending invoice items that haven’t yet been included in an invoice.
Stream for payment attempts, both successful and failed. Each charge represents a single attempt to move money into your Stripe account.
Stream for payment intents, which represent the full lifecycle of a payment from creation to completion.
Stream for all transactions that have contributed to or will contribute to the Stripe account balance.
Stream for products and services offered for sale.
Stream for pricing configurations for products. A product can have multiple prices for different billing intervals or currencies.
Stream for discount coupons that can be applied to customers or subscriptions.
Stream for shareable promotion codes that customers can apply when checking out.
Stream for billing credit grants issued to customers. Available when Credit Balance is enabled in the source configuration.
Stream for the current credit balance summary for each customer. This is a child of Customers and only available when Credit Balance is enabled in the source configuration.
Stream for individual transactions that affect a customer’s credit balance. This is a child of Customers and only available when Credit Balance is enabled in the source configuration.
Stream for connected accounts on a Stripe Connect platform. Only available when Stripe Connect is enabled in the source configuration.
Stream for transfers made to connected accounts. Only available when Stripe Connect is enabled.
Stream for fees collected from connected accounts on your platform. Only available when Stripe Connect is enabled.
Stream for transfers between the platform account and connected subaccounts. Only available when Stripe Connect is enabled.
Stream for all Stripe events, representing every change that occurs on your account. Useful for auditing and building event-driven workflows.
The events stream can only bring historical data from the last 30 days.

Data Model

The following diagram illustrates the relationships between the core data streams in Stripe. The arrows indicate the join keys that link the different entities, providing a clear overview of the data structure.

Use Cases for Data Analysis

This guide outlines valuable business intelligence use cases when consolidating Stripe data, along with ready-to-use SQL queries that you can run on Explorer.

1. Monthly Revenue Overview

Track your monthly recurring and one-time revenue using invoice and charge data. Business Value:
  • Monitor revenue trends over time
  • Identify periods of growth or decline
  • Compare paid vs. outstanding invoices

2. Subscription Churn Analysis

Identify subscription cancellations and churn trends to understand customer retention. Business Value:
  • Track monthly churn rates
  • Identify high-churn periods
  • Understand cancellation reasons to improve retention
  • Monitor trial conversion rates

Implementation Notes

Data Quality Considerations

  • All monetary amounts are provided in the smallest currency unit (e.g., cents for USD). Divide by 100 to get the standard value in queries.
  • Incremental sync uses the updated_at field for most streams. Use created for Balance Transactions.
  • Some streams (Subscription Items, Invoice Line Items, Customer Tax IDs) are children of parent streams and require the parent stream to be enabled.

Optional Features

  • The Connect streams are only available when Stripe Connect is enabled in the source configuration. Enable this if you manage a marketplace or platform using Stripe Connect.
  • The Credit Balance streams are only available when Credit Balance is enabled in the source configuration.

API Limits & Performance

  • The connector optimizes API interactions by caching and reusing connections, ensuring efficient data extraction especially for accounts with many subaccounts or high data volumes.
  • Selecting all streams can increase extraction times significantly.
  • For faster extractions, select only the streams necessary for your analysis.
  • Parent-child stream pairs (e.g., Invoices + Invoice Line Items) require both to be selected if you need the child data.

Skills for agents

Download Stripe skills file

Stripe connector documentation as plain markdown, for use in AI agent contexts.