.letscode | Stripe Developers | Page 1

maiden sailBOT Jul 25, 2023, 10:44 AM

#

somber spoke Jul 25, 2023, 10:44 AM

#

even i set the timestamp value 1692057600

#

Hi there!
Can you share the ID (req_xxx) of the failing API request?
https://support.stripe.com/questions/finding-the-id-for-an-api-request

frigid void Jul 25, 2023, 10:44 AM

#

req_VENhQsVSfSiWs3

#

{
"backdate_start_date": "1689379200",
"items": {
"0": {
"price": "price_1NXifcFG3Dh3H5V4O75ThBWJ"
}
},
"customer": "cus_OKNQjpBmzWCvFH",
"payment_behavior": "default_incomplete",
"payment_settings": {
"save_default_payment_method": "on_subscription"
},
"billing_cycle_anchor": "1692057600",
"expand": {
"0": "latest_invoice.payment_intent"
}
}

#

any luck?

somber spoke Jul 25, 2023, 10:52 AM

#

Thanks for sharing, checking...

frigid void Jul 25, 2023, 10:58 AM

#

ok

frigid void Jul 25, 2023, 11:13 AM

#

any luck with this?

somber spoke Jul 25, 2023, 11:14 AM

#

Yes,

#

Your customer is attached to a test clock 2031-05-05 12:20:00 while the future timestamp you are passing is 2023-08-15 00:00:00 UTC

frigid void Jul 25, 2023, 11:16 AM

#

test clock is for testing future date and what is the max date

#

and billing cycle anchor is for next invoice date

#

both are different. Right? i'm missing anything?

somber spoke Jul 25, 2023, 11:18 AM

#

Yes, but here the customer is attached to a test clock, so you need to pass future dates according to that test clock .

frigid void Jul 25, 2023, 11:20 AM

#

you mean same date for billing cycle and test clock?

somber spoke Jul 25, 2023, 11:23 AM

#

no, the billing cycle must be considered in the future comparing to test clock

#

in other words, in your use case, billing_cycle_anchor must be in the future comparing to 2031-05-05 12:20:00 of the test clock

frigid void Jul 25, 2023, 11:26 AM

#

Okay

#

got it

#

thank you

#.letscode