v0.15.1 dbt_stripe_source

PR #98 includes the following update:

Under the Hood

• Removed trailing spaces from YML files to ensure clean documentation and proper compilation.
• Updated conditions in .github/workflows/auto-release.yml.
• Added .github/workflows/generate-docs.yml.
• Added +docs: show: False to integration_tests/dbt_project.yml.
• Migrated flags (e.g., send_anonymous_usage_stats, use_colors) from sample.profiles.yml to integration_tests/dbt_project.yml.
• Updated maintainer_pull_request_template.md with improved checklist.
• Updated .gitignore to exclude additional DBT, Python, and system artifacts.

Full Changelog: v0.15.0...v0.15.1

v0.15.0 dbt_stripe_source

PR #96 includes the following updates:

Breaking Change for dbt Core < 1.9.6

Note: This is not relevant to Fivetran Quickstart users.

Migrated freshness from a top-level source property to a source config in alignment with recent updates from dbt Core. This will resolve the following deprecation warning that users running dbt >= 1.9.6 may have received:

[WARNING]: Deprecated functionality
Found `freshness` as a top-level property of `stripe` in file
`models/src_stripe.yml`. The `freshness` top-level property should be moved
into the `config` of `stripe`.

IMPORTANT: Users running dbt Core < 1.9.6 will not be able to utilize freshness tests in this release or any subsequent releases, as older versions of dbt will not recognize freshness as a source config and therefore not run the tests.

If you are using dbt Core < 1.9.6 and want to continue running Stripe freshness tests, please elect one of the following options:

1. (Recommended) Upgrade to dbt Core >= 1.9.6
2. Do not upgrade your installed version of the stripe_source package. Pin your dependency on v0.14.2 in your packages.yml file.
3. Utilize a dbt override to overwrite the package's stripe source and apply freshness via the previous release top-level property route. This will require you to copy and paste the entirety of the previous release src_stripe.yml file and add an overrides: stripe_source property.

Under the Hood

• Updates to ensure integration tests use latest version of dbt.

Full Changelog: v0.14.2...v0.15.0

v0.14.2 dbt_stripe_source

Under the Hood

• Prepends materialized configs in the package's dbt_project.yml file with + to improve compatibility with the newer versions of dbt-core starting with v1.10.0. (PR #92)
• Updates the package maintainer pull request template. (PR #93)

Contributors

• @b-per (PR #92)

Full Changelog: v0.14.1...v0.14.2

v0.14.1 dbt_stripe_source

PR #91 includes the following updates:

Bug Fixes

• Fixed a Snowflake error in the does_table_exist macro that could occur when another package using quoted table or column names runs concurrently.
• Updated the following models to dynamically select the correct source based on available tables:
  • stg_stripe__price_plan_tmp
  • stg_stripe__subscription_tmp

Under the Hood

• Improved the does_table_exist macro:
  • Added a dispatch to prevent conflicts with macros of the same name in other packages.
  • Updated logic to return 'exists' only when the table is present, replacing 'True'/'False' string outputs. This prevents Jinja from misinterpreting them as truthy values and ensures reliable variable configuration based on exact 'exists' matching.

Full Changelog: v0.14.0...v0.14.1

v0.14.0 dbt_stripe_source

PR #89 includes the following updates:

Breaking Changes

• In alignment with the Fivetran Stripe connector March 2025 update, added:
  • Source:
    • PAYOUT_BALANCE_TRANSACTION
  • Models:
    • stg_stripe__payout_balance_transaction
    • stg_stripe__payout_balance_transaction_tmp
• This is a new mapping table that provides all associated balance transactions for a payout, supporting the 1:many payout → balance_transaction relationship.
  • NOTE: The existing balance_transaction_id in PAYOUT only reflects the most recent associated record, necessitating this update.

Documentation

• Added definitions for new fields and models.

Under the Hood (Maintainers Only)

• Added macro get_payout_balance_transaction_columns.
• Added seed payout_balance_transaction_data.

Full Changelog: v0.13.0...v0.14.0

v0.13.0 dbt_stripe_source

PR #87 includes the following updates:

Feature Updates: Optionally Convert Amounts to Major Units

Stripe passes amount-based fields, such as amount, net, and fee, in the smallest denomination as raw form. This means, if your currency has minor and major units such as USD, 100 represents 100 cents, the minor unit, or 1 USD, the major unit. Alternatively, if your currency doesn't use minor units such as JPY, 100 represents 100 JPY.

• This PR introduces a variable stripe__convert_values (false by default) which allows users the option to divide all amount-based fields by 100.
  • For information on how to enable the division, refer to the README on configuring the stripe__convert_values variable.
  • Otherwise, amount-based fields will be brought through in their raw form.
  • Examples of currencies using minor units (in which enabling stripe__convert_values is relevant) include United States Dollar (USD), Euro (EUR), and the Canadian Dollar (CAD).
  • Examples of currencies NOT using minor units (in which it makes more sense to keep the amount-based fields in raw form) include Japanese Yen (JPY), Indonesian Rupiah (IDR), and Korean Won (KRW).

Under the Hood

• Introduces the convert_values macro which contains the logic for enabling the division by 100, referenced by all amount-based fields.
• Updates the run_models.sh script to test for when stripe__convert_values is set to True.

Notes

• This update is not providing multiple currency support; however, we're interested in exploring this functionality if there's a need. As such, we have created a feature request to support multiple currencies where you are welcome to provide feedback or contribute to the discussion.

Documentation

• Updates the descriptions for all amount-based fields to specify the grain of the values and add information about the stripe__convert_values variable.
• Corrected references to connectors and connections in the README. (#88)

Full Changelog: v0.12.1...v0.13.0

v0.12.1 dbt_stripe_source

Feature Updates

• Declaration of passthrough variables for the stg_stripe__card model. This can, for example, be used to pull in non-standard columns from Stripe such as description, iin and issuer. See the README for more details (PR #81).

# dbt_project.yml

vars:
  stripe_source:
    card_pass_through_columns:
      - name: "description"
      - name: "iin"
      - name: "issuer"
        alias: "card_issuer"  # optional: define an alias for the column 
        transform_sql: "cast(card_issuer as string)" # optional: apply transformation to column. must reference the alias if provided

Under the Hood

• Removed un-used columns from the get_card_columns() macro and aliased the metadata field, which is parsed via the stripe__card_metadata variable, but not included as a field in its entirety in stg_stripe__card by default (PR #83).
  • This ensures users can utilize the new card_pass_through_columns variable to include these fields in stg_stripe__card.

Contributors

• @bramrodenburg (#81)

Full Changelog: v0.12.0...v0.12.1

v0.12.0 dbt_stripe_source

[PR #77] includes the following updates:

Feature Updates

• Addition of the following new staging models and accompanying upstream references:
  • stg_stripe__discount (required for downstream dbt_stripe model transformations)
  • stg_stripe__product (enabled by default, but can be disabled by setting the stripe__using_subscriptions variable to false)

Full Changelog: v0.11.1...v0.12.0

v0.11.1 dbt_stripe_source

[PR #74] includes the following updates:

Bug Fix

• Removes the unique_invoice_line_item_id uniqueness test in stg_stripe__invoice_line_item. This is because unique_invoice_line_item_id (unique_id in the raw source invoice_line_item table) was part of an older version of Stripe that was brought forth to help migrate internal references. See the Stripe API update for more information. The Fivetran connector persists this in order to resolve the pagination break issue for invoice line items that was introduced by the API update.
  • Furthermore the column definition for unique_invoice_line_item_id (unique_id in the raw source invoice_line_item table) has been made more specific:

    "A unique id generated and only for old invoice line item ID's from a past version of the API. The introduction of this field resolves the pagination break issue for invoice line items, which was introduced by the Stripe API update."

Full Changelog: v0.11.0...v0.11.1

v0.11.0 dbt_stripe_source

PR #72 includes the following updates:

🚨 Breaking Changes 🚨

• No longer filters out deleted customers in stg_stripe__customer.
  • Persists is_deleted field to differentiate between deleted and active customers.
  • Note that this is a 🚨 breaking change 🚨, as previously filtered-out records will appear in stg_stripe__customer (and the downstream transform stripe__customer_overview model).

Feature Updates

• Adds the phone column to stg_stripe__customer.

Under the Hood

• Included auto-releaser GitHub Actions workflow to automate future releases.
• Updated the maintainer PR template to resemble the most up to date format.

Full Changelog: v0.10.0...v0.11.0