-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[CORE-942] [stripe] 3 payment intents created for 2 providers when updating cart totals #2736
Comments
Thanks for reporting this one @chemicalkosek. @adrien2p Would you be up for digging a bit into this one? |
Yes sure 💪 |
I have also noticed that sometimes the number of customers in that situation is doubled (same email) |
@olivermrbl, in the cart, set payment sessions, if the total > 0 and if there is only one provider and no payment session, then we create a new session. Could it be the issue? So we update one and create a new one? could it be it? I ll test just to be sure |
Thanks for sharing @chemicalkosek. We'll attend to this one. |
@chemicalkosek can you share us the packages versions you are using please? |
|
@chemicalkosek I found the issue, I ll release a snapshot that you will be able to test very soon, thanks again for reporting reference: #2921 |
Bug report
Describe the bug
If there are two providers available (ie. stripe and stripe-przelewy24) and the customer is a new email, then if you update the cart totals, we end up with 3 payment intents: 2 with new totals, 1 with initial totals.
This doesn't happen when the customer already existed in stripe before starting the checkout.
System information
Medusa version (including plugins): 1.6.4, medusa-payment-stripe: 1.1.48
Steps to reproduce the behavior
stripe
andstripe-przelewy24
)Expected behavior
2 payment intents for 2 providers with correct totals.
Screenshots
Additional context
This PR (which is included in 1.1.48) states that it should be fixed, but that's unfortunately not the case: #2603
CORE-942
The text was updated successfully, but these errors were encountered: