Added support for customizing Stripe Checkout parameters #10
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 addresses issue #2.
Some of the checkout parameters are specified in
DRF_STRIPE
settings:CHECKOUT_SUCCESS_URL_PATH
: The checkout session success redirect url path.CHECKOUT_CANCEL_URL_PATH
: The checkout session cancel redirect url path.PAYMENT_METHOD_TYPES
: The defaultdefault payment method types
, defaults to
["card"]
.DEFAULT_CHECKOUT_MODE
: The default checkout mode, defaults to"subscription"
.By default, you can create a checkout session by calling the default REST endpoint
my-site.com/stripe/checkout/
, thisREST endpoint utilizes
drf_stripe.serializers.CheckoutRequestSerializer
to validate checkout parameters and create aStripe Checkout Session. Only a
price_id
is needed,quantity
defaults to 1.You can extend this serializer and customize Checkout behavior, such as specifying multiple
line_items
,
payment_method_types
, andcheckout_mode
.See README for more info.