search

craftcms / commerce-mollie

Mollie payment gateway for Craft Commerce.
https://plugins.craftcms.com/commerce-mollie
MIT License
5 stars 10 forks source link

Mollie test payment page returns to the site only for "paid" payment status #25

Closed nikolenko-dmitriy closed 3 years ago

nikolenko-dmitriy commented 4 years ago

When there is more than 1 payment method, mollie handles correctly status "paid" only, with the redirection to the original website. For any other payment status selected it only returns to the general page with the list of available methods without any additional message.

Tested with "Test API key" on 2 different mollie accounts and I have got the same result in both cases.

Details: Craft CMS Version 3.4.17.1 Craft Commerce Version 3.1.3 Mollie for Craft Commerce Version 2.1.1

jornwildenbeest commented 4 years ago

When will this issue be addressed?

nfourtythree commented 3 years ago

Hi All

I was just wondering if someone could give me a little bit more information on what is happening.

A video or steps to reproduce would be great.

I have just tried to reproduce the issue with the latest version of Commerce and the example templates and couldn't see any issues. Here are my findings for the statues:

Open

Remains on the mollie page as expected (webhook is not called, as stated by the mollie docs)

open - The payment has been created, but nothing else has happened yet. This is not a status Mollie will call your webhook for.

Paid

Redirects to the site and completes the order.

Failed

Redirects to the site with appropriate "failed" error message. A failed transaction is recorded.

Canceled

Redirects to the site with appropriate "canceled" error message. A failed transaction is recorded.

Expired

Webhook is triggered and a failed transaction is recorded. User remains on Mollie.

nfourtythree commented 3 years ago

Hi All,

With no further information, we are going to close this issue.

If you find specific steps to reproduce this issue with the latest version of Commerce and this plugin please update this issue with those steps.

We can then reopen the issue and investigate.

Thanks.