Stripe to Postgres

This page provides you with instructions on how to extract data from Stripe and load it into PostgreSQL. (If this manual process sounds onerous, check out Stitch, which can do all the heavy lifting for you in just a few clicks.)

What is Stripe?

Stripe is a software-as-a-service (SaaS) platform that lets businesses accept payments online and in mobile apps.

What is PostgreSQL?

PostgreSQL, known by most simply as Postgres, is a hugely popular object-relational database management system (ORDBMS). It labels itself as "the world's most advanced open source database," and for good reason. The platform, despite being available for free via an open source license, offers enterprise-grade features including a strong emphasis on extensibility and standards compliance.

It runs on all major operating systems, including Linux, Unix, and Windows. It is fully ACID-compliant, has full support for foreign keys, joins, views, triggers, and stored procedures (in multiple languages). Postgres is often the best tool for the job as a back-end database for web systems and software tools, and cloud-based deployments are offered by most major cloud vendors. Its syntax also forms the basis for querying Amazon Redshift, which makes migration between the two systems relatively painless and makes Postgres a good "first step" for developers who may later expand into Redshift's data warehouse platform.

Getting data out of Stripe

You can get data off of Stripe's servers using the Stripe REST API, which exposes information about core resources, payment methods, subscriptions, and more. To get a list of all customers, for instance, you could call GET /v1/customers.

Sample Stripe data

The Stripe API returns JSON-formatted data. Data from a call to retrieve customers might look like this.

{
  "object": "list",
  "url": "/v1/customers",
  "has_more": false,
  "data": [
    {
      "id": "cus_BykTW2x4M6Yrrt",
      "object": "customer",
      "account_balance": 0,
      "created": 1513697132,
      "currency": "usd",
      "default_source": null,
      "delinquent": false,
      "description": null,
      "discount": null,
      "email": null,
      "livemode": false,
      "metadata": {
      },
      "shipping": null,
      "sources": {
        "object": "list",
        "data": [
    
        ],
        "has_more": false,
        "total_count": 0,
        "url": "/v1/customers/cus_BykTW2x4M6Yrrt/sources"
      },
      "subscriptions": {
        "object": "list",
        "data": [
    
        ],
        "has_more": false,
        "total_count": 0,
        "url": "/v1/customers/cus_BykTW2x4M6Yrrt/subscriptions"
      }
    },
    {...},
    {...}
  ]
}

Preparing Stripe data

Now you need to parse the JSON in the API response and map each column to a corresponding field in a table in the destination database. You'll have to know the datatypes for each field. The Stitch Stripe Docs can give you a sense of what datatypes will come through the API.

Loading data into Postgres

Once you have identified all of the columns you will want to insert, you can use the CREATE TABLE statement in Postgres to create a table that can receive all of this data. Then, Postgres offers a number of methods for loading in data, and the best method varies depending on the quantity of data you have and the regularity with which you plan to load it.

For simple, day-to-day data insertion, running INSERT queries against the database directly are the standard SQL method for getting data added. Documentation on INSERT queries and their bretheren can be found in the Postgres documentation here.

For bulk insertions of data, which you will likely want to conduct if you have a high volume of data to load, other tools exist as well. This is where the COPY command becomes quite useful, as it allows you to load large sets of data into Postgres without needing to run a series of INSERT statements. Documentation can be found here.

The Postgres documentation also provides a helpful overall guide for conducting fast data inserts, populating your database, and avoiding common pitfalls in the process. You can find it here.

Keeping Stripe data up to date

So, now what? You've built a script that pulls data from Stripe and loads it to your destination, but what happens tomorrow when you have hundreds of new transactions?

The key is to build your script in such a way that it can also identify incremental updates to your data. Thankfully, Stripe's API results include fields like "created" that allow you to identify records that are new since your last update (or since the newest record you've copied). Once you've taken new transactions into account, you can set up your script as a cron job or continuous loop to keep pulling down new data as it appears.

Other data warehouse options

PostgreSQL is great, but sometimes you need to optimize for different things when you're choosing a data warehouse. Some folks choose to go with Amazon Redshift, Google BigQuery, or Snowflake, which are RDBMSes that use similar SQL syntax, or Panoply, which works with Redshift instances. If you're interested in seeing the relevant steps for loading data into one of these platforms, check out To Redshift, To BigQuery, To Snowflake, and To Panoply.

Easier and faster alternatives

If all this sounds a bit overwhelming, don’t be alarmed. If you have all the skills necessary to go through this process, chances are building and maintaining a script like this isn’t a very high-leverage use of your time.

Thankfully, products like Stitch were built to solve this problem automatically. With just a few clicks, Stitch starts extracting your Stripe data via the API, structuring it in a way that is optimized for analysis, and inserting that data into your PostgreSQL data warehouse.