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

Decline Adobe Commerce orders is not possible in case Adyen Notifications is not processed #138

Open
serhii-petrychenko-vaimo opened this issue Oct 16, 2024 · 0 comments

Comments

@serhii-petrychenko-vaimo

In case an Adobe Commerce order is placed by using the Adyen payment method and the order status is changed to the one that can't be held by checking in that place

That leads to the impossibility execute

$this->setMessage($order, 'decline', $forterEntity);
what prevents the Forter entity being updated with correct entity type with value order
$forterEntity->setEntityType('order');
.
As a result, this Ferter entity will not be selected to be processed on the PostDecisionActions cron run here
$items = $this->entityHelper->getForterEntitiesPostDecisionAction();
.

At the same time when is used to force order-holding configuration

if ($this->forterConfig->forceHoldingOrders() && !$order->canHold()) {
the Adyen Authorization webhook that is created on the Adobe Commerce side can't be processed when the order is held. This is stuck in processing status and does not finish updating all Adyen DB tables with the necessary data to be used in the PostDecisionActions cron run.

Could you please fix the logic that allows to execution decline handler on the Adobe Commerce side only in the case when Adyen Authorization webhooks are processed and all data from Adyen is successfully placed in DB?

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