garreh

[rare dove]

Hello 👋
You can use fingerprint to identify if the card has been set up before
https://stripe.com/docs/api/payment_methods/object#payment_method_object-card-fingerprint

[odd halo]

thats awesome

is there a way to prevent setting up payment method with same fingerprint ? like maybe some radar rules that can reject it

[rare dove]

Not sure if radar can help here as it can only compare it to one fingerprint you provide.
You'd likely want to store fingerprint in a database on your end and compare it when a new payment method gets created

[odd halo]

yes thats possible for us to store the fingerprint... but with the Stripe.js it will still technically allow that customer to set up same fingerprint payment method hundreds of times...?

so this filtering needs to happen on the stripe side, it should check to see if existing payment method has that fingerprint and if so deny setting up the method

[rare dove]

Right, but the payment method needs to be tokenized first in order to calculate the fingerprint. There's nothing in Stripe.js that currently allows getting the fingerprint without tokenizing

[odd halo]

might i suggest that being added as a feature to the Create api for Payment Method... so have a new attribute "deny_duplicate_fingerprint" which is a boolean that will send a deny/failed api creation response if that payment method matches an existing fingerprint ?

[rare dove]

I can file a feature request for this yes. You can also submit one by writing in

https://support.stripe.com/?contact=true