#raghul-s_docs

1 messages ¡ Page 1 of 1 (latest)

strange aspenBOT
#

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

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

wet meteor
abstract granite
#

billing_cycle_anchor_config
only valid with monthly and yearly price intervals
Can specify charging time at the seconds level, right?

billing_cycle_anchor:
takes in the current UTC time
execute at start of the day. is it?

wet meteor
#

Unix time is a date and time representation widely used in computing. It measures time by the number of non-leap seconds that have elapsed since 00:00:00 UTC on 1 January 1970, the Unix epoch. For example, at midnight on January 1 2010, Unix time was 1262304000.
Unix time originated as the system time of Unix operating systems. It has come to be...

abstract granite
#

billing_cycle_anchor_config - Once we set the date config, it works for intervals.

billing_cycle_anchor: We need to set the future UTC timestamp whenever the subscription has to be charged. Is this one time use? Once executed, what will be the billing date time for next billing?

wet meteor
#

For example if you set billing_cycle_anchor to 10 Nov 1:32PM and the billing interval is monthly, your customer will be billed at

  • 10 Nov 1:32PM
  • 10 Dec 1:32PM
  • 10 Jan 2025 1:32PM

And so on

abstract granite
#

Then both billing_cycle_anchor_config & billing_cycle_anchor does the same. Only difference is the way we provide the input. Am I correct?

wet meteor
#

Yes you are right

strange aspenBOT