As the screenshot above, the actual refund status should be 'succeeded', but received 'failed' at the first request of /v1/refunds.
Then I request the /v1/refunds/{refundID} immediately, and the status turned to 'succeeded'.
Please fix this bug for production! there's no issue with sandbox tho.
Meanwhile, I find out that the e-commerce private token is changing every time I view it. Please give a notice for that to avoid unexpected accidents.
You are posting a refund, we are returns failure, then when you immediately retrieve it we return a success? How often does this happen? Is your integration for multiple clover merchants?
This is happening because you are using a test merchant (which is blackholed, e.g. hitting a fake gateway that blindly approves everything). This isn't happening for real merchants. I have written up a ticket but it isn't going to be a high priority because it is not impacting real merchants.
Understood. Thank you for your response. My suggestion is that at least keep all the JSON responses in the formatted form (succeed format and fail format). For example, in this case, the payment and refund are not really processed based on your explanation. So the response should be formatted in a failed format with an error and message in it. Otherwise, as a developer, we need to handle the extra case that happens only in this special situation which would not happen in both production and sandbox.
2 People are following this question.
