Skip to content
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

createdDate for createPayment has Daylight Saving applied #204

Open
mikesmith-createfuture opened this issue Sep 28, 2023 · 0 comments
Open

Comments

@mikesmith-createfuture
Copy link

When calling createPayment on the Hyperwallet class here -

https://github.com/hyperwallet/java-sdk/blob/master/src/main/java/com/hyperwallet/clientsdk/Hyperwallet.java#L2251

The returned response HyperwalletPayment contains two fields - createdDate and expiredDate.

The created date field has daylight saving time applied so is one hour ahead. expired field doesnt have this applied - see screenshot -

image

If I call the same endpoint to create a payment directly using Postman, both fields do not hav daylight saving applied -
image

In fact, if you look at line 163, you can see that the initial response (Reponse) has the two fields returned both with no dalylight saving applied. But once the processResponse method has been called, daylight saving is appleid to createdDate -

https://github.com/hyperwallet/java-sdk/blob/master/src/main/java/com/hyperwallet/clientsdk/util/HyperwalletApiClient.java#L163

I would expect the SDK and the direct call to Hypewallet to both return the createdDate in the same format (probably with no daylight saving applied)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant