#chunkyboi_credit-balance-subscriptions

1 messages · Page 1 of 1 (latest)

shadow atlasBOT
#

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

📝 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.

restive pecan
#

in addition, we want to allow the customers to upgrade their subscriptions. Since every customer on the platform should already have the existing free subscription, is it better to build a checkout session or a customer portal (for managing subscription and such) to allow them to upgrade? Ideally, we want to discourage people from downgrading their subscription once they've upgraded

jolly sleet
#

HI 👋

This is a pretty general question

#

Can you be more specific?

restive pecan
#

I currently have this integration built for our platform:

  • when a new user onboards to the platform, we automatically create a $0 subscription for them and internally grant credits to their account. For example, $10 subscription == 10 credits, $20 == 20 credits. When they do certain things on our platform, we then decrement credits.

  • We are currently tracking the credits internally in an internal ledger. However, I'm reading up on the credit transaction/balance API, and I realized that this API could potentially replace our internal ledger completely. Is this a valid path?

^ You're saying this is a general question?

#

Let me know what parts I can be more specific on

jolly sleet
#

"Is this a valid path" is pretty general, yes.

#

You can definitely attempt to model your business using customer credit grants

#

but it may not be suitable for some aspects you have not discussed.

restive pecan
#

I see, what info can I provide that will help you more?

jolly sleet
#

It's not up to me to say

restive pecan
#

We have an AI platform that allows customers to send queries

jolly sleet
#

It's up to you to research how the customer credit balances work

restive pecan
#

and each of these queries can be of different price points

jolly sleet
#

Are you using usage based billing?

restive pecan
#

we are not

#

we are just using flat rate billing

jolly sleet
#

okay I have a couple recommendations

restive pecan
#

and we're currently just granting a set amount of credits to the users when their invoice is paid

jolly sleet
#

I think you should start by reviewing our docs here

#

And how the Credit Balance APIs work here

#

But, and this is the most important thing when it comes to Stripe billing, I strongly recommend you build out a sample version with a Sandbox

restive pecan
#

yes I took a look at those already

#

we already are building it out, but just want to avoid having to change integrations completely down the line

jolly sleet
#

It's really easy to overlook some edge cases unless you are hitting the APIs and trying to use the responses for your integration

#

Again, I would recommend creating a quick simulation to validate the expected behavior (rather than trying to build it in to your full integration)

restive pecan
#

I hear you, but I guess I'm just asking for some general opinion since I've built out most of the billing + invoices integration

jolly sleet
#

The issue you will run into is that there is nothing preventing a user from spending more than their available credits. That is still a limit you will have to enforce on your end

restive pecan
#

Got it, thank you

jolly sleet
#

But I think you could use the Credit Balance Summary API to show your customers how much credit they have and use that to block transactions in your integration (if they try to use more than they have)