#deadshot-sub-payment-timing

1 messages · Page 1 of 1 (latest)

formal socketBOT
#

Hello! We'll be with you shortly. 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.

haughty jacinth
crisp thorn
#

I mean, I have a weekly subscription and I want to charge customer on every sunday at 01:00 pm for example, can I do that?

haughty jacinth
#

Sorry, misunderstood. 😅

crisp thorn
#

np

crisp thorn
haughty jacinth
#

Yep, that's correct. You supply a Unix timestamp to set the date and time of the billing_cycle_anchor to your desired value.

formal socketBOT
crisp thorn
#

But every charge has different timestamp, I mean

haughty jacinth
#

For example, if I wanted to set it to Feb 15th at 1:00 PM UTC I would set that value to 1708002000.

#

That sets the billing cycle anchor for the next period, and then the interval determines the next payment.

#

To extend the example, if I set 1708002000 on a monthly Subscription, that would mean future payments would happen on the 15th of every month at roughly 1:00 PM UTC.

#

If I set 1708002000 on a yearly Subscription, it would be Feb 15th at 1:00 PM UTC every year.

crisp thorn
#

And for weekly subscription?

haughty jacinth
#

It would be 7 days between each payment.

crisp thorn
#

It would be Feb 22nd at 1:00 PM UTC?

haughty jacinth
#

Yep.

crisp thorn
#

Yeah I got it, thanks

haughty jacinth
#

You can speed up time so you don't have to wait for 7 actual days to pass.

crisp thorn
#

Yeah, its great, i am using it already