>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #2908280. --> Reported by: [ndf](https://www.drupal.org/user/599438) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>commerce_mollie doesn't work well when a user cancels the payment on the Mollie website.<br> What happens is that the user will see an "Access Denied" message.<br> According to Mollie about 2% of the payments will be cancelled.</p> <p>The technical reason for this issue is that Mollie calls the onNotify() method with a 'cancel state'. In the onNotify() method commerce_mollie sets the order-status to "cancelled" via a state_machine transition.<br> Then the user lands on the onReturn() and checkout/complete page. Because the order is cancelled the user gets an "Access Denied" page.</p> <p>The Mollie API does not implement the onCancel() url.<br> See:&nbsp;<a href="https://github.com/mollie/mollie-api-php/issues/18">https://github.com/mollie/mollie-api-php/issues/18</a></p> <p>The Commerce Payment API does not handle a pending payment page, but expects either a successful payment via onReturn() or a cancelled payment via onCancel.<br> See: <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-1"><a href="https://www.drupal.org/project/commerce/issues/2864515" title="Status: Active">#2864515: Document that offsite gateways should handle both pending and successful payments in onReturn</a></span></p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>As discussed with Thomas Cys and ndf on <a href="https://github.com/DxEx/commerce_mollie/pull/4">https://github.com/DxEx/commerce_mollie/pull/4</a> we don't see a solution that can be worked out in commerce_mollie without changes to either the Mollie API or the Commerce Payment API.</p> <p><del>We hope that Mollie will change it's API so we can use the onCancel() method.</del></p> <h4>Update feedback Mollie API guys</h4> <p>See: <a href="https://github.com/mollie/mollie-api-php/issues/18#issuecomment-331119639">https://github.com/mollie/mollie-api-php/issues/18#issuecomment-331119639</a></p> <blockquote><p>Sad to hear the Commerce Payments API is pushing for a URL based feedback system, Niels. As stated above, Mollie won't introduce a cancel URL. It may solve your particular issue, but will result in a vague API that Mollie will have to live with for years to come.</p> <p>I'd advise to push the Commerce Payments API developers to mark the cancel URL as an optional feature.</p> <p><strong>If all else fails, since you're stuck between two APIs with different workflows, a last resort could be for you to introduce a layer inbetween Mollie's API and the Commerce Payments API. The middleware would then catch all webhooks and would redirect consumers to the appropriate status URL based on the async webhook status received from Mollie.</strong></p></blockquote> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <h3 id="summary-ui-changes">User interface changes</h3> <h3 id="summary-api-changes">API changes</h3> <h3 id="summary-data-model-changes">Data model changes</h3> > Related issue: [Issue #2894779](https://www.drupal.org/node/2894779) > Related issue: [Issue #2864515](https://www.drupal.org/node/2864515) > Related issue: [Issue #2934647](https://www.drupal.org/node/2934647) > Related issue: [Issue #2934653](https://www.drupal.org/node/2934653) > Related issue: [Issue #2964719](https://www.drupal.org/node/2964719)