#Bammy_dee
1 messages · Page 1 of 1 (latest)
Your billing cycle anchor can't be more than a year into the future, if I recall correctly
yes,
but I added year 2023
Do you have a Request ID for the request?
Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
Find help and support for Stripe. Our support center provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
yes
Can you copy/paste it to the thread so I can take a look?
req_RVG7pE5B2SRmXO
Stepping in for my teammate. Looks like this returned an error because we're expecting a timestamp without milliseconds. Could you try 1681912800 for the billing_cycle_anchor value instead?
OK, let me try
waw!
it worked
please explain
difference between 1681912800 and 1681912800000?
1681912800 is in unix time, and is the number of seconds since 1/1/1970. 1681912800000 is the same date/time but in milliseconds. our systems expect unix timestamps
ohhh!
now I get
thanks
sure thing!