Load Stripe data in Python using dltHub

Build a Stripe-to-database or-dataframe pipeline in Python using dlt with automatic Cursor support.

In this guide, we'll set up a complete Stripe data pipeline from API credentials to your first data load in just 10 minutes. You'll end up with a fully declarative Python pipeline based on dlt's REST API connector, like in the partial example code below:

Example code
@dlt.source
def stripe_crypto_onramp_sessions_source(access_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.stripe.com/v1/",
            "auth": {
                "type": "apikey",
                "token": access_token,
            },
        },
        "resources": [
            reports,,tax_ids,,files
            ],
    }
    [...]
    yield from rest_api_resources(config)


def get_data() -> None:
    # Connect to destination
    pipeline = dlt.pipeline(
        pipeline_name='stripe_crypto_onramp_sessions_pipeline',
        destination='duckdb',
        dataset_name='stripe_crypto_onramp_sessions_data', 
    )
    # Load the data
    load_info = pipeline.run(stripe_crypto_onramp_sessions_source())
    print(load_info)

Why use dltHub Workspace with LLM Context to generate Python pipelines?

  • Accelerate pipeline development with AI-native context
  • Debug pipelines, validate schemas and data with the integrated Pipeline Dashboard
  • Build Python notebooks for end users of your data
  • Low maintenance thanks to Schema evolution with type inference, resilience and self documenting REST API connectors. A shallow learning curve makes the pipeline easy to extend by any team member
  • dlt is the tool of choice for Pythonic Iceberg Lakehouses, bringing mature data loading to pythonic Iceberg with or without catalogs

What you’ll do

We’ll show you how to generate a readable and easily maintainable Python script that fetches data from stripe_crypto_onramp_sessions’s API and loads it into Iceberg, DataFrames, files, or a database of your choice. Here are some of the endpoints you can load:

  • Reports: Contains endpoints for generating various reports.
  • Tax IDs: Endpoints for managing tax identification numbers.
  • Files: Endpoints to handle file uploads and management.
  • Cards: Endpoints for managing payment card information.
  • Plans: Endpoints related to subscription plans.
  • Quotes: Endpoints for managing quotes related to payments.
  • Utilities: Various utility endpoints for different functionalities.
  • Tokens: Endpoints for managing tokens used for secure transactions.
  • Events: Endpoints for handling webhook events and notifications.
  • Prices: Endpoints for managing pricing information.
  • Topups: Endpoints related to top-up transactions.

You will then debug the Stripe pipeline using our Pipeline Dashboard tool to ensure it is copying the data correctly, before building a Notebook to explore your data and build reports.

Setup & steps to follow

💡
Before getting started, let's make sure Cursor is set up correctly:

Now you're ready to get started!

  1. ⚙️ Set up dlt Workspace

    Install dlt with duckdb support:

    pip install dlt[workspace]

    Initialize a dlt pipeline with Stripe support.

    dlt init dlthub:stripe_crypto_onramp_sessions duckdb

    The init command will setup the necessary files and folders for the next step.

  2. 🤠 Start LLM-assisted coding

    Here’s a prompt to get you started:

    Prompt
    Please generate a REST API Source for Stripe API, as specified in @stripe_crypto_onramp_sessions-docs.yaml 
Start with endpoints reports and  and skip incremental loading for now. 
Place the code in stripe_crypto_onramp_sessions_pipeline.py and name the pipeline stripe_crypto_onramp_sessions_pipeline. 
If the file exists, use it as a starting point. 
Do not add or modify any other files. 
Use @dlt rest api as a tutorial. 
After adding the endpoints, allow the user to run the pipeline with python stripe_crypto_onramp_sessions_pipeline.py and await further instructions.

  3. 🔒 Set up credentials

    Authentication is handled using an API key, which should be included in the request header as 'Authorization'.

    To get the appropriate API keys, please visit the original source at https://www.stripe.com/. If you want to protect your environment secrets in a production environment, look into setting up credentials with dlt.

  4. 🏃‍♀️ Run the pipeline in the Python terminal in Cursor

    python stripe_crypto_onramp_sessions_pipeline.py

    If your pipeline runs correctly, you’ll see something like the following:

    Pipeline stripe_crypto_onramp_sessions load step completed in 0.26 seconds
1 load package(s) were loaded to destination duckdb and into dataset stripe_crypto_onramp_sessions_data
The duckdb destination used duckdb:/stripe_crypto_onramp_sessions.duckdb location to store data
Load package 1749667187.541553 is LOADED and contains no failed jobs

  5. 📈 Debug your pipeline and data with the Pipeline Dashboard

    Now that you have a running pipeline, you need to make sure it’s correct, so you do not introduce silent failures like misconfigured pagination or incremental loading errors. By launching the dlt Workspace Pipeline Dashboard, you can see various information about the pipeline to enable you to test it. Here you can see:

    • Pipeline overview: State, load metrics
    • Data’s schema: tables, columns, types, hints
    • You can query the data itself
    dlt pipeline stripe_crypto_onramp_sessions_pipeline show --dashboard

  6. 🐍 Build a Notebook with data explorations and reports

    With the pipeline and data partially validated, you can continue with custom data explorations and reports. To get started, paste the snippet below into a new marimo Notebook and ask your LLM to go from there. Jupyter Notebooks and regular Python scripts are supported as well.

    import dlt

data = dlt.pipeline("stripe_crypto_onramp_sessions_pipeline").dataset()
# get eport table as Pandas frame
data.eport.df().head()

Running into errors?

When using Stripe, you must ensure compliance with laws regarding customer payment data. Be aware of the limitations regarding certain payment methods and the requirements for Strong Customer Authentication (SCA). Testing must be thorough before going live, and care should be taken with sensitive information like client secrets. Pay attention to idempotency keys for POST requests to avoid duplicate operations.

Extra resources:

Next steps