#jackyfreeds_best-practices

1 messages ¡ Page 1 of 1 (latest)

lapis pierBOT
#

👋 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/1421231573780660390

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

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.

prisma bough
#

Yes, this can be a good use case for Billing Entitlements. once you create the features you can then listen for the webhook event to let you know what the customer's entitlements are and proceed from there.

idle ingot
#

Right, but would you say that method is the best practice, or should I add specific metadata also specifying the limits and features?

prisma bough
#

What is the purpose of the metadata and where will it be added?

#

Not sure I understand the question.

idle ingot
#

Essentially, what is the right implementation through stripe and my own platform to create a bronze package that limits 10 users to be created on my platform

prisma bough
#

Have you tested the entitlements flow in the Sandbox?

idle ingot
#

Not yet

prisma bough
#

I recommend you do that.

idle ingot
#

So if stripe enforces which features are being enabled per account on my platform via my platform listening to stripe webhooks.

I just need to ensure that stripe knows which products on my platform map to those webhooks and I assume the products will be available on my platform per whats been configured in Stripe? I was thinking the platform would send Stripe which products the accounts have been entitled with.

#

These entitlements would be true for all features that live above core functionality on the platform then?

#

And I suppose creating a trial account where a customer is not going to pay first would bypass entitlements some how?

prisma bough
#

When creating the relevant payment request, you'll be information Stripe of the product the customer is purchasing.

idle ingot
#

Would you be available for a qiuck call?

#

This is leaving me with more questions than answers, but I think I have a minor misunderstanding

prisma bough
#

We don't do calls unfortunately.

idle ingot
#

Is there another agent you can direct me to

prisma bough
#

What is your misunderstanding?

idle ingot
#

So if I create a settings page within each account that can add, add-ons ons per account, how would this work with stripe? The flow I imagine would be that the customer contacts our company to turn on a feature or upgrade their account and then they get billed for it monthly, instead of them paying for it right away and then getting the feature.

#

I am B2B so customers will want to order through PO rather than changing plans within our portal

prisma bough
#

Gotcha

idle ingot
#

So because they're paying with POs I want to receive the PO then turn on the billable feature in each account

#

I think that would be ideal

prisma bough
#

I'm not sure what approach will work for this use case. I'll need to double check.

#

This is separate from Entitlements, it's more about how to handle the upgrade of subscriptions.

idle ingot
#

Okay, can you let me know please? I am hoping to find the best practice so I don't build it incorrectly from the start

prisma bough
idle ingot
#

Okay, I'm thinking maybe a simplier approach would be to create a page unique to admins with billing permissions where they can turn on different products and features from our console instead of us doing it internally, that way we can still use products & features/entitlements.

The only thing to verify with you is that if the charge for that would appear in the next month's billing statement instead of being billed on the spot.

prisma bough
#

Ok, I think I understand where the confusion is from.

#

You will use Entitlements to take advantage of events that are triggered that will let you know what the user is entitled to based on the products they signed up for. You will also need to implement functionality that will handle the upgrade/downgrade of the subscription. In this case, that's where Subscription Schedules will come in to play.

#

When you update the subscription they will not be charged until the beginning of next phase or the period you specify [0].