-
-
Notifications
You must be signed in to change notification settings - Fork 157
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
[Payment] when payment is authorized or paid, order get's confirmed #2628
Conversation
|
@solverat We would like to get your Feedback on this. |
I'm afraid of this. |
Funny! We just experienced this behavior in one of our new shops (not in manually mode but by payum / client workflow). I'm unable to reproduce it, though... Not sure, if this is true:
The only difference now is, that the callback happens after a transition instead of the payum extension. If we're dealing with a sort of race condition here, this PR could be an improvement, since the order transition will be dispatched at the end of the payum cycle. |
@solverat so not afraid anymore? :D |
I guess not 😀 |
@solverat the main issue that this tries to solve is, when a user exists the payment workflow just before we come back to the payum capture/authorize route, and there is no async implemented, you never know the status of the payment. if you then manually confirm it in the backend using the payment workflow, the order never gets confirmed. this fixes that. We actually could reproduce it. We looged at the access logs of these orders (based on timestamps) and saw they never returned from the PSP to the shop. |
Current Issue is that:
UpdateOrderStateExtension
never updates to order state cause the payment state got changed beforepay
transition, order is stuck innew
and does not get confirmedThis PR automatically
confirms
the order when a single payment is partially paid, fully paid, partially authorized or fully authorized.@solverat I would like to get your opinion on this.