Bug report
Describe the bug
Payments are sometimes returned by the API from outside the date range requested, and sometimes not returned by the api when the received date is inside the date range requested.
The API only allows a maximum of 1 year on a date range query, which means that multiple requests are required in order to fetch the full history of the businesses payments (which is required for the functionality of our product)
Due to the fact that payments may sometimes appear where their received date is outside of the date range requested and sometimes also not appear when the received date is inside it, we are unable to determine if this is the same payment record we have previously seen.
This doesn't appear to affect all businesses.
It appears that there is enough information available to provide at least a unique reference in the api response for each payment so that it would be possible to deduplicate the results we see, however, it would be much better if it only returned payments where the received date is inside the date range requested, and if all payments with a received date inside the date range are returned, then there would be no need for the additional information.
To Reproduce
Steps to reproduce the behavior:
Take todays date, and the date 1 year ago
Request all payments inside that date range.
Subtract 1 year from each date (ensuring that you do not include the previous start date as the end date, subtract 1 day if you did) and requests all payments in that range.
repeat until you reach the earliest date supported by the api
Inspect the results, you will for some businesses observe the above described behaviour.
Expected behavior
Payments to all be returned where their received date is inside the date range requested.
Payments where the received date is not inside the requested date range to not be returned.
Screenshots / Requests / Responses
Has already been provided to the SDS team via email over a month ago.
Additional context
Bug report
Describe the bug
Payments are sometimes returned by the API from outside the date range requested, and sometimes not returned by the api when the received date is inside the date range requested.
The API only allows a maximum of 1 year on a date range query, which means that multiple requests are required in order to fetch the full history of the businesses payments (which is required for the functionality of our product)
Due to the fact that payments may sometimes appear where their received date is outside of the date range requested and sometimes also not appear when the received date is inside it, we are unable to determine if this is the same payment record we have previously seen.
This doesn't appear to affect all businesses.
It appears that there is enough information available to provide at least a unique reference in the api response for each payment so that it would be possible to deduplicate the results we see, however, it would be much better if it only returned payments where the received date is inside the date range requested, and if all payments with a received date inside the date range are returned, then there would be no need for the additional information.
To Reproduce
Steps to reproduce the behavior:
Take todays date, and the date 1 year ago
Request all payments inside that date range.
Subtract 1 year from each date (ensuring that you do not include the previous start date as the end date, subtract 1 day if you did) and requests all payments in that range.
repeat until you reach the earliest date supported by the api
Inspect the results, you will for some businesses observe the above described behaviour.
Expected behavior
Payments to all be returned where their received date is inside the date range requested.
Payments where the received date is not inside the requested date range to not be returned.
Screenshots / Requests / Responses
Has already been provided to the SDS team via email over a month ago.
Additional context