Connector

Collect Stripe balance transactions in AWS Redshift

Load Stripe balance transactions and payouts into your own AWS Redshift cluster with a custom OWOX connector. Every movement keeps its gross, fee and net, so revenue after Stripe's cut is a query, not an estimate.

StripeConnectedBalance transact…ChargesCustomersDisputes
Data MartPublishedone definition
AWS RedshiftIdAccou…Livem…Daily 09:00
Refreshed on a schedule. No exports, no copy-paste.

Get started free

Endpoints

Stripe Endpoints

Documentation

14 Stripe endpoints you can import. Each lands in its own table in your data warehouse.

S00 · Why

Why bring balance transactions next to payouts and the bank

Balance transactions are the ledger behind every Stripe payout: the gross, the fee and the net of each movement. Matching payouts to the bank statement is only possible when both sit in one data warehouse.

  • Compute revenue after Stripe's fees from gross and fee
  • Set payouts by arrival date beside the gross, fee and net of the period
  • Reconcile with the bank statement in the same query
StripeLedger, fees, net
BankStatement lines
AccountingLedger
Your data warehouseAWS RedshiftStripeBankLedgerJoined by idCharge takenPayout arrivesOne query shows what reached the balance and what was paid out.

S01 · Step 1

Step 1: Connect Stripe and pick the fields

Create a Data Mart, choose Stripe as the data source and add a restricted API key with read access. Open an endpoint and tick only the fields you need.

  • Balance transactions carries gross, fee, net, type and reporting category
  • A custom connector: the restricted API key is yours
New Data MartChoose a sourceShopifyStripeGoogle AdsAuthorizeConnectedEndpointBalance transacti…ChargesCustomersDisputes
Balance transacti…16 fieldscreatedamountfeenetcurrencyreporting_category

S02 · Step 2

Step 2: Load Stripe into AWS Redshift

Each endpoint becomes its own table, and refresh settings are set in the Data Mart. Run it and the first load lands as a table in a schema of your own AWS Redshift cluster or workgroup. The location is pre-filled from your data storage, and you can change it.

  • Balance transactions and payouts each get their own table in the Redshift schema
  • Every run is logged in Run History
DestinationAWS RedshiftSchemastripeTablebalance_transactionsRun
Run HistoryPendingRunningSuccessIncremental load
Tablestripe.balance_transactions

S03 · Step 3

Step 3: Get a business-friendly Stripe output schema

After the first run you get the output schema: every field with its type and a description. amount, fee and net are in the smallest currency unit, and the schema says so.

  • net is amount minus fee, so no rounding is invented
  • source names the charge, refund or payout that caused the movement
stripe.balance_transactionsOutput schemaFieldDescriptioncreatedWhen Stripe created the object…amountGross amount of the transaction…feeStripe fees taken on this…netAmount after fees in the…currencyThree-letter ISO currency code…reporting_categoryStripe's reporting category…

S04 · Step 4

Step 4: Keep the Stripe tables linked

Balance transactions, payouts and refunds stay separate tables, joined by balance transaction id. Together they become the reconciliation part of one Stripe data model.

  • A payout names its own balance transaction
  • A refund names the balance transaction that carried it
Balance transacti…idnetfee
Payoutsbalance_transact…arrival_datestatus
Refundsbalance_transact…amountreason

S05 · Step 5

Step 5: Schedule the Stripe refresh and backfill history

Set it once. A daily scheduled refresh keeps the ledger current, and a manual backfill loads earlier periods.

  • Daily runs with no pipeline to maintain
  • Backfill the ledger for the periods under reconciliation
ScheduleRun on a scheduleDaily 09:00
BackfillRun backfill
Run HistoryDaily scheduleManual backfillDaily schedule

S06 · Step 6

Step 6: Reuse the same Stripe table everywhere

One table feeds your data model, spreadsheets, dashboards, AI assistants and scheduled insights in Slack or email.

  • Define net revenue once
  • Every report reads the same table
StripeData MartPublished
Your data model
Google Sheets
Data Studio dashboards
Claude, ChatGPT
Slack, email

Recent updates

Why OWOX

Why OWOX for Stripe in AWS Redshift

The Stripe dashboard shows balance and payouts. OWOX puts the ledger behind them in your own AWS Redshift, ready to reconcile.

  • You own the data. It lands in your own data warehouse, in tables you control.
  • Gross, fee and net. Every movement keeps all three, so revenue after Stripe's cut is a column.
  • Built to extend. As a custom connector it can gain fields without a vendor roadmap.
  • Built to extend. Add a field or an endpoint in the builder when the account needs it.

Book a callGet started free

Trust

The Data Partner You Can Trust

users

176K Source: Internal OWOX data as of 2026-10-02

Executives and data analysts across 20+ industries

G2 rating

4.9★2

“A trusted data analytics partner” — verified review

npm installs

165K3

In Open Source We Trust

Customers