You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the other end the golang SDK (https://github.com/Adyen/adyen-go-api-library) is expecting a Integer but from time to time the Adyen Component is returning that information as a string creating complexity and inaccurate information.
Expected behavior
Adyen component should probably always return that information as an integer
It is weird that you are getting different types for the browserInfo.timeZoneOffset property. We just call the built-in browser defined method of the Date object, getTimezoneOffset. This returns a number. We don't do any further manipulation of that field.
I tested through BrowserStack different Edge versions (122, 124, 125, 126) and they are all returning as Integer.
I am not sure what can be causing this function to return a string type in your case. Do you have more information about which browsers/versions are returning this as 'string', besides the Edge ones that I mentioned?
Describe the bug
Hello,
The adyen documentation is not really clear on the browserInfo.timeZoneOffset type on /payments API.
API explorer show that it should be an integer
https://docs.adyen.com/api-explorer/Checkout/71/post/payments
and
https://docs.adyen.com/online-payments/3d-secure/api-reference/
is showing it as a string.
On the other end the golang SDK (https://github.com/Adyen/adyen-go-api-library) is expecting a Integer but from time to time the Adyen Component is returning that information as a string creating complexity and inaccurate information.
Expected behavior
Adyen component should probably always return that information as an integer
BrowserInfo
The text was updated successfully, but these errors were encountered: