#nukesforbreakfast_docs

1 messages · Page 1 of 1 (latest)

gray gateBOT
#

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

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

humble zenith
#

hello! can you describe more of your current billing system? rate cards are a pretty new feature and are still in private preview, and my team doesn't have a lot of info on them still. most subscriptions should still be supportable via the V1 APIs

winged oracle
#

We normally have a permit fee that could be renewable on some cadence, normally annually. For example there could be an up front price of say $50 and then an annual renewal at $15. I was going to use subscription schedules to set up the first year at $50 and then every year after that at $15 until cancelled.

#

There are other items that will generate one off invoices, which are basically fines due to some adverse action of the permit holder.

humble zenith
#

yep! subscription schedules are a great way to do that

winged oracle
#

but those will not be on the subscription itself.

#

they'll be charged ad-hoc as those adverse events occur.

#

I'm currently calcuating those amounts outside of Stripe because Stripe usage based billing doesn't have any concept, as far as I can tell, of an escalating fee schedule. I.E.:

  • First false alarm in a 365 day rolling period is $0
  • 2nd is $0
  • 3rd is $100
  • 4th is $250
  • 5th and every one after in the same 365 day rolling period is $500
gray gateBOT
broken umbra
#

👋 Taking over this thread, catching up now

#

I don't fully get your latest scenario. Do you mean that you would like to have tier pricing based on the quantity in a cycle?

winged oracle
#

basically, but the cycle is moving.

#

so the false alarm event occurs at X time. I have to look at a window of all events between X time and X time - 365 days, count the number of events, and that determines the price of the most recent event.

#
  • 2025-01-01 - $0
  • 2025-02-14 - $0
  • 2025-12-31 - $100
  • 2026-02-01 - $100
  • 2026-02-13 - $250
  • 2026-03-01 - $250

etc.....

#

it's basically a lookback period.

broken umbra
#

Stripe subscription charges at a fixed interval. If the cycle isn't fixed, the only way is to use one-time invoice