magento / magento2

Prior to making any Submission(s), you must sign an Adobe Contributor License Agreement, available here at: https://opensource.adobe.com/cla.html. All Submissions you make to Adobe Inc. and its affiliates, assigns and subsidiaries (collectively “Adobe”) are subject to the terms of the Adobe Contributor License Agreement.
http://www.magento.com
Open Software License 3.0
11.54k stars 9.32k forks source link

Authorize.net DirectPost Error: Sorry, but something went wrong. Please contact the seller. #18496

Closed jayanta88 closed 4 years ago

jayanta88 commented 6 years ago

Summary (*)

We've some complaints from the customer they see an error popup saying "Sorry, but something went wrong. Please contact the seller." But order gets processed with Authorize.net DirectPost and they charged.

Information on your environment

Magento 2.2.2

Steps to reproduce

Set the authorize.net directpost method in admin with test gateway url and transaction url. Then in checkout console of chrome you can see javascript error duplicate billing id for 2 payment methods. When you will enter the test card details and place order, you will see the error but orders get processed. Now if you manually enter the url domain/checkout/onepage/success it will show you the success page with order id.

Examples (*)

We've tried to replicate the issue with sandbox account and observed the following.

  1. https://test.authorize.net/gateway/transact.dll this response is successful.
  2. Then in the network tab, we can see the last get request /authorizenet/directpost_payment/redirect/x_invoice_num/1000001457/success/1/controller_action_name/directpost_payment/is_secure/1/
  3. Then we see the error popup "Sorry, but something went wrong. Please contact the seller."
  4. In the console we see the errors: Content Security Policy: Ignoring ‘x-frame-options’ because of ‘frame-ancestors’ directive. Content Security Policy: The page’s settings blocked the loading of a resource at https://staging.com/checkout/ (“frame-ancestors”).
  5. In this scenario, if we manually go to checkout/onepage/success page it shows the success message with the order ID.

    Proposed solution

    Please let us know.

Thanks

magento-engcom-team commented 6 years ago

Hi @jayanta88. Thank you for your report. To help us process this issue please make sure that you provided the following information:

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento-engcom-team give me $VERSION instance

where $VERSION is version tags (starting from 2.2.0+) or develop branches (for example: 2.3-develop). For more details, please, review the Magento Contributor Assistant documentation.

@jayanta88 do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

jayanta88 commented 6 years ago

@magento-engcom-team give me 2.2.2 instance

magento-engcom-team commented 6 years ago

Hi @jayanta88. Thank you for your request. I'm working on Magento 2.2.2 instance for you

magento-engcom-team commented 6 years ago

Hi @jayanta88, here is your Magento instance. Admin access: https://i-18496-2-2-2.engcom.dev.magento.com/admin Login: admin Password: 123123q Instance will be terminated in up to 3 hours.

jayanta88 commented 6 years ago

I confirm that I was able to reproduce the issue on vanilla Magento instance following steps to reproduce.

  1. Set the authorize.net directpost method in admin with test gateway url and transaction url.
  2. Then in checkout console of chrome you can see javascript error duplicate billing id for 2 payment methods.
  3. When you will enter the test card details and place order, you will see the error but orders get processed. Now if you manually enter the url domain/checkout/onepage/success it will show you the success page with order id.

check your instance https://i-18496-2-2-2.engcom.dev.magento.com/simple-product.html

Thanks

jayanta88 commented 6 years ago

I had contacted with Authorize.net they said the below regarding this issue.

This error message is a message from Magento. You will want to reach out to Magento to find out why they return this message when the transaction was successful.

https://support.authorize.net/s/article/Why-Are-My-SIM-Relay-Response-Transactions-Timing-out-After-Submitting-the-Request

inkobject commented 6 years ago

@jayanta88 This thread may shed more light on your observation: https://github.com/magento/magento2/issues/12366#issuecomment-420523861

magento-engcom-team commented 5 years ago

Hi @engcom-backlog-nazar. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

magento-engcom-team commented 5 years ago

@engcom-backlog-nazar Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-96214, MAGETWO-96215 were created

jayanta88 commented 5 years ago

@magento-engcom-team any solution for this. Transaction and order get successfully but still getting the popup. Please let us know if you have any solution.

treii28 commented 5 years ago

I'm getting the same response from authorize as jayanta. Contact the magento community. Meanwhile, I have posted my issues with the patch not working to a couple of different threads, and it seems no one associated with the magento code base has even acknowledged yet on any of them that a problem even exists.

After applying the patch, removing the trans_key and the md5hash and adding a new generated signature, trying to process a payment returns a:

"The transaction was declined because the response hash validation failed"

treii28 commented 5 years ago

Someone pointed out in a similar thread https://github.com/magento/magento2/issues/21696 that the authorize console shows the payment as successful but the patched/magento plugin sees an error and thus doesn't complete the checkout.

The item is also gone from the cart.

treii28 commented 5 years ago

There is also a similar discussion on the Magento support blog: https://community.magento.com/t5/Magento-DevBlog/Authorize-Net-Direct-Post-Patch-for-M2-and-M1/bc-p/124989#M445

treii28 commented 5 years ago

anything new?

m2-assistant[bot] commented 4 years ago

Hi @ihor-sviziev. Thank you for working on this issue. Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:


ihor-sviziev commented 4 years ago

Hi @jayanta88 , According to following announcement this extension was already removed from 2.4 version: https://community.magento.com/t5/Magento-DevBlog/Deprecation-of-Magento-core-payment-integrations/ba-p/426445

All future collaboration related to this extension should be on Marketplace using "Contacts" or "Bug reports" related to this extension.

I'm closing this issue.