How to Sync Billing Data to Prisma Postgres (Stripe, QuickBooks, Xero & Paddle)

Prisma Postgres is a billing-friendly option for syncing data from Stripe, QuickBooks, Xero or Paddle. Unlike most usage-priced databases that charge based on query duration, Prisma Postgres bills per operation, making it a cost-effective choice for scheduled batch syncs. SaaS companies typically deal with thousands of billing records, not millions, and these records change slowly, making Prisma Postgres an ideal fit.

To set up Prisma Postgres, you'll need to create a database in the Prisma Console. Choose a region, which can be difficult to change later, and you may consider creating a separate database for billing data due to schema drift risks. When generating a connection string, there are two options: pooled and direct. The pooled string is recommended as it allows for longer connections and is specifically designed for background workers like scheduled syncs.

Each credential used generates a new set of access permissions, so it's advised to generate a separate credential for Codeless Sync.

When connecting Prisma Postgres to Codeless Sync, create a new sync configuration and choose your billing provider. For most providers, you'll need an API key, with the exception of Stripe and Paddle, which require restricted keys. QuickBooks and Xero use OAuth, so you won't handle any tokens yourself. Once connected, auto-create a table to store the synced data, name the configuration, and run the sync. The table names follow a predictable pattern: provider_name_data_type.

The cost of a batch sync is a small number of operations rather than a per-row charge. For instance, a sync of 375 Stripe payment_intents cost only 15 operations. This makes Prisma Postgres an efficient solution for syncing billing data from providers like Stripe, QuickBooks, Xero or Paddle to your database.