2

I recently applied the latest security patches on the website which went successful. But after the patches, we found that we are not able to capture the funds now. We can authorize the payment, but when clicking on capture in Invoice it gives "Gateway error: Credit card is required". I cross-checked the log response with our earlier successful captures and found that x_type in the request was going as prior_auth_capture whereas now it's going as auth_capture. I think this is the reason of fail, how to send the request to capture as prior_auth_capture?

Any ideas what could be wrong. Note that we have not changed any config settings or anything, just applied last few patches that's it.

  • I encountered the same issue. Tracked it back to applying the security patch. In the Admin console it says "Order was placed using USD" instead of the usual x'd out CC information. Adding notes to this to see if it helps resolve. Here is a similar thread on the Magento forums, but not sure if the solution mentioned is a good path: community.magento.com/t5/Security-Patches/… – coreyg Oct 18 '16 at 2:50
  • It looks like they have resolved this issue with a v2 of the patch. Here are the instructions on the patch site: NOTE: if you have installed version 1 of the patch, it is recommended to do the following: Revert SUPEE-8788 v1/ Revert SUPEE-1533 (if installed) Install SUPEE-3941 (if not installed yet) Install SUPEE-8788 v2 magentocommerce.com/… Going to try this out. – coreyg Oct 18 '16 at 3:18
  • I already tried the solution mentioned in that thread without any luck. Thanks for the update on v2 of the patch, i installed v1. I will try out v2 and see if that resolves. Thank you very much coreyg! – Kalpesh Oct 18 '16 at 3:24
  • I just tried the v1 revert and applied the v2 patch. This resolved the issue of "Order was placed using USD" just showing instead of the CC info. I'm going to monitor for the next transaction to see if it resolves the problem. – coreyg Oct 18 '16 at 3:41
  • Great. I am getting errors when applying patch 8788 v2, will update you once done. – Kalpesh Oct 18 '16 at 4:06
1

Resolved. The issue was with SUPEE-8788 v1 patch. After going through the steps to remove SUPEE-8788 v1 and install SUPEE-8788 v2 patch from here, the issue was finally resolved for all the NEW orders. For all the old orders, we had to manually settle them.

Steps to revert patch v1 and install v2:

NOTE: if you have installed version 1 of the patch, it is recommended to do the following:
Revert SUPEE-8788 v1/
Revert SUPEE-1533 (if installed)
Install SUPEE-3941 (if not installed yet)
Install SUPEE-8788 v2
  • Worked for me as well – coreyg Oct 19 '16 at 13:43

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.