magento2: Magento 2.1 Authorize.net not redirecting to failure or success page after migration from 2.0.4 to 2.1
Steps to reproduce
Go to http://www.kidsafetystore.com
Add Any Product to cart
Proceed to checkout
Select Credit Card Authorize.net
Enter the below details Card No : 4111111111111111 Any Expiry Date Any CVV
Expected result
- Redirect to failure page
Actual result
- Loader just loading
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 72 (6 by maintainers)
Commits related to this issue
- Merge pull request #5642 from magento-honey-badgers/MC-33394-pr-delivery [honey] Remove MySQL search engine — committed to magento/magento2 by cpartica 4 years ago
Guys : I tried commenting the code $this->checkTransId(); in line number 689 in vendor/magento/module-authorizenet/Model/Directpost.php and it started working in server but in local its still rejecting as Magento is not responding with a patch or fix I tried to debug and this fix started working in server and for client its working and got going. I have overridden the vendor module and made a module. Please contact me for patch.
@SewHappy58 If you’ve installed Magento via Composer, then the
app/code/Magento/Payment/view/frontend/web/js/view/payment/iframe.jsfile path will be located invendor/magento/module-payment/view/frontend/web/js/view/payment/iframe.js.Keeping the md5 hash value to just 10 characters solved the issue for me.
@erikhansen, do you ever get orders in the “Pending” status within the Magento admin where Authorize.net was the payment method?
Maybe I was not clear in previous posts, in both 2.1.1 and 2.1.2 I am still getting trouble with the infinite spinner for failure scenarios (entering test visa card number for instance), but for valid credit card numbers I was able to successfully finish the payments through Authorize.net.
@jernejh Ah, that certainly is a problem. I don’t know when / if this’ll be fixed, as it was apparently fixed (as per the comments above), but there is no commit referencing this ticket. Furthermore, the dev files do not fix this issue (I’ve tried), and the last changes to the authorize.net module had nothing to do with this.
@graffxdesign That was the route that I was going to take, until my client was approved for Braintree. Heads up – it was supposed to take 24 hours, but took 5 days! 5 days of downtime. 5 days of stress, and 5 days of hearing, “I thought Magento was supposed to be good…”.
Guys – we can’t continue to recommend this platform to our clientele, when bugs are not even addressed. I understand that this is a community effort, but certainly someone could speak up on this. The “patch” mentioned above did not work for our live sites, and editing core files is not recommended anyway. What are we as developers supposed to think, when our bug reports are ignored?
Magento2.1.1 still “400 (Bad Request)” issue generate while place order using custom payment method…magneto2.1.0 in working perfect but magneto2.1.1 in getting this issue.