Sync real-time Stripe data to Postgres with Stripe Data Pipeline

Many applications keep their own copy of Stripe data, such as a customer's current plan or whether an order was paid, so they can grant access or ship goods without asking Stripe every time. Until now developers built that copy themselves, either by calling Stripe's APIs repeatedly or by running webhook handlers that write each change into their database, and then had to deal with failed or out-of-order events and periodically confirm the copy still matched. Stripe's new real-time sync to Postgres takes over that job (Stripe).

A developer connects a Postgres database, including ones hosted by Supabase, AWS, Neon or Databricks Lakebase, and picks which Stripe tables to sync, with no code. Stripe's Data Pipeline backfills the existing records, sends changes within seconds as they happen in Stripe, and regularly audits the copy against Stripe's own data to fix discrepancies. Data Pipeline already sent Stripe data to data warehouses and cloud storage for analytics and reporting; the new sync instead targets the database an application itself runs on, and Postgres is the first destination to get real-time syncing. It is in public preview and free to start, with Snowflake, BigQuery, Redshift, Databricks and cloud storage listed as coming next. The preview has limits the announcement leaves out: Stripe's documentation says a row can briefly show an earlier state, and updates to some tables, including payment intents, can take up to 10 minutes to arrive.