#Sinduri-sfu-woocommerce
1 messages · Page 1 of 1 (latest)
req_n3nMs7g3j49eUS
This is happened on our customer site and now i've replicated the same issue in my testing environment and i am sharing my test request ID
The PM (pm_1KqZrlEKZ4Dtb2aTTH9xdcbd) used in that Payment Intent was created via this API request: https://dashboard.stripe.com/test/logs/req_JiaRGgaA6DZ1jV
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
Now we fixed the issue but what can we do for existing recurring payments?
It's never been saved to a customer object, so after one usage it cannot be reused. Was initially used in this PI: https://dashboard.stripe.com/test/payments/pi_3KqZrpEKZ4Dtb2aT0XFvUJHE
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
You'll need to bring the customer back on-session and they'll need to input their payment details again for them to be saved correctly
omg!
There is no other way to resolve this!!?
One more concern should the customer need to pay all the renewal order manually?
Not unless you have another payment method associated to the relevant customers
I don't understand the question
I mean the parent order is created without setup_future_usage param, so all the renewal order get failed bcz the same payment method can't used with the customer again..This is the case
So my question is the customer need to pay all the renewal orders by entering payment details again..?
If you bring them on-session to provide payment details and save them for future usage, then they won't be required to provide payment details for every recurring payment no
okay thank you so much
Sure, np