Skip to content
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

[9.0] Don't try and find a user when stripeId is null #721

Merged
merged 2 commits into from
Jul 30, 2019
Merged

[9.0] Don't try and find a user when stripeId is null #721

merged 2 commits into from
Jul 30, 2019

Conversation

nick-f
Copy link
Contributor

@nick-f nick-f commented Jul 30, 2019

If a payment is manually created from the Stripe dashboard, it is
possible that it will not be linked to a customer.

When this null stripeId is used to find a user record, it will find the
first customer record that does not have a stripeId in the database.

Adding an early exit will prevent this from happening, and stop these
null stripeId users being erroneously referenced in webhook handling.

nick-f and others added 2 commits July 30, 2019 21:28
If a payment is manually created from the Stripe dashboard, it is
possible that it will not be linked to a customer.

When this null stripeId is used to find a user record, it will find the
first customer record that does not have a stripeId in the database.

Adding an early exit will prevent this from happening, and stop these
null stripeId users being erroneously referenced in webhook handling.
@driesvints driesvints changed the title Don't try and find a user when stripeId is null [9.0] Don't try and find a user when stripeId is null Jul 30, 2019
@driesvints driesvints merged commit 8f37c15 into laravel:9.0 Jul 30, 2019
@driesvints
Copy link
Member

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants