#darkstar_unexpected
1 messages · Page 1 of 1 (latest)
👋 Welcome to your new thread!
⏱️ We automatically close idle threads, which makes them read-only. Make sure you stick around to chat in realtime!
🔗 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/1212647602323980289
📝 Have more to share? You can add more detail below, including code, screenshots, videos, etc.
⏲️ 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. Thank you for your patience!
Stripe doesn't de-duplicate the payment methods to save on the customer. This is the video showing how to de-duplicate payment methods:
Learn how to save a payment method without duplication. This video uses the Deduplicate payment methods tinydemo on Glitch. Remix the project to follow along: https://glitch.com/edit/#!/stripe-tinydemos-deduplicate-cards
Presenter
Charles Watkins - Developer Advocate at Stripe - https://twitter.com/charlesw_dev
Table of contents
00:00 ...
Find help and support for Stripe. Our support site provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
That's a bummer because I don't create payment methods manually. The payment intent is created on the server (.NET) before the checkout (custom flow) page is displayed and then it's all taken care of by Stripe's own Payment Elements JS library. I just call the .confirmPayment() function at the end. So at the time of PI creation, I know nothing about the payment method that will be used. And I also don't save the payment method to the Customer object, it happens automatically...
The linked YT video explicitly uses card payment, whereas we use Payment Element that automatically supports various payment methods.
Ah I see! This is also supported in Payment Element with deferred intent flow, i.e. collect payment method in Payment Element first, then charge later: https://docs.stripe.com/payments/accept-a-payment-deferred
Once the payment method details is collect, your server can retrieve the Payment Method information to check the fingerprint exists.
- If the fingerprint exists, then old payment method should be used
- If the fingerprint doesn't exist, then new payment method can be used
OK. Is that the only solution?
Yup! This is the only solution
Alright. Thank you very much!