phillip_api | Stripe Developers | Page 1

candid egretBOT Oct 18, 2024, 1:27 PM

#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always 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/1296827012723249204

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

#

keen shell Oct 18, 2024, 1:28 PM

#

Bildschirmfoto_2024-10-18_um_15.27.45.png

#

This my subscription create request. (trialPeriodDays should be undefined in this scenario)

const subscription = await stripe.subscriptions.create({
    customer: customerId,
    items: [{ price }],
    trial_period_days: trialPeriodDays,
    default_payment_method: paymentMethod,
    coupon: couponId,
    collection_method: "charge_automatically"
});

opaque walrus Oct 18, 2024, 1:32 PM

#

Thanks for the info and ID, looking in to this and will get back to you

#

I think this may be expected behavior for usage based billing but need to confirm with my colleagues

#

I see that it still says the next invoice says it will be for the same time period so if you record usage during that time period it should be billed properly. My guess is that this happens because there can be upfront fees but I do agree it is confusing when there is no actual payment involved

keen shell Oct 18, 2024, 1:45 PM

#

Okay, thanks, let me know what your colleagues think.
It would also be interesting to know if there is an option to not send 0€ invoices at all, but that's another topic.

opaque walrus Oct 18, 2024, 1:57 PM

#

Sounds good, reached out and will get back to you. As far as I know there isn't a general way to avoid $0 invoices unfortunately but I will file feedback requesting that

#

It looks like there isn't currently a good way of preventing that first invoice. There is a kind of involved way to do it: you can create the subscription in send_invoice mode, delete the first invoice while it is still in draft mode, and then update the subscription to be in charge_automatically mode, but that is obviously pretty cumbersome. I'll also file feedback about this, I definitely agree that that first invoice could be confusing. At least from a behavioral standpoint the subscription will charge properly

#phillip_api