-
Notifications
You must be signed in to change notification settings - Fork 25
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
Explanation of error "There is no authorised Adyen payments for this order" requested #603
Comments
Hi @Gugiman , Thank you for reaching out to us. We would like to clarify that we cannot guarantee compatibility with third-party plugins or custom systems. Since we don’t have visibility into your refund system or its implementation, could you please provide us with more information? Specifically:
This information will help us better understand the situation and investigate further. Thank you in advance for your cooperation. Best regards |
We just use your RefundService()->refund() Method. We do not change your process of notifications etc. I cannot give you informations about number 3 because this is basically my question :) |
Hi @Gugiman , The error message "There is no authorised Adyen payment for this order!" occurs when the Adyen plugin cannot find a payment record for the order you are trying to refund. The plugin searches for the payment record in the adyen_payment database table using the last order transaction ID for the given order. You can find more details by checking the \Adyen\Shopware\Service\AdyenPaymentService::getAdyenPayments method implementation. If this method does not return any records, the error will appear. This issue can occur if:
Please let us know if you need further clarification. Best regards |
Hi,
we have developed our own refund system for Shopware which uses the refund services of this plugin.
Unfortunetly, we often get this error :
"There is no authorised Adyen payments for this order!"
In this moment, the payment status of that order is already succesfully switched to "paid".
So I assume that everything worked like it should.
Can you pleasy explain to me, what causes this error?
The text was updated successfully, but these errors were encountered: