daisdead | Stripe Developers | Page 1

north questBOT Jan 31, 2024, 4:12 PM

#

coarse raven Jan 31, 2024, 4:12 PM

#

I think billing_reason would specify that it was for a trial. If that isn't it, can you send me the invoice ID for me to double check?

boreal osprey Jan 31, 2024, 4:14 PM

#

I don't see that as possible enum from the docs 👀

Give me a moment to find you an invoice ID example please!

#

in_1OegRND0tZaJVqhDBIAvM0wq Here's an example invoice

coarse raven Jan 31, 2024, 4:16 PM

#

Should be on the invoice object https://stripe.com/docs/api/invoices/object#invoice_object-billing_reason

The Invoice object | Stripe API Reference

Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.

boreal osprey Jan 31, 2024, 4:18 PM

#

Sorry to clarify, I didn't see a value within billing_reason that specially points to trialing. Unless you were referring to subscription_create which sounds more like a superset that could or not, include trials

coarse raven Jan 31, 2024, 4:27 PM

#

Ah, my apologies, I thought we did have a specific billing reason for that.

#

Unfortunately I'm not seeing anything on the invoice other than that some of the invoice items have a name that starts with trial. So I think you would want to retrieve the subscription object or listen to customer.subscription.created and check the subscription's status from there

boreal osprey Jan 31, 2024, 4:31 PM

#

I see! Yeah, we're working w/ a team regarding billing integration and it was flagged that checking the subscription object would be vulnerable to timing of that check if we were to process a invoice at a later date

#

We were floating around the idea of adding metadata to signal such but confirming there isn't an out-of-the-box signal of such behavior

coarse raven Jan 31, 2024, 4:43 PM

#

Ah gotcha, in that case it sounds like setting metadata on the invoice object would be a good way to keep that context for the future

#daisdead