#nate-getaround-fingerprints

1 messages · Page 1 of 1 (latest)

rocky vessel
#

Hi 👋 I'm not certain off the top of my head why you would be seeing that, my suspicion is that we may be using a different hash process for the various types of objects so the fingerprints aren't calculated the same way. Do you have a couple examples of objects where you saw this behavior that you can share?

sweet marten
#

cus_59tcAXVrQSxcqy

This is the customer object that kicked off the conversation. I can pull other examples in our data as well if more would be helpful

rocky vessel
#

Thank you for that, I'm starting to go through the various sources, cards, and payment methods for that record. Do you happen to have the IDs of those types of objects that you saw which contained the same card details for this customer but had different fingerprints?

sweet marten
#

So I better understand are all cards kept in the sources object and the cards object?

Duplicate Sources on the Current Customer Object
src_0JnVV6Zw6GjhZd0YIh1bHxg5
src_0JnVUxZw6GjhZd0Yat2tZvLa

Duplicate Source/Card Object on the Customer updated = 10/22/21 7:59
src_0JnMPWZw6GjhZd0YAhKZ7WrY
card_0JnMNmZw6GjhZd0YcqvWesEU

Duplicate Sources/Cards Objects on the Customer updated = 7/28/21 9:56
card_0JIDFZZw6GjhZd0YALxZChm0
card_0JGE6ZZw6GjhZd0YnVXsmkb6
card_0JGDHUZw6GjhZd0YwPSjsEsA

rocky vessel
#

Sources were the original objects that held these details, and Card objects are a more specific type of Source objects. Payment Methods can also contain card details, and are the newer object that take the place of Sources for newer integrations.

#

Duplicate Sources on the Current Customer Object
src_0JnVV6Zw6GjhZd0YIh1bHxg5
src_0JnVUxZw6GjhZd0Yat2tZvLa
For this grouping, I do see that the details are the same, but the fingerprint is also the same as expected.

src_0JnMPWZw6GjhZd0YAhKZ7WrY
card_0JnMNmZw6GjhZd0YcqvWesEU
These objects appear to be in the same scenario as above, the information is the same between them so their fingerprints also match.

Duplicate Sources/Cards Objects on the Customer updated = 7/28/21 9:56
card_0JIDFZZw6GjhZd0YALxZChm0
card_0JGE6ZZw6GjhZd0YnVXsmkb6
card_0JGDHUZw6GjhZd0YwPSjsEsA
These three appear to each be a different card, and therefore it's expected for their fingerprints to be different.

Stripe does not automatically deduplicate sources/cards/payment methods, but provides the fingerprint field so your integration can identify and remove duplicates if that is something that you would like to do.

sweet marten
#

So using the fingerprint is likely a better unique id for each payment method than the id?

Is there something in our implementation that could be causing this behavior?

rocky vessel
#

Correct, the fingerprint is the value that you should be using to identify duplicates, every object in the Stripe ecosystem has a unique ID.

If your flow always creates a new source/card, then that is likely why you would see so many attached to a customer. Though it is possible for a customer to have and use a large number of different cards.

sweet marten
#

With respect to the sources and cards. If there is a src_ and a card_ object should we be using one over the other for analytics or should it all be the same data as long as the fingerprint is shared?