2025-W22: recent changes to `transactions` + coming changes to `charges`
Recent changes to transactions
transactions(2025-05-28) We recently made 2 changes to the transactions table. This links to deeper re-engineering work at Monta, but also to efforts to make data in the Partner Data Warehouse align more cleanly with the raw data one can query from the API or see in the Hub.
- column
transaction_idis nowid - columns
to_currency_rate_eurandfrom_currency_rate_eurwere removed.
Please contact us, if these changes are causing issues in your setup.
Coming changes to charges table -- June to August 2025
charges table -- June to August 2025Overview of changes and motivation
(2025-05-28) We are redesigning the way our charges table is created. This links to deeper re-engineering work at Monta, but also to efforts to make data in the Partner Data Warehouse align more cleanly with the raw data one can query from the API or see in the Hub.
With these changes, we will replace the charges table and add two new tables charge_pricings and charges_config. Some columns currently in charges will in the future exist in the new tables. The three tables can be joined using charge_id.
COMING IN WEEK 23: Schema pages for the coming tables
Timing of the changes
- before 2025-06-15: New
charges,charge_pricings, andcharges_configtable will appear with theFUTURE__preposition. No changes will be made to the existing table. - 2025-07-15: Existing
chargestable will be renamed withDEPRECATED__preposition. New tables will be available both with and without theFUTURE__preposition allowing preparing your codebase for the future stable state. - 2025-08-15: Tables with the
DEPRECATED__andFUTURE__prepositions are dropped
Some highlighted changes in the charges table
charges tableis_deleted_chargecolumn is removed.- This column is always 0 in the current table, so no data is lost
avg_renewablecolumn is removedstart_source,payment_method,payment_method_typeandstatecolumns have same universe of values but the values have different format- values are in upper case
- values use
_separator instead of-
