#riptired_api
1 messages ¡ Page 1 of 1 (latest)
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- riptired_api, 1 day ago, 5 messages
- riptired_webhooks, 3 days ago, 7 messages
- riptired_code, 3 days ago, 12 messages
đ 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/1268718887264845834
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
For context I have a stripe subscriptions based product so I am only monitoring the events related to that product line (anything related to subscriptions, customers, invoices)
Hi there, are you asking if customer filed is always non-empty for invoice, subscription and checkout session objects?
Yeah for any objects related to stripe subscriptions if the customer id will always be present
I assume so?
https://docs.stripe.com/api/subscriptions/create?lang=ruby#create_subscription-customer yes customer is required for subscription
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Will the customer object (when retrieved from stripe api) always have the product id / price_XXXX value?
No, customer objects aren't associated with products or prices
even after a customer has purchased a product?
The core question I have is what attribute should I be using for the following:
Let's say I have 5 products in my stripe account. Each product is for a different client we service as a Stripe Connect Platform.
Each product may have X subscribers. For each subscriber, I need to identify which product they are subscribed to and provision access to that specific product based on the stripe events (active subscriber, cancelled, etc)
OK, so your question is about what webhook event that you should listen to so that you can provision access / disable access for the corresponding customer?
No, more specifically what attribute I can use that is consistently available across events
I was planning on using the price_XXX value before but I realized that attribute was not consistently available across events since the price__XXX would give me an indication of what specific product the customer was subscribed to
I still don't quite understand what you want to achieve, but I'd recommend you reading this doc https://docs.stripe.com/billing/subscriptions/webhooks#state-changes to understand more about using webhooks for subscriptions
I've already read this
I understand how to provision or deprovision access to the product based on the events
I am asking a different question here: Given that I have 5 products which each have a distinct set of customers, based on a given stripe event, what attribute should i use to identify what product that event is related to
There's no direct relationship between product and customers. If you want, you can form a relationship by adding the product ID to the customer's metadata, so that you can achieve the product ID from the customer object.