Noman/payment - #123
Open
nomanSanjari wants to merge 10 commits into
Open
Conversation
…nd DB Schema to accomodate requirements Signed-off-by: nomanSanjari <nomansanjari2001@gmail.com>
Signed-off-by: nomanSanjari <nomansanjari2001@gmail.com>
…alizing payment controller and webhook handler Signed-off-by: nomanSanjari <nomansanjari2001@gmail.com>
…ail logic and added a separate field to database for keeping track of PaymentIntents Signed-off-by: nomanSanjari <nomansanjari2001@gmail.com>
… into Noman/Payment
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Signed-off-by: nomanSanjari <nomansanjari2001@gmail.com>
Signed-off-by: nomanSanjari <nomansanjari2001@gmail.com>
…ing to implementing cron scheduling and additional requirements Signed-off-by: nomanSanjari <nomansanjari2001@gmail.com>
Signed-off-by: nomanSanjari <nomansanjari2001@gmail.com>
Signed-off-by: nomanSanjari <nomansanjari2001@gmail.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Ticketing controller lets users buy tickets to events
Also where the frontend is gonna be pulling information from to generate the QR codes, both for client-side and business-side operations.
There's a method for business facing UI to be able to verify those QR codes when payload is received from reading the QR code.
Payment is where the Stripe implementation is.
Primary endpoint is Payment Intent Creation for actually starting the process and allowing the frontend to take over from there.
WebHook endpoint for all the functionality that allows us, with it right now it emailing users regarding payment status.
Changes made to the Event Schema so that can keep track of prices.
Added a Payment Schema such that we can keep a local store of information on payments and user records.
Added a Ticket Schema which keeps track of userId and eventId for tickets they purchase via the ticketing endpoints.