What changed
On October 15, 2026, Stripe launched real-time sync to PostgreSQL through Data Pipeline in public preview. Customers select supported API-resource tables, get a historical backfill and receive ongoing changes into an owned PostgreSQL 13+ database. Stripe manages replication and reconciliation rather than requiring teams to build webhook listeners and retry/backfill pipelines. Stripe supports Neon and Supabase OAuth setup and other PostgreSQL providers via credentials. Current pricing includes 5,000 free rows synced per month; additional usage is billed per row according to regional pricing. Most changes arrive in seconds, but certain updates can lag up to ten minutes in preview.
Why it matters
Subscription businesses commonly maintain a local copy of Stripe customers, invoices and subscription states to enforce entitlements and answer application queries. A managed mirror reduces engineering and operational maintenance, but builders must distinguish eventually consistent reporting and account views from synchronous authorisation, fulfilment or irreversible actions. Pricing follows row mutations, not just customer count; updates across multiple tables can increase cost.
From webhook integration to managed data mirror
Data Pipeline now connects directly to a customer-controlled PostgreSQL database and performs both initial backfill and continuous sync. It exposes listable Stripe API resources such as charges, customers, subscriptions, payment intents and invoices, while single-object-only resources such as Balance are not included. Stripe reconciles drift against source records. Unlike warehouse exports, this destination is designed to power application reads.
Seconds for most changes, ten minutes for some
Stripe says most new and updated rows appear within seconds, but the preview documentation explicitly allows up to ten minutes for updates to payment_intents, invoice_items, setup_intents, identity_verification_sessions, topups, quotes and climate_orders, and for creation of checkout_sessions. Do not rely on the mirror alone for time-critical fulfilment, payment finality or access control; retain suitable webhook/API verification paths.
Database ownership and integration boundaries
Teams must provide PostgreSQL 13+ with SSL access. Supabase and Neon support direct OAuth connection; other providers use a dedicated database login, schema and firewall allowances. Stripe recommends separate credentials and warns against modifying Stripe-managed tables. Its sizing guidance suggests roughly 1 GB for every 100,000 charges when syncing all tables, subject to actual data volume.
Pricing is by row mutation, not a flat webhook replacement
Stripe's current pricing page provides 5,000 synced rows free per month, free initial backfill, and usage-based per-row pricing beyond that, with separate charges for warehouse destinations. A row counts on create, update or delete; a multi-field update to one row counts once. The price shown depends on country and billing arrangement; check your Stripe Dashboard and region-specific price before forecasting. Database hosting and storage remain separate costs.