[IMP] payment_stripe: manage async notifications #84150
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
|
Demesmaeker
force-pushed
the
15.0-stripe_asynchronous_update-edm
branch
10 times, most recently
from
cd6a369 to
068a6e0
Compare
Demesmaeker
force-pushed
the
15.0-stripe_asynchronous_update-edm
branch
3 times, most recently
from
1caa9fa to
40630eb
Compare
Demesmaeker
force-pushed
the
15.0-stripe_asynchronous_update-edm
branch
from
40630eb to
ec90cb6
Compare
Demesmaeker
force-pushed
the
15.0-stripe_asynchronous_update-edm
branch
from
ec90cb6 to
4684cda
Compare
Feyensv
reviewed
Feb 17, 2022
Demesmaeker
force-pushed
the
15.0-stripe_asynchronous_update-edm
branch
4 times, most recently
from
056080b to
23e7d8e
Compare
Demesmaeker
force-pushed
the
15.0-stripe_asynchronous_update-edm
branch
from
23e7d8e to
f83a634
Compare
Feyensv
reviewed
Feb 22, 2022
Demesmaeker
force-pushed
the
15.0-stripe_asynchronous_update-edm
branch
from
f83a634 to
f0ad8a4
Compare
Demesmaeker
force-pushed
the
15.0-stripe_asynchronous_update-edm
branch
from
f0ad8a4 to
2a21f09
Compare
AntoineVDV
requested changes
Mar 14, 2022
Demesmaeker
force-pushed
the
15.0-stripe_asynchronous_update-edm
branch
8 times, most recently
from
8f38228 to
51ac5f3
Compare
Some payments may be confirmed asynchronously, and we need to be aware of their status, even if they are not in a "checkout session complete" event. Relying on successful payment or setup intents instead manage more use cases. task-2733725
Demesmaeker
force-pushed
the
15.0-stripe_asynchronous_update-edm
branch
from
51ac5f3 to
0e7ae37
Compare
Contributor
|
@AntoineVDV, you may want to rebuild or fix this PR as it has failed CI. |
Contributor
|
@robodoo r+ |
Contributor
|
Linked pull request(s) odoo/upgrade#3350 not ready. Linked PRs are not staged until all of them are ready. |
robodoo
pushed a commit
that referenced
this pull request
Mar 16, 2022
Some payments may be confirmed asynchronously, and we need to be aware of their status, even if they are not in a "checkout session complete" event. Relying on successful payment or setup intents instead manage more use cases. task-2733725 closes #84150 Related: odoo/upgrade#3350 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some payments may be confirmed asynchronously, and we need to be aware
of their status, even if they are not in a "checkout session complete"
event.
task-2733725
see also: