#nate-getaround
queen socket
grave charm
Hey, thanks for the info. Where specifically are you seeing the fingerprint qNGvoT3WQ6YiVHbQ vs F7bahEfiEuxob8f6? I see the F7 fingerprint on the card object on that Charge
kind cargo
This is how the records are coming to us. The first record, succeeded has the qNG fingerprint in both the source and payment_method_details. The second record, paid, for that charge from 2 seconds later has the F7 fingerprint in the source but the qNG fingerprint in the payment_method_details
grave charm
Interesting, are those from webhook events or is that from a report that we are sending you?
kind cargo
Stitch uses the Stripe API for its replication
It looks like they drive individual object fetches off of the events table but it should all be via webhook events I believe
grave charm
Is Stripe Connect being used here? I know there used to be some behavior where fingerprints would be different between platform and connected accounts but thought that that was corrected
And are you working with the Stripe API directly anywhere here? We don't develop the Stitch API so unfortunately we will only have limited advice on this server if you aren't writing the the code that is making these calls
kind cargo
https://github.com/singer-io/tap-stripe
So it appears that they are using the Singer tap for Stripe which is using the python based API using version "stripe==2.64.0", though the actual calls appear to be using stripe.api_version = '2020-08-27' but no we are not currently maintaining the pipeline. After reviewing this though we may need to