wip: upgrade stripe api #1858
Draft
wip: upgrade stripe api #1858
Conversation
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.
Issue(s)
part of #1705
Description
to upgrade to py 3.12 we need to upgrade stripe, but the API we were using is no longer supported.
We can no longer charge users an arbitrary amount. We need to create a product and a price.
We still need to decide how we implement this in stripe - do we let users pick the price on the stripe site, or do we do it on freesound and dynamically create a price object?
With payment links, we can get payments from people without needing to first create a session from freesound, but we can't link additional data (credit name if they don't want their fs name).
In chat we discussed removing paypal and activating more payment types on stripe.
Deployment steps: