Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Connector Improvement: Add missing "amount captured" Stripe charge field

Completed
Will Bryant User

Hello,

We have been trying to port from our existing ETL vendor to Fivetran's Stripe connector. However we've noticed that the "charge" schema has "amount" and "amount_refunded", but is missing "amount_captured".

Could this please be added?

We also noticed that "statement_descriptor_suffix" is missing, which we can work around, but would be nice to have. Finally "failure_balance_transaction_id" is missing and others might need that (we don't get data in that field ourselves).

Thanks

Please sign in to leave a comment.

Comments

3 comments

Date Votes
  • Official comment
    Sandeep Preetam Saila Fivetranner

    Hi Will,



    This is a valuable suggestion—adding the amount_captured field, as well as other missing fields like statement_descriptor_suffix and failure_balance_transaction_id, would improve the completeness of our Stripe connector. I have added this request to our feature improvements backlog for prioritization and review.



    To help us better understand the impact, could you share more about your use case? Specifically, how does the lack of these fields affect your current reporting or workflow? Any details about intended analyses or downstream processes would be helpful for us to scope the work appropriately.



    We will keep this thread updated with any progress or changes regarding this request.



    Thanks,
    Sandeep

  • Will Bryant User
    • Edited

    Hi Sandeep,

     

    Without the amount_captured, you don't know how much money has actually been paid. Only how much money could be paid, if the payment were to be captured. Not the same thing.

     

    statement_descriptor_suffix just makes it easier to pull out the relevant part of what customers will see on their statement. It can be worked around if you know what the prefix is (which we do), but it's part of the Stripe API and is a bit useful. failure_balance_transaction_id would be important for Stripe customers who use payment methods that "bounce back" in the case of failures, such as bank transfers. My company itself does not use that but others may need it.

     

    Thanks

  • Sandeep Preetam Saila Fivetranner

    Hi Will,

    Thank you for your valuable feedback and suggestions. I'm pleased to inform you that we've just released an update to the Stripe connector, which includes the addition of the following columns to the CHARGE table: amount_captured, failure_balance_transaction_id, and statement_descriptor_suffix. You can find more details in our documentation here. We appreciate your support and are excited to help you transition smoothly.

    Best,  
    Sandeep