Skip to main content Skip to complementary content
Already have an account? Sign in

Stripe (v1)

Last updated: 9/15/2026

Stripe integration summary

Stitch’s Stripe integration replicates data using the Stripe REST API. Refer to the Schema section for a list of objects available for replication.

Stripe feature snapshot

A high-level look at Stitch's Stripe (v1) integration, including release status, useful links, and the features supported in Stitch.

STITCH
Release status

Deprecated on June 20, 2022

Supported by

Stitch

Stitch plan

Standard

API availability

Not available

Singer GitHub repository

singer-io/tap-stripe

REPLICATION SETTINGS
Anchor Scheduling

Supported

Advanced Scheduling

Supported

Table-level reset

Unsupported

Configurable Replication Methods

Unsupported

DATA SELECTION
Table selection

Supported

Column selection

Supported

Select all

Supported

TRANSPARENCY
Extraction Logs

Supported

Loading Reports

Supported

Connecting Stripe

Stripe setup requirements

To set up Stripe in Stitch, you need:

  • Administrator permissions in Stripe. This is required to grant Stitch access to Stripe.

Step 1: Add Stripe as a Stitch data source

  1. Sign into your Stitch account.
  2. On the Stitch Dashboard page, click the Add Integration button.

  3. Click the Stripe icon.

  4. Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.

    For example, the name “Stitch Stripe” would create a schema called stitch_stripe in the destination. Note: Schema names cannot be changed after you save the integration.

Step 2: Define the historical replication start date

The Sync Historical Data setting defines the starting date for your Stripe integration. This means that data equal to or newer than this date will be replicated to your data warehouse.

Change this setting if you want to replicate data beyond Stripe’s default setting of 1 year. For a detailed look at historical replication jobs, check out the Syncing Historical SaaS Data guide.

Step 3: Create a replication schedule

In the Replication Frequency section, you’ll create the integration’s replication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.

Stripe integrations support the following replication scheduling methods:

To keep your row usage low, consider setting the integration to replicate less frequently. See the Understanding and Reducing Your Row Usage guide for tips on reducing your usage.

Step 4: Authorize Stitch to access Stripe

  1. Next, you’ll be prompted to sign into your Stripe account.
  2. A screen explaining what you’re authorizing will display. Note: Stitch will only ever read your Stripe data, and cannot create charges or any other records in Stripe.
  3. Click Sign in with Stripe to connect.
  4. Sign into your Stripe account.
  5. After the authorization process is successfully completed, you’ll be directed back to Stitch.
  6. Click All Done.

Step 5: Set objects to replicate

The last step is to select the tables and columns you want to replicate. Learn about the available tables for this integration.

Note: If a replication job is currently in progress, new selections won’t be used until the next job starts.

For Stripe integrations, you can select:

  1. Individual tables and columns

  2. All tables and columns

Click the tabs to view instructions for each selection method.

  1. In the integration’s Tables to Replicate tab, locate a table you want to replicate.
  2. To track a table, click the checkbox next to the table’s name. A blue checkmark means the table is set to replicate.

  3. To track a column, click the checkbox next to the column’s name. A blue checkmark means the column is set to replicate.

  4. Repeat this process for all the tables and columns you want to replicate.
  5. When finished, click the Finalize Your Selections button at the bottom of the screen to save your selections.
  1. Click into the integration from the Stitch Dashboard page.
  2. Click the Tables to Replicate tab.

  3. In the list of tables, click the box next to the Table Names column.
  4. In the menu that displays, click Track all Tables and Fields:

    The Track all Tables and Fields menu in the Tables to Replicate tab
    The Track all Tables and Fields menu in the Tables to Replicate tab

  5. Click the Finalize Your Selections button at the bottom of the page to save your data selections.

Initial and historical replication jobs

After you finish setting up Stripe, its Sync Status may show as Pending on either the Stitch Dashboard or in the Integration Details page.

For a new integration, a Pending status indicates that Stitch is in the process of scheduling the initial replication job for the integration. This may take some time to complete.

Free historical data loads

The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.

Stripe replication

Events table replication

Stripe will only provide 30 days of historical event data for the events table. Refer the the Stripe docs for more information about the events table.

Objects and events

In the Stripe API, there are two concepts:

  • Objects, which are items like charges, invoices, customers, etc.
  • Events, which are changes to objects. For example: An invoice being created, or its status going from draft to open.

Whenever an object is created or updated in Stripe, a corresponding event is created. Because Stripe creates and updates object records in this way, there are two types of tables in Stitch’s Stripe integration:

  • A table for events, which contains all events that have occurred for Stripe’s supported event types. This table acts as a history for an object record, showing how it has been changed over time.
  • Tables for objects, which contains the latest version of records. These are tables like customers, charges, invoices, etc.

Note: Updates based on events is only applicable to the type of object the event is for. For example: If a dispute object is updated, only the corresponding record in the disputes table will be updated. The related charge in the charges table will not be updated. To retrieve related data for different objects, you’ll need to use the events table. Refer to Stripe’s documentation for info about event types and the objects they describe.

Example event and object data replication over time

In the image below is an example of how records for the events and invoices tables will look as an invoice changes over time. Click the image to enlarge.

Example showing how event and invoice records are replicated as an invoice changes over time
Example showing how event and invoice records are replicated as an invoice changes over time

Stripe table reference

balance_transactions

The balance_transactions table contains info about transactions have have contributed to your Stripe account balance, including charges, transfers, etc.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

created

Useful links

Stripe documentation

balance_transactions schema on GitHub

Stripe API method

charges

The charges table contains info about charges to credit and debit cards.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

created

Useful links

Stripe documentation

charges schema on GitHub

Stripe API method

coupons

The coupons table contains info about percent or amount-off discounts that may be applied to a customer. Note: Coupons only apply to invoices; they don’t apply to one-off charges.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

created

Useful links

Stripe documentation

coupons schema on GitHub

Stripe API method

customers

The customers table contains info about your customers.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

created

Useful links

Stripe documentation

customers schema on GitHub

Stripe API method

disputes

This table contains information about customer disputes related to charges on their credit card.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

created

Useful links

Stripe documentation

disputes schema on GitHub

Stripe API method

events

The events table contains info about events. When an event occurs, a new event object is created. This table acts as the history of an object, allowing you to see how it has changed over time.

For example: When an invoice is created, an invoice.created event is created. When the draft invoice is finalized and updated to be open, an invoice.finalized event is created. When the invoice is sent to the customer, an invoice.sent event is created.

For more info about this table and how data is replicated, refer to the Replication section. Additionally, refer to Stripe’s documentation for info about event types and the objects they describe.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

created

Useful links

Stripe documentation

events schema on GitHub

Stripe API method

invoice_items

The invoice_items table contains info about items contained in customer invoices.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

date

Useful links

invoice_items schema on GitHub

Stripe API method

invoice_line_items

The invoice_line_items table contains info about the line items contained in invoices.

Note: In order to replicate invoice line item data, the invoices table must also be set to replicate.

Invoice line item replication

To replicate invoice line items, Stitch will use the Replication Key of the corresponding invoice in the invoices table to detect new and updated records. This means that any time an invoice is updated, its associated line items will also be replicated.

For example: An invoice with five line items is updated when its status changes from draft to open. The record in invoices will be replicated, as will the records for its five line items. In this example, a total of six records will be replicated.

Replication Method

Key-based Incremental

Primary Keys

invoice

id

Useful links

Stripe documentation

invoice_line_items schema on GitHub

Stripe API method

invoices

The invoices table contains info about invoices. Invoices are statements of amounts owed by customers, which can be one-off charges or generated periodically from a subscription.

Invoice line items

Full records for the line items associated with an invoice can be found in the invoice_line_items table. To replicate these records, you must set this table and the invoice_line_items table to replicate.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

date

Useful links

Stripe documentation

invoices schema on GitHub

Stripe API method

payout_transactions

This table contains info about payout transactions.

Replication Method

Full Table

Primary Key

id

Useful links

Stripe documentation

payout_transactions schema on GitHub

Stripe API method

payouts

The payouts table contains info about payouts, which occur when you receive funds from Stripe or initiate a payout to a bank account of the debit card of a connected Stripe account.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

created

Useful links

Stripe documentation

payouts schema on GitHub

Stripe API method

plans

The plans table contains info about the plans in your Stripe account. A plan defines the base price, currency, and billing cycle for subscriptions.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

created

Useful links

Stripe documentation

plans schema on GitHub

Stripe API method

products

The products table contains info about the products in your Stripe account.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

updated

Useful links

Stripe documentation

products schema on GitHub

Stripe API method

subscription_items

The subscription_items table contains info about subscription items. In Stripe, subscription items are used to create customer subscriptions with more than one plan.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

created

Useful links

Stripe documentation

subscription_items schema on GitHub

Stripe API method

subscriptions

The subscriptions table contains info about subscriptions, which allow you to charge a customer on a recurring basis. A subscription ties a customer to a particular plan.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

created

Useful links

Stripe documentation

subscriptions schema on GitHub

Stripe API method

transfers

The transfers table contains info about transfers sent to connected accounts.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

created

Useful links

transfers schema on GitHub

Stripe API method

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!