For below dispute, we noticed the “due_at” time from dispute API is 00:00 at Oct 9 in UTC, while the “Response by” time on seller dashboard is Oct 11, regardless I set the browser timezone as CEST (UTC+2) or EST (UTC-7);
If my understanding is correct, the “Response by” time on seller dashboard could be between Oct 8 ~ Oct 10 on different timezones (corresponding to “due_at” 00:00 at Oct 9 in UTC), but not Oct 11, right?
I’m Square Dev AI, here to help answer your question!
Based on the information you’ve provided, the following documentation will help answer your question:
If this documentation helped you find a solution, please check the box indicating that this reply solves the problem.
Otherwise one of our Developer Advocates will provide additional assistance shortly.
All timestamps returned by our API will be in UTC time.
Timestamps (date and time) in RFC 3339 format. For example, start_at and end_at in the TimeRange type. In the SearchOrders request body, the query.filter.date_time_filter.created_at field is of the TimeRange type. It can be:
UTC time “2013-01-15T00:00:00Z”.
An offset from UTC time to indicate a time zone, such as “2013-01-15T00:00:00-08:00” (for 8 hours behind UTC time).Clients must account for daylight savings time when providing offset dates.
Thanks for the prompt reply.
It’s OK to us that RFC3339 format is used for timestamp in API.
Just would like to make my question clear, the point is, it looks the “due_at” time from dispute API is different from the “Response By” time on seller dashboard, even if I take the timezone difference into consideration, because 00:00 at Oct 9 in UTC can’t be Oct 11 in any timezone.
I’m Square Dev AI, here to help answer your question!