Which Stripe API key should I use?

A restricted key with **Read** permission on the resources you plan to export is enough. Grant read access to Customers in any case, because Renta verifies the key by reading the customer list. The secret key of the account also works.

Why are the amounts 100 times larger than in the Stripe Dashboard?

Stripe reports amounts in the smallest currency unit, and Renta loads them as is: 1999 means 19.99 in a currency with two decimal places. Divide by 100 in your queries. Zero-decimal currencies such as JPY need no division.

Can I export test mode data?

Yes. The pipeline loads the data of the mode the key belongs to: a test key exports test records, a live key exports live ones. The Livemode field shows which mode a record comes from.

How do I convert the Created field into a readable date?

Stripe timestamps arrive as Unix seconds. In BigQuery, use TIMESTAMP_SECONDS(created) . The Created Date parameter is the ready-made date version of the same field.

Stripe

Renta exports Stripe data to your data warehouse: charges, invoices, subscriptions, customers, payouts, and other objects of your account.

Authentication

Renta connects to Stripe with an API key: either the secret key of your account or a restricted key. You create the key in the Stripe Dashboard under Developers > API keys and paste it into the connection form.

For a restricted key, grant Read permission to every resource you plan to export. Read access to Customers is required in any case: Renta verifies the key by reading the customer list when you save the connection. If the key cannot read the resource behind the selected report type, the run stops with a permission error.

Connect Stripe source

Follow these steps to add Stripe as a source in Renta using your API key.

Go to the CatalogStep 1

Navigate to the Connections > Catalog section in the left sidebar.
Open the Finance category and click the Stripe card.

Stripe card in the Finance category of the Renta catalog

Fill in the connection formStep 2

Source name.
A display name for this connection. It is used exclusively in the Renta interface.
API key.
Paste your Stripe secret or restricted key.

Add a new Stripe connection page with the Source name and API key fields

Save the connectionStep 3

Check the Source name.
Click Save.

Renta verifies the key with Stripe before saving the connection, so an invalid key, or a restricted key without read access to Customers, fails right on this step.

Stripe connection setup with the source name filled in and the Save button

Source createdStep 4

The new source appears in the Sources list with the Active status. You can now use it in pipelines.

Sources list with the new Stripe source in the Active status

Create a pipeline

Once the source is connected, create a pipeline to sync your Stripe data into your destination.

Create a Stripe pipeline

Link your Stripe source to a destination and configure the pipeline.

Select Stripe as the sourceStep 1

In the left sidebar, click New pipeline. On the Source step, select Stripe under Already connected and click Next step.

Select a source step with Stripe under Already connected

Select your Stripe connectionStep 2

Choose the Stripe connection you created earlier and click Next step. The card shows the name of the connection and the date it was added.

Select your Stripe connection step with the connection card and its creation date

Select a destinationStep 3

On the Destination step, select your destination (for example, Google BigQuery) and click Next step.

Select a destination step with Google BigQuery under Already connected

Select the destination connectionStep 4

Choose the destination connection you want to load data into and click Next step. The card shows the dataset and project the data will land in.

Select your Google BigQuery connection step with the dataset and project identifiers on the card

Pipeline configuration

On the final step, choose the report type, pick its fields, and set the date range and the schedule.

Report type

Select which Stripe object the pipeline exports. One pipeline loads one report type.

Report type	Description
Balance Transactions	Every movement of your Stripe balance: charges, refunds, transfers, payouts, and Stripe fees, with the gross amount, the fee and its breakdown, and the net amount. Amounts of deductions are negative.
Charges	Payments with their amount, status, and currency, card and billing details, the risk outcome, receipt links, and the identifiers of the customer, invoice, and payment intent.
Coupons	Discount coupons: a fixed amount or a percent off, duration, redemption limits, and validity.
Credit Notes	Credit notes issued against invoices: totals, reason, status, the credited lines, and the linked refunds.
Customers	Customers with their email, name, currency, account balance, delinquency flag, invoice settings, and your metadata.
Disputes	Disputed charges with the contested amount, reason, status, and the state of the evidence.
Invoice Line Items	Individual lines of invoices: amount, currency, quantity, billing period, and the identifiers of the price and subscription.
Invoices	Invoices with their totals, the amounts due, paid, and remaining, status, billing reason, collection method, and the timestamps of status changes.
Payment Intents	Payment intents with their amount, status, available payment method types, cancellation reason, and the details of the last payment error.
Payouts	Payouts to your bank account or card: amount, currency, status, method, and arrival date.
Plans	Billing plans of the legacy subscription model: amount, currency, billing interval, and usage type.
Prices	Prices of your products: unit amount, currency, billing scheme, and the recurring interval.
Products	The product catalog: name, description, active flag, images, and attributes.
Refunds	Refunds with their amount, currency, status, reason, and the identifiers of the charge and payment intent.
Subscriptions	Subscriptions with their status, billing period, trial dates, cancellation details, and the subscription items with the attached prices.

Parameters

Select the Stripe fields to include in the destination table.

Each field lists its destination column name right under it. Select All checks the full set, and the Selected tab shows the result.

The set of available fields depends on the report type. Created Date is a date column that Renta derives from the creation timestamp: the destination table is partitioned by it, and incremental loading works only when it is selected.

Stripe reports monetary amounts in the smallest currency unit, and Renta loads them as is: a charge of $19.99 arrives as 1999. Timestamps such as Created arrive as Unix seconds. Created Date is the only ready-made date column.

Fields that reference another Stripe object hold its identifier: the Customer field of a charge is the customer ID. To get the attributes of the related object, create a pipeline for its report type and join the tables by ID. Nested objects arrive flattened into separate columns prefixed with the parent name, such as the billing details and payment method details of a charge.

Fields that hold a list of values load as nested records.

Report type	Fields that load as nested records
Balance Transactions	Fee Details
Credit Notes	Lines, Refunds
Invoices	Custom Fields
Subscriptions	Items

The Metadata field, along with Fraud Details on charges and Evidence Details on disputes, arrives as a JSON string. The keys inside Metadata are the ones you set in Stripe, so extract them with the JSON functions of your warehouse.

Table name

Name the pipeline and the destination table.

Integration name.
The name of the pipeline. It is used exclusively in the Renta interface.
Table name.
The destination table name. You can keep the auto-generated name or enter your own.

Date range

Set the period the pipeline covers. Renta selects records by their creation date in Stripe.

Date start.
The first date of the period.
Date end.
The last date of the period. Keep Today so that the end of the period advances with every run.

A run loads the records created before the start of the run day (UTC). Records created during the day arrive with the next run.

For Invoice Line Items, the period applies to the invoices: Renta loads the lines of the invoices created within the period.

Schedule

Choose how often the pipeline runs.

Schedule type	Description
Manual	The pipeline runs only when triggered manually through the interface or via API.
Daily	The pipeline runs once a day at the specified update time.
Interval	The pipeline runs at specified time intervals.
Cron Expression	The pipeline runs on a schedule defined by a cron expression.

For Daily schedules, set the Update time, the exact time each run starts, then click Create pipeline.

Update time selection and the Create pipeline button

Renta also supports API triggers and integration with external orchestrators such as Apache Airflow, Dagster, and Prefect. See the full scheduling documentation for details.

The new pipeline appears in the Pipelines section under the ETL tab, where you can track its runs, progress, and the destination table name.

Pipelines list with the new Stripe integration in the Completed status

Sync strategy

How Renta synchronizes a Stripe report type depends on whether the Created Date parameter is selected.

Strategy	Supported report types	Description
Incremental	Balance Transactions, Charges, Coupons, Credit Notes, Customers, Disputes, Invoices, Payment Intents, Payouts, Plans, Prices, Products, Refunds, Subscriptions (with the Created Date parameter selected)	The destination table is partitioned by the day of record creation. Renta selects records by creation date, so each run picks up the records created since the previous run and replaces only the daily partitions it touches. The first run loads the whole configured date range.
Full reload	Invoice Line Items, and the report types above when the Created Date parameter is not selected	Renta reads the entire configured date range on every run and replaces the contents of the destination table. Invoice line items carry no creation date of their own, so this report type always works this way.

Because Renta selects records by creation date, changes to already loaded records stay out of the table: a charge whose status changed after it was loaded keeps the old status in the warehouse. If the current state matters more than loading speed, create the pipeline without Created Date: every run then re-reads the whole period.

Renta keeps within the Stripe API rate limits, so the first run over several years of history takes noticeably longer than the daily increments. Invoice Line Items is the slowest report type, because Stripe returns line items invoice by invoice.

Frequently asked questions

Ready to get started?

Build your data pipeline today or get a personalized demo. Start free!

Need help?

Get expert support to ensure your project succeeds. We're here to help!

Feature requests?

Help shape our product! Share your ideas for new features and integrations.