#shakilkhan496_api
1 messages ¡ Page 1 of 1 (latest)
đ 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/1268616456061452475
đ Have more to share? Add more 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.
- shakilkhan496_api, 1 day ago, 29 messages
This was the error message from the first payment attempt
^I contacted the client. He changed his card information, and that's when I received the Stripe log error message
Any one for help?
I'm looking
Have you tried attaching the payment method to a customer prior to using it directly with the PaymentIntent?
It is wordpress site with WooCommerce Stripe Gateway/8.5.2 (https://woocommerce.com/products/stripe/)
Every payment is working fine
But for this one this erroe
Were all the customers set up this way?
I'm not seeing anything that'd suggest that the issue is something else other than what's returned in the error
To solve this what we need to do? Do we need to tell them to create a different account ?
So woocommerce is a third-party integration.. I don't know how exactly they utilize Stripe APIs.. Have you tried talking to their support team and check if they had a solution for this?
Stripe won't have insights into their integration flow so I can't say what would fix this error.
Okay I have not contacted them, but we have just re-installed the plugin with their updated