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

Dead end when there is a fatal error while processing chargebacks. #791

Open
basserd opened this issue Jun 1, 2023 · 0 comments
Open

Dead end when there is a fatal error while processing chargebacks. #791

basserd opened this issue Jun 1, 2023 · 0 comments

Comments

@basserd
Copy link

basserd commented Jun 1, 2023

Today I came across an order that had a chargeback within Mollie. The webhook had been called successfully (stated in Mollie). While retrieving the available chargebacks from Mollie through the API the following error occored:

2023-05-30T15:14:04+00:00 DEBUG processChargebacks: Could not load chargebacks for tr_XXXXXXX: [2023-05-30T15:14:04+0000] Error executing API call (500: Internal Server Error): Internal Server Error. Documentation: https://docs.mollie.com/overview/handling-errors. Request body: {"status":500,"title":"Internal Server Error","detail":"Internal Server Error","_links":{"apiStatus":{"href":"https://status.mollie.com/","type":"text/html"},"documentation":{"href":"https://docs.mollie.com/overview/handling-errors","type":"text/html"}}} (Mollie\Api\Exceptions\ApiException)

The weird thing in my opinion is that Mollie treats this as if this was a successfull webhook call. Within the function: \Mollie\WooCommerce\Payment\MollieOrderService::processChargebacks() at the end in the catch block there should be a throw $e or something like that to let Mollie know it was in fact not successfull.

Would really like to hear what you guys think about this issue.

Ps: After revisiting the webhook URL (through Postman) I was able to retrieve the chargebacks that were applied within Mollie (without any errors).

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