-
Notifications
You must be signed in to change notification settings - Fork 681
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
Confirm Payment notification never sent #1676
Comments
Hi @ragulka. Thank you for flagging this. If that's the case then yes we should fix this. I guess it's the |
Thank you for reporting this issue! As Laravel is an open source project, we rely on the community to help us diagnose and fix issues as it is not possible to research and fix every issue reported to us via GitHub. If possible, please make a pull request fixing the issue you have described, along with corresponding tests. All pull requests are promptly reviewed by the Laravel team. Thank you! |
Correct - |
Yes please! ❤️ |
@ragulka are you still up for sending in that PR? |
Since we only had one ticket about this and there's no activity here I'm gonna close this one. |
@driesvints sorry - somehow I did not see the notifications from this thread. I'd be up to submit a PR, I've just been rather tight with time. |
@ragulka no worries. Would still very much appreciate a PR when you can spare the time. |
Cashier Stripe Version
15.3.2
Laravel Version
10.48.9
PHP Version
8.2
Database Driver & Version
No response
Description
It looks like when a subscription is created via Stripe Checkout, and a future payment (on subscription renewal) requires confirmation, the notification is never triggered, because of the
is_on_session_checkout
check here.This check was added in this PR to prevent confirmation notifications being sent while the customer is in the checkout session, which makes sense, because the initial payment is not off-session: the customer can already see that they need to confirm the payment when checking out.
However, it seems to me that this flag should be cleared from subscription metadata once the initial payment is successful, so that future renewals can still trigger this notification.
Steps To Reproduce
4000002760003184
)The text was updated successfully, but these errors were encountered: