#mrfede_payments-future
1 messages ยท Page 1 of 1 (latest)
๐ Welcome to your new thread!
โฒ๏ธ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1253446922891563059
๐ Have more to share? Add details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- mrfede_link-notshowing, 3 hours ago, 62 messages
Hi there ๐ that depends on whether your customer has more than one Payment Method, but I'd expect the Payment Method that was created by the Setup Intent to be in the list of Payment Methods you'd get back.
I don't think you need to change your flow. Are you encountering errors while testing it with Link?
Yeah
What im doing is using the PaymentMethod that I got from the confirmed SetupIntent, to create the PaymentIntent... but that is giving me this error when I try to create the PaymentIntent:
"message": "The payment failed."
"type": "card_error"
From what I understand from the docs, I should not pass that PaymentMethod, but instead, search for the customer's payment method and grab one from there
But there are multiple payment methods.... how would I know which one it is
If you're manually creating a Payment Intent to be paid by a specific Payment Method, you should use the Payment Method that you want to use for the payment.
That's a little hard to answer, because I'd sort of expect you to know which Payment Method you plan to charge.
Can you share the ID of the example Payment Intent from your testing that encountered the error you're referring to?
When it comes time to process a payment for a Customer who already has Payment Methods, do you let the customer choose which saved payment method they'd like to be charged? Do you assume the newest Payment Method is the one that you should use? Do you plan to have a concept of a customer's "default" Payment Method and need to track that?
mrfede_payments-future
This is one of the PaymentIntents that failed: pi_3PTrRGLHmVLUO0Ni0z1qgzud
The customer chooses the payment method in the PaymentElement, once he chose one and click a "Next" button, then I confirm the SetupIntent, which attaches the PaymentMethod
That leaves me with a confirmed SetupIntent and a PaymentMethod Id... I use that to create the PaymentIntent
Non 3DS credit card works fine BTW
Which exact test card number are you using?
This one from the docs 4000000000003220
yeah that one always require 3DS all the time. We recommend not using those test cards. Prefer the ones under https://stripe.com/docs/testing#regulatory-cards instead
Ok let me try one of those
I tried with the first one on the list and it gave the same error
This is the payment intent pi_3PTrxcLHmVLUO0Ni0FOH18Ui
This is the card: 4000002500003155
Did you properly go through 3DS first?
I think so... I completed this one
Gotcha, so yeah I can repro. Looks like we don't properly handle previously set up card with 3DS in Link.
My advice is to just ignore it, just use the normal 4242424242424242 card in Link
I would say Test mode, just a quirk here. But I'll flag internally because it really should work as you were expecting and not fail that way
sure thing ๐
One more question... lets say my customer is using Link, after I confirm the SetupIntent, is there a way I can get the card info? From either the SetupIntent or the PaymentMethod?
no that's impossible we abstract that away from you
Ooh ok good to know! Thanks again...good night!