#mesudev_paymentmethod-list
idle gladeBOT
đ 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/1230654459084935229
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
trim dewBOT
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.
- mesudev_api, 6 days ago, 30 messages
drifting junco
GooglePay and ApplePay work the same as a card so you just pass card. We highly recommend not passing payment_method_types though and using Dynamic Payment Methods, see https://docs.stripe.com/payments/payment-methods/integration-options#using-dynamic-payment-methods
torpid rampart
I explicitly have to pass it as our integration requires auth and capture & must not redirect our customers while paying / saving payment methods, which is the case for these three payment types.
drifting junco
sounds good, then card
torpid rampart
Actually then we did it right. Because the problem we faced is that, after saving a payment method according to the provided link, we did not get any payment method for the concerned customer when calling https://docs.stripe.com/api/payment_methods/customer_list afterwards
So to list payment methods of a customer which have been added according to this guide: https://docs.stripe.com/payments/save-and-reuse?platform=web&ui=elements, do we have to explicitly attach the created payment method to the customer using https://docs.stripe.com/api/payment_methods/attach
drifting junco
Sorry you're losing me a bit. Do you have a concrete example of a PaymentMethod that isn't listed? I don't really get the question
mesudev_paymentmethod-list
torpid rampart
In other words: when you store a new payment method for future usage, and you provide the customer ID 'cus_xyz' for the setup intent you create to add the new payment method. When adding the new payment method according to your guide with setup intent client secret you obtained, and you properly add the payment method. After that, when I fire the API request https://docs.stripe.com/api/payment_methods/customer_list , with the customer ID provided to create the setup intent 'cus_xyz', I am not getting any payment method back in the response. The 'data' value of the associative array that is the response (PHP) is empty.
drifting junco
yeah that should be impossible. Can you give an example Customer id cus_123 and an example SetupIntent id seti_123 so I can check?
torpid rampart
Is that normal; do you have to explicitly attach a payment method to a customer, even though you provide the customer's ID when creating the setup intent ?
drifting junco
no you don't, it should attach automatically. Once I look at the ids you share I can tell you what went wrong
torpid rampart
cus_OZ4eC8IloOhJt4
drifting junco
yeah that Customer has a ton of SetupIntents created, but you never seem to confirm those SetupIntents, so not card is collected/attached
torpid rampart
yes that's possible as we're using that in testing
but we have confirmed at least one setup intent, so it's really weird that that's not showing up
drifting junco
I mean I didn't check them all. If you give me an exact SetupIntent I can look
or really try a new one now, confirm it and then I can look
torpid rampart
no you don't, it should attach automatically. Once I look at the ids you share I...
but that's what I wanted to double-check with you, as I supposed that behaviour. Guess that there's an issue on our end then
torpid rampart
I mean I didn't check them all. If you give me an exact SetupIntent I can look
seti_1P5DSjGX4jC1zJlQ4nd4dCOu
this one is confirmed
and should hold the payment method
pm_1Mq6jBGX4jC1zJlQcfK5QWeG
drifting junco
the specific SetupIntent you gave me was never confirmed. Created, it has status: 'requires_payment_method'. So you must have a bug in your code where you think you confirm it but never did and just create a PaymentMethod and never do the next step possibly
torpid rampart
can you maybe search for the pm_1Mq6jBGX4jC1zJlQcfK5QWeG on your end? Isn't it attached to any customer at all ?
drifting junco
it is attached to a completely different Customer cus_NUMsIFUbOM6RrC
torpid rampart
what
ok that's super strange
Is this conversation stored in discord, do you may know that ?
Definitely have to investigate on that
and sorry for wasting your time then
drifting junco
yeah it's all public and in Discord, you can access it with https://discord.com/channels/841573134531821608/1230654459084935229
torpid rampart
excellent cheers and apologies again!