topic Re: Time Zone setting in Account does not affect Created Date for ARB Subscriptions in Integration and Testing

Time Zone setting in Account does not affect Created Date for ARB Subscriptions

kevinreedspeak — Thu, 03 Mar 2016 21:30:48 GMT

I am currently creating ARB subscriptions via the dotnet sdk.

I am located in CST.

My sandbox is setup with Time Zone UTC. When I create a ARB subscription via the API, the "Created Date" ends up being -6hrs my current time. ie if I submit one at 14:00 CST, it shows up as "Created Date" 08:00(-6hrs).

If I change the system time zone to CST, the same thing happens. If I create a ARB subscription via the API with the system time zone set as CST at 14:00 CST it shows up in the ARB list as being created at 08:00(-6hrs).

Even weirder is that this morning my auth.net system time zone was set to CST. I created a ARB subscription via the api at 09:00 and it showed up in the ARB list as being created at 15:00!!! (+6hrs) How is this possible?

How do I make sure that the system has the correct time zone for my subscription creation dates?

Re: Time Zone setting in Account does not affect Created Date for ARB Subscriptions

RaynorC1emen7 — Thu, 03 Mar 2016 23:24:06 GMT

http://developer.authorize.net/api/reference/#recurring-billing-get-a-list-of-subscriptions

there response is always in UTC

And we don't pass the created datetime, it whatever datetime on authorize.net server, and not your pc/account settings.

Re: Time Zone setting in Account does not affect Created Date for ARB Subscriptions

kevinreedspeak — Fri, 04 Mar 2016 13:46:42 GMT

Ah ok, I see the subscription "Created Date" is always in UTC. Thanks