jbranchaud/egg 270 create lifetime membership checkout session #1441
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
make it explicit what the known/handled stripe events are
jbranchaud
force-pushed
the
jbranchaud/egg-270-create-lifetime-membership-checkout-session
branch
from
6f52fdd
to
e751192
Compare
the server needs this value (not the checkout session ID) in order to create a `transaction` record for this purchase
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR does two core things:
First, it sets up the pre-purchase flow for Lifetime Subscriptions via the
/foreverpath. This collects an email if the user is not already signed in and then hands them off to a Stripe checkout session.Second, it handles the post-purchase flow. This sets up egghead-next to process Stripe webhook events for
checkout.session.completedvia inngest. It will only process for a specific purchase (stripe price ID) because everything else should be handled by the egghead-rails backend.Note: this depends on some API changes being merged into egghead-rails before this changes can be deployed.
Deployment Task
checkout.session.completedto the list of events for the production webhook endpoint