#secretsquirrel
1 messages · Page 1 of 1 (latest)
yes, works fine when you try it :
In the diagram in the docs here https://stripe.com/docs/billing/subscriptions/usage-based#lifecycle it says to set the payment_behavior to "default_incomplete". Is that necessary with Checkout? If so, how do we do that?
not necessary when using Checkout no
Terrific. And if I had an additional flat fee that I wanted to include with the usage fee, but I wanted to bill both usage and flat fee in arrears, how do I set that up with checkout? I'm looking at the documentation here: https://stripe.com/docs/billing/subscriptions/usage-based#billing-in-arrears
I've tested this out but can't figure out how to not have it invoice immediately
you just pass another line_item with a regular licensed price
well yeah it will invoice immediately if you pass a licensed Price when creating the Session, since those always charge in advance, only usage can be charged in arrears
The documentation says "If you charge a flat fee in addition to the usage, Stripe won’t charge for the flat fee until the end of the billing cycle, along with any accrued usage."
Is that not true? Or am I missing some param in order to configure that?
what you might do is add it but also pass a 100% one-time coupon to https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-discounts-coupon so that first payment is skipped
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
I guess it depends what who wrote the docs was thinking of
it is true if they meant, you add a one-time flat fee during a cycle
since that will be added to the next invoice generated.
if they/you mean a recurring flat fee, that is charged on creating the subscription, and then subsequently on each invoice, AFAIK
e.g.
Hmm, ok I think I get that, but I would prefer not to use a discount. I'm probably just going to create a second usage-based product with the recurring flat fee that I am hoping to charge, and then just set the quantity of one and aggregate usage to "last_ever".
I think that might work yeah. There isn't really a clean solution, we just do not natively support licensed pricing plans that charge in arrears. Coupons do work at least as another option