Skip to content

createdDate for createPayment has Daylight Saving applied  #204

@mikesmith-createfuture

Description

@mikesmith-createfuture

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)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions