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
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 -
If I call the same endpoint to create a payment directly using Postman, both fields do not hav daylight saving applied -
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 -
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 -
If I call the same endpoint to create a payment directly using Postman, both fields do not hav daylight saving applied -
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)
The text was updated successfully, but these errors were encountered: