#mehdi_code
1 messages ยท Page 1 of 1 (latest)
๐ Welcome to your new thread!
โฒ๏ธ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can start a new thread if you have another question.
๐ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1253783567742406656
๐ Have more to share? Add details, code, screenshots, videos, etc. below.
If this is just a 1-time discount you want applied to the first invoice, I think it makes sense to use a negative amount invoice item
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
hmmmm interesting, i like that workaround but a bunch of our backend code checks to make sure the invoice only has 1 item
which that would break
is there a diff workaround?
previously we did something like this with a subscription schedule, where we created a schedule with start_date now and end_behaviour release, with a single phase
could we do the same? (to avoid the invoice being charged immediately)
You could
Kinda complicated just for a 1 time discount though
You could also use a coupon
with a duration of once: https://docs.stripe.com/api/coupons/create#create_coupon-duration
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
oh does default_incomplete do the same thing?
oh hmm nope, seems like default_incomplete still tries to charge
actually, not sure
hmmm it might, just feels a bit odd to make a coupon for this one-off
That's what the duration of once functionality is for ๐
haha true
It's cleaner solution than using subscription schedule
i am leaning towards the subscription schedule workaround, only because then the flow of adding a coupon to an invoice is the same for both the first month and each successive month