#kado-kaelan-subs
velvet path
valid elm
I'm also wondering if people usually track if theyre an active subscriber in their own system or rely on stripe
velvet path
For your first question, given a customer ID you can list all their subscriptions (https://stripe.com/docs/api/subscriptions/list#list_subscriptions-customer) and check the statuses of the subscriptions
valid elm
great! to expand on the second question. I'm thinking through cancellations right now and am finding some interesting edge cases trying to track the active subscription in my system
so thinking of just relying on stripe for that
velvet path
It's up to you and depends on your integration requirements really - if relying on Stripe for tracking active subscriptions means you're making a LOT more api requests, it would be in your best interest to keep this data in your own databases so you're not blowing past your api request limits.
Most people are able to closely track the current state of the subscription by listening for the customer.subscription.updated events and making sure to update their database if there are changes they need to track