Stripe's new Data Pipeline streams billing data into Postgres
The feature backfills then continuously syncs charges, customers, subscriptions and invoices into a dedicated schema, authenticated with short-lived OAuth tokens rather than a stored database password.
Stripe launched Data Pipeline on 15 October, a feature that syncs Stripe data straight into a Postgres database without a hand-built webhook listener. It is in public preview and free to start using.
Setup happens entirely in the Stripe Dashboard, under Reporting, Data Management, Data Pipeline. You pick Postgres as the destination, Supabase is one of the first providers supported alongside AWS, Neon and Databricks Lakebase, and authenticate through it directly. Stripe creates a dedicated stripe_sdp-prefixed schema with its own scoped role, connects over SSL, and authenticates with short-lived OAuth tokens rather than a stored password. It backfills historical charges, refunds, disputes, customers, subscriptions and invoices, then keeps them continuously in sync, and Stripe says it regularly audits the synced records against its own source data to catch discrepancies. Snowflake, BigQuery, Redshift and cloud storage destinations are coming soon.
Why it matters: this removes the webhook-and-reconciliation layer most teams build by hand just to make billing state queryable. Once synced, subscription status, invoice state and refunds sit in the same database as your application data, so a plan check or a dunning query is a SQL join rather than an API call.
The caveat: it is public preview and Postgres-only for now. Stripe does not publish a sync latency figure, so treat it as near-real-time rather than instant until that is documented.