We need a solution to address both of the following problem/issues, which are new as of moving our web presence over from American Eagle to Magento. The issues were not present on web implementations of WooCommerce (Drake) or the old American Eagle site (which we know was a proprietary development).
Since we are on Magento v2.1.7 and the software is now up to v2.2.2, we would like for your team to first look into a possible implemented fix via a newer Magento version. If there is a fix, we will need to discuss the best route to take to upgrade the software. As an aside, Monica has already made us aware about changes from v2.1.7 to 2.2.0 was being major and that the update won’t be as simple as compared to WordPress or Woocommerce updates.
If there is no fix, we will need to know our options to move forward with fixing the problem. Also, if there are any other possible solutions to alleviate these issues for our company, please let us know those options.
Breakdown of the Problems/Issues:
The way Magento behaves with how it is coded in handling Paypal, causes the following:
The flow of how it happens seems to be as follows:
We believe that the two issues are related somehow but need your team to check into it. As it happens, I did some preliminary research to ensure that Paypal was set up properly according to Magento guide: http://docs.magento.com/m2/ee/user_guide/payment/paypal-payflow-pro.html
We also found the link below detailing and alerting us to similar issues which resulted in the extra charges. Prior to this, we only knew about the fraud filter and zero amount issues. The below link shows that it is not an isolated issue:
Can you please advise on a fix or possible workaround to this issue.
Did you get a response to fix this? My client is complaining about the same issue on our Magento 2.2.2 website.