Connector Improvement: Support for Stripe API Version 2023-08-16 to Access fingerprint Field
AnsweredWe request that Fivetran updates its Stripe connector to support Stripe API version 2023-08-16 or later. This update is necessary because earlier versions of the API does not report correct fingerprint field in the payment_method.sepa object, which is critical for our reconciliation and fraud detection processes.
Business Impact:
The fingerprint is a unique identifier for the underlying sepa, which remains consistent across multiple uses, even if the card details are tokenized separately. Without this field:
-
We cannot accurately link or de-duplicate card activity across payment methods.
-
Fraud detection and user profiling are significantly limited.
-
It impairs the integrity of our data warehouse analytics, especially in customer behavioral analysis.
Current Limitation:
Fivetran's Stripe connector currently pulls data based on a Stripe API version prior to 2023-08-16. As a result, the fingerprint field is wrongly in the synced data. Manually altering the API version on our Stripe account is not a viable workaround, as Fivetran's connector enforces its own version.
Request:
Please update the Fivetran Stripe connector to use Stripe API version 2023-08-16 or newer, or allow users to configure the API version explicitly. At a minimum, this would ensure support for the fingerprint field in the payment_method.card object.
Additional Context:
Stripe API changelog (2023-08-16): https://stripe.com/docs/upgrades#2023-08-16
Relevant object: payment_method.card.fingerprint
Thank you for considering this request. Please let us know if further information or testing support is needed.
-
Official comment
Hi Davide,
This is a valuable request. The need to support Stripe API version 2023-08-16 or newer—particularly for accessing the
fingerprintfield in thepayment_method.cardandpayment_method.sepaobjects—is now added to our feature improvements backlog.Testing support will be essential for this implementation. We will reach out for your assistance once we move forward with this change.
Any progress will be communicated here so the community is kept informed.
Thanks,
Sandeep
Please sign in to leave a comment.
Comments
1 comment