Connector Improvement: Adding Stripe Reporting Report Connector
AnsweredThe card_payments_fees.transaction_level.2 financial report available via the Stripe Reporting API includes data that has been requested by one of our internal teams. The underlying data does not appear to be available in the existing Stripe data model provided by Fortran.
Is adding a report like this within the scope of what Fivetran expects to provide? Is this an improvement that could be added? If so, is there an estimate on when such an improvement might be made?
Our accounting teams likely need this data available by July, so I'm trying to assess whether we should write our own API client for this report or if it is possible to leverage our already existing Fivetran connector.
-
Official comment
Hi David -
Thanks for submitting this feature request. Would you mind sharing where this report is in the documentation? I see a few different reports but not that specific one.
Fivetran doesn't typically support de-normalized data, however if this data is not able to be synced in any other way we could consider what specific fields are needed and if they can be synced to a new table or an already existing table.
Best,
Erin
-
We will need this as well in order to add stripe costs to our automated reporting process
-
Hello Erin, the report is documented here.
We've written our own API client to ingest this data into our data warehouse. This is an interesting case, as the fee data is not provided as an externally accessible set of normalized tables (apparently they are available if you are a Stripe Sigma user, but we are not).
-
Any update here?
Please sign in to leave a comment.
Comments
4 comments