Stripe Data Reaches Postgres in Seconds, and Webhooks Won't Disappear Because of It

Databricks' Stripe Data Pipeline now supports real-time sync to Lakebase Postgres. Data such as Stripe customers, subscriptions, invoices, and charges lands in this Postgres database within seconds. Applications no longer need to wait for batch processing or call the Stripe API on every page load.

For teams that have used Stripe, this scenario is familiar. Stripe handles payments, Databricks handles data analytics and AI, and Lakebase is Databricks' serverless Postgres database aimed at applications and AI agents. Now the same Stripe pipeline can send data to two places: Unity Catalog for analytics, and Lakebase for applications to query real-time state. The Databricks blog post was published by Carlota Soto, and it says Stripe manages the sync end to end, with OpenSharing under the hood.

One Pipeline, Two Destinations

On the analytics side, Delta Sharing places data such as payments, customers, subscriptions, refunds, and payouts into Unity Catalog, where it can be used as ordinary tables. On the application side, data such as payments, customers, and subscriptions is continuously synced to Lakebase, with updates arriving within seconds. The two destinations serve different workloads: one looks for patterns across thousands of customers and weeks of history, while the other decides, at request time, what to show users and what permissions to grant.

The Cost of Webhooks Is Not in Receiving Events

There are usually two traditional approaches. Calling the Stripe API works for low volume, but as traffic grows, rate limits and operations become more troublesome. With webhooks, you have to write a handler for every event, handle failed retries, and separately reconcile missed or out-of-order events. The really hard part comes after receiving events: making sure the table in your database is trustworthy. When sync fails, users may get incorrect permissions or see stale invoices.

Stripe Data Pipeline takes over this layer. You select the Stripe tables to sync, and Stripe handles historical backfill, continuous delivery, and data auditing without requiring code. Applications query the latest data in Lakebase using SQL. The Databricks blog lists several typical use cases: unlocking features within seconds after a subscription upgrade; promptly revoking permissions after a cancellation or failed renewal; showing recently paid invoices and cards that need updating on the account page; building real-time financial dashboards with charges, refunds, and payouts; and offering retention discounts after a user cancels, or prompting an upgrade when usage exceeds the plan.

How to Get Started

This real-time sync to Postgres capability is now in public preview and free to get started. Create a pipeline in the Stripe Dashboard; for detailed steps, see the Stripe documentation. The Lakebase entry point is in the Databricks documentation, and the original post is on the Databricks blog.

Public preview also means that businesses with high reconciliation and audit requirements still need to confirm data integrity and permission boundaries themselves. Webhooks will not disappear because of this; complex business events, internal system integrations, and data flows outside Stripe still need to be connected by you. What this update saves is the work of repeatedly maintaining a sync pipeline; complex integration logic still has to be written by you.