-
Notifications
You must be signed in to change notification settings - Fork 203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stripe Express Integration Error on Failed 3D Secure Authentication. #2168
Comments
@daniel-toader, thank you for reporting this issue regarding the Stripe Express payment integration. I have tried to reproduce the problem on my end by following the steps you described, but unfortunately, I was unable to encounter the same errors ( To better understand and investigate this issue, I kindly request your assistance in providing some additional information:
Having more detailed information about your setup and the circumstances under which the issue occurs will greatly assist in identifying potential contributing factors and ultimately resolving the problem. Additionally, if you have access to a staging or development environment where the issue can be consistently reproduced, it would be extremely helpful if you could provide access to that environment for further investigation. I understand that debugging issues can be challenging, especially when they cannot be easily reproduced. Please feel free to contact our support team for further collaboration and assistance in resolving this issue. Our support team will be happy to work closely with you and gather any additional information or access required to investigate and find a solution. I appreciate your patience and cooperation in helping us gather the necessary information to effectively resolve this issue. I remain committed to working with you and our support team to ensure a smooth payment integration experience. |
@mralaminahamed, i believe the issue was addresed by the Dokan developers in the latest updates. Now we have this (200 OK) (A request to update a PaymentIntent source_cancel completed) after a failed 3D Secure event in the Stripe dashboard log. |
Thank you for the update, @daniel-toader. I'm glad to hear we have resolved this issue in our latest updates. Seeing the expected responses in the Stripe dashboard log after a failed 3D Secure event is a positive sign. I appreciate you confirming the resolution. It's great when critical issues like payment integration are properly addressed. If you encounter any other problems or need further assistance, please feel free to contact our support team. They'll be happy to collaborate with you and provide any additional help needed. We are committed to ensuring a smooth payment integration experience, and our support team is ready to assist you further if required. |
Bug Description
When a client fails 3D authentication and attempts the payment again, this error occurs in the Stripe Developer Dashboard.
..................
x payment_intent_unexpected_state
You cannot modify customer on a PaymentIntent once it already has been set. To fulfill a payment with a different Customer, cancel this PaymentIntent and create a new one.
..........
From what I see (I'm not 100% sure) users have found a workaround by leaving the checkout and returning to attempt the payment again.
This integration error it's followed by another:
...........
x resource_missing - intent
No such setupintent: 'pi_.............'
.............
The text was updated successfully, but these errors were encountered: