-
Notifications
You must be signed in to change notification settings - Fork 131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BrowserInfo.TimezoneOffset type #2719
Comments
Hey @mderasse , Sorry for the delay getting back to you here. It is weird that you are getting different types for the I tested through BrowserStack different Edge versions (122, 124, 125, 126) and they are all returning as |
I was able to list a few user agent based on the payload the adyen component return.
|
Hi @mderasse , Thanks for sharing the browser list. We tested in different browsers as I mentioned above, and we always get the If you are able to reproduce in any browser and you can show us that the value is not being returned as Integer, we can re-evaluate this and perhaps add a strict cast on our side. Cheers |
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: