#itergo_best-practices
frozen gyroBOT
👋 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/1265576234495250537
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
zenith pagoda
- Do you mean the description to be displayed somewhere? I think we only have 1 kind of quantity and it might not be customizable
- We don't have the group invoices functionality, unfortunately. You can do something like have a custom grand total Invoice, and mark all the "member invoices" from different subscription to be paid_out_of_band, but might need more management effort
- Sorry don't really follow. Would you give an example for your expectation?
analog umbra
The best solution for us is:
Have ID of stripe product or ID of product quantity that I can assign to a specific employee in our DB or
I have separate subscriptions for each employee and I can assign subscription ID to specific employees in our DB and the customer receives a group invoice for all subscriptions.
We are stuck in the moment when We need to recognize if the employee has access or not 🙂
I think is the Miro.com scenario.
I have one team (which has got 1 subscription on the stripe in quantity 10) and I can assign max 10 members to the above team or I can change members in the team.
zenith pagoda
Sorry not familiar with Miro (?) So you have customer which is a company? And they have their employees?
And you either setup
- Each company has a Subscription with quantities corresponding to their employee count
- Each employee of a compnay has a Subscription
I think 1 makes sense. You can manage the information of which employee using Stripe's metadata for example
frozen gyroBOT
analog umbra
True, 1 makes sense. But what metadata I can use for it?
hoary zealot
Stripe metadata fields allows you to save any information in a form of key-value pairs: https://docs.stripe.com/api/subscriptions/create#create_subscription-metadata
My colleague suggested you can use it to specify which employees are included in the Subscription, if needed.
analog umbra
Oh great, I will check it.
I have one more question.
What if the payment is failed?
How can I handle the failed payment only for increased quantity?
How can I recognize payment failed for increased quantity instead of payment for the new whole cycle?
hoary zealot
What do you mean by this exactly?
payment only for increased quantity