JimP

[trail granite]

👋 Thanks for reaching out
You can listen to this webhook event customer.subscription.updated:
Occurs whenever a subscription changes (e.g., switching from one plan to another, or changing the status from trial to active)
https://stripe.com/docs/billing/subscriptions/webhooks#events:~:text=customer.subscription.updated
https://stripe.com/docs/api/events/types#event_types-customer.subscription.updated

[twilit kelp]

Thanks. I actually want to check for the subscription being created, so I can then update it to set cancel_at?

[trail granite]

You can listen to the customer.subscription.created event, this one is sent when the subscription is created.

[twilit kelp]

Thanks.

Another quick question: is the Stripe customer record unique on email address?

[errant crest]

They're not no

[twilit kelp]

Really? More than one customer can have the same email address?

(within my account, I mean)

[errant crest]

Yep, plausible. If you need to prevent that you'd need to validate that yourself

[twilit kelp]

Wow. Glad I asked. So if I'm identifying customers uniquely by email in my app, how do I reliably associate my customer ID with Stripe customer IDs? I suppose I need to keep a record mapping my customer ID (with its unique email address) to (potentially) several Stripe customer Ids sharing the same email address?

[errant crest]

You'd store the cus_xxx ID (which are unique) directly in your DB and relate those to your users/sessions.

[twilit kelp]

I'm very glad I asked what I thought was a dumb question! Thanks so much for clarifying!! 👍

[errant crest]

np!

[twilit kelp]

Just want to say this is the best tech support experience I've ever had. Really appreciate it. 💯

[errant crest]

We love to hear it, thank you!