#archie_best-practices

1 messages ¡ Page 1 of 1 (latest)

sharp frigateBOT
#

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

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

wild bridge
#

inviting @ripe timber

shadow saddle
#

hello! looking at this now

#

hmm, i'm digging into this a bit more and i don't think we have a super clean way of supporting this. the best option might just be to create a monthly subscription and then to use some reference point (metadata on the subscription or the billing_cycle_anchor or something like that) to instruct your application when to give them more "credits"

#

can you share more about your subscription? what exactly are the credits? are they just something you're tracking on your side?

sharp frigateBOT
ripe timber
#

Our current subscription consists of a yearly flat fee price (3000$) + usage based graduated tiered price (with $XX worth of credits included for free)

#

The credits are just measured via meters

#

Ideally, we could keep everything the same, except charge monthly (as like a yearly commitment-based subscription)

lilac path
ripe timber
#

We're already using flexible billing subscriptions

lilac path
#

Ah I see. Sorry about the confusion.

For a monthly invoice, you need to have a monthly subscription. You could model it as a yearly sub in your application but on Stripe it can't be considered an "annual" subscripition as such

ripe timber
#

I see. Thanks for the help! Are there any plans on the Stripe future roadmap to support subscription commitments? (This seems like something a lot of companies & startups would love to see!)

lilac path
#

I'm not sure I fully understand the usecase but let's take a step back..
A monthly subscription goes on until it's cancelled so I don't fully grasp how it's different from an annual subscription that you charge monthly?

Are you looking for a Subscription that ends after that "commitment" period i.e. 12 months? If so, we do have Subscription Schedules API

#

Like what I'm trying to understand is - how is a $3000 "annual" subscription that you'd charge monthly different from $250 monthly subscription?