feat(checkout): build payment section #67
Merged
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.
Closes #36
This PR implements the payments section for checkout. The flow basically goes as follows:
payment
record on the DB and also hit the Stripe API to create apayment_intent
. The frontend server will receive aclient_secret
that identifies thepayment_intent
.client_secret
and render the Stripe payment form.payment
status on the DB. Also, the Stripe components on the frontend will redirect the user to a thank you page. If the payment fails the flow is analogous.https://www.loom.com/share/fc0bc160ec444e41b0199784d9ec7e34