facu_paymentsheet-deduplicate-paymentmethods | Stripe Developers | Page 1

ripe ibexBOT Aug 23, 2024, 4:20 PM

#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1276576875170500689

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

neon pawn Aug 23, 2024, 4:26 PM

#

Hi 👋

Just so I'm clear, the issue you are having is that your customers can re-enter the same bank information or card information and generate a new Payment Method, but when you review the new Payment Method you see it is the same actual bank account or card?

somber iron Aug 23, 2024, 4:30 PM

#

Hi snufkin!
Exactly, I need to know if there is a way to validate in the PaymentSheet that the payment method is already registered, because if not, something like this happens to me

(ll the same, same number, CVC, and expiration date.)

neon pawn Aug 23, 2024, 4:31 PM

#

Okay, so first the tough news. No there isn't a way to validate this directly in the Payment Sheet

#

BUT

#

there are some work-arounds.

#

The easiset, in my opinion, is to display the saved payment methods directly in the payment sheet so your customers can select an existing one instead of creating a new one.

somber iron Aug 23, 2024, 4:35 PM

#

Exactly, that’s how we have it set up currently. A list of payment methods where the customer can select one, but in case they don’t see it or simply create a new one, it would get duplicated

neon pawn Aug 23, 2024, 4:36 PM

#

Unfortunately that is logic you would need to build into your integration. There isn't a way to configure the PaymentSheet to do this for you.

somber iron Aug 23, 2024, 4:39 PM

#

I completely understand, and I appreciate your help so far. I have a question: Is there a way to handle this entire process on the backend, where the card/ACH data can be sent and checked for duplicates? This would be without using the PaymentSheet.

neon pawn Aug 23, 2024, 4:48 PM

#

I do not think we have support for that but let me double check.

#

Essentially you would be transfering untokenized data which is a huge PCI risk and you would need to have your app thoroughly reviewied for us to support it.

somber iron Aug 23, 2024, 4:50 PM

#

Ok, and currently the data that could be compared to determine if two payment methods are the same would be their ‘last4’ and ‘expiration date,’ correct?

neon pawn Aug 23, 2024, 4:55 PM

#

Actaully there is a much more precise property you can use. The card.fingerprint
https://docs.stripe.com/api/payment_methods/object#payment_method_object-card-fingerprint

#

Uniquely identifies this particular card number. You can use this attribute to check whether two customers who’ve signed up with you are using the same card number

From the API doc

somber iron Aug 23, 2024, 4:56 PM

#

Ok! I think with this I can find a way to solve the problem. Thank you so much for all your help!

neon pawn Aug 23, 2024, 4:57 PM

#

Sure thing! I'm happy to shed what 💡 I can 🙂

#facu_paymentsheet-deduplicate-paymentmethods