Magento2: Authorize.Net Direct Post causing orders to be marked as pending, no transaction posted

Created on 6 Jan 2016  Â·  25Comments  Â·  Source: magento/magento2

An order popped up today with the status "Pending" but payment method set to Authorize.Net Direct Post. A search through transactions and declines on Authorize.net did not show a transaction attempt. Mail logs show that an email was sent out to the customer.

After doing some research and combing through stackexchange, I have a feeling that this is related to antivirus software on visitor's systems intercepting the form post in the iframe. Checkout treats it as a successful send and creates the order but there's never a response from Authorize.net.

Are there any plans to migrate the Authorize.net AIM implementation from Magento 1 as an alternative option to DPM? For the long term, finding a viable workaround for antivirus intercepts on DPM would be valuable as well.

Format is not valid needs update

Most helpful comment

@modern I definitely agree. This issue based on my experience is isolated to authorize.net direct post. Magento 1 is having the same issue. I believe there is a core flaw in the architecture of this module that's been around for many years now. I do agree that Magento should look at this. Magento is an ecommerce platform where everything culminates at checkout, the fact that Magento doesn't jump onto this issue as priority 0 is painful.

All 25 comments

Hi @tigerx7

DPM allows easier PCI compliance compared to AIM implementation. Can you submit your antivirus software that is blocking the form so we can reproduce the issue?

This post goes into further detail about the issue: http://magento.stackexchange.com/questions/19826/authorize-net-direct-post-sometimes-fails-in-chrome

Of the end users I've been able to get a hold of, most of them aren't really that computer literate. They know they have antivirus software on their system, but they're really not sure which one. It's usually whatever comes bundled or whatever a PC repair shop / some kid installed for them.

Internally here I haven't been able to reproduce it (just using Windows Defender), but I haven't quite taken the plunge in convincing myself to install those third-party bloated antivirus software packages on my system for testing.

Hi,

We've created MAGETWO-49139 internal ticket regarding this issue

Hi,
We've delivered https://github.com/magento/magento2/commit/e9e74ada55c9d287d86f322ec834a76161b5d8c6 code changes that might solve the issue with blocking by antivirus software to develop branch. Please verify if this solves the issue. If the issue still exists, please provide us with information regarding antivirus software used by customers for us to be able to investigate this further.

Closing this issue due to no response, please reopen when you have an update.

Could we re-open this issue? We are using 2.0.7 with php 7. We get pending orders at random times - perhaps 5 a week...so authorize.net has no record of the auth only transaction.

It does not look like the customer is e-mailed because we don't get the e-mail. I have set to send us the same confirm e-mail and we don't get an e-mail copy. However, the order does show up in our system under pending...all their information is in the system.

We are having same issue in magento 2.1.7. @plentyhappy, were you able to find solution or figure out what the issue is?

Same issue here. 2.1.7, turning off anti-virus doesn't help. No response from Authorize.net. Anyone have a solution? I'm getting tired of M2 checkout issues.

@mjf10. I agree, I haven't tested this in 2.2 rc-x yet, but it would be nice to get acknowledgement if this was solved, addressed or nothing happened. Since this is an out of box implementation and subsequently makes Magento look bad. @magento do you plan on protecting your brand or doing nothing. This issue caused me to lose a well respected client because an agency was blamed for a core issue.

We are at 2.1.8 and, for a while, this issue really affecting our sales and reputation. On average our every third sale is lost to "pending" status bug. With such big magento 2 community, I surprise this issue affecting only this few participating people in the thread.
I read some band-aid workarounds, like creating loop requests, switching from built-in direct post to normal. Can someone please suggest any 100% solid fix? I really hate the idea of start looking and learning a different framework, so much time already invested, but this issue is not something we can continue live with.
I think payment option part of any eCommerce frameworks should be polished, solid, bugs free and the #1 priority on the bug list. If people can only browse through products and CAN'T buy anything, than it just defeats a purpose of eCommerce part, and it as good as info WordPress site.

@modern I definitely agree. This issue based on my experience is isolated to authorize.net direct post. Magento 1 is having the same issue. I believe there is a core flaw in the architecture of this module that's been around for many years now. I do agree that Magento should look at this. Magento is an ecommerce platform where everything culminates at checkout, the fact that Magento doesn't jump onto this issue as priority 0 is painful.

@moderncodes Does this issue resolved? Any updates?

Any updates? Actually, I have contact with Authorize.net Support .. she replies "Actually I am showing you said you are using Direct post method, that is no longer available. Your developer would need to set up Accept.js"

http://developer.authorize.net/api/reference/features/acceptjs.html

Please check the below link. same issues in facing.

https://mage2.pro/t/topic/4465

We're experiencing this with 2.1.9 as well. When looking in the sales_order table it looks like the customer is emailed. We've yet to confirm with a customer, but everything in the DB suggests that they have. We were also set to receive a copy of the order confirmation email, but never received them.

I am using magento latest version 2.2.5 and configured the Authorize.net direct post method as payment method. when I tried to placed an order it saves the order in admin with pending status but after placed the order didn't redirect to success or failure page please any one can advice on this issue.

{success: true, authorizenet_directpost: {,…}}
authorizenet_directpost: {,…}
fields: {x_version: "3.1", x_delim_data: "FALSE", x_relay_response: "TRUE", x_test_request: "TRUE",…}
controller_action_name: "directpost_payment"
is_secure: "1"
x_address: "8778 High Ridge Drive"
x_amount: 1329.31
x_city: "Brooklyn"
x_company: "Test Company"
x_country: "US"
x_currency_code: "USD"
x_cust_id: ""
x_customer_ip: "111.11.11.111"
x_customer_tax_id: ""
x_delim_data: "FALSE"
x_email: "[email protected]"
x_email_customer: "0"
x_fax: ""
x_first_name: "Jag"
x_fp_hash: "d4594a75aab8b43f31136e3699409363"
x_fp_sequence: "51"
x_fp_timestamp: 1536640689
x_freight: "0.00"
x_invoice_num: "000000034"
x_last_name: "Ram"
x_login: "48nL9pR49pEb"
x_merchant_email: "[email protected]"
x_method: "CC"
x_phone: "01234567890"
x_po_num: ""
x_relay_response: "TRUE"
x_relay_url: "https://domain.com/authorizenet/directpost_payment/response"
x_ship_to_address: "8778 High Ridge Drive"
x_ship_to_city: "Brooklyn"
x_ship_to_company: "Test Company"
x_ship_to_country: "US"
x_ship_to_first_name: "Jagdish"
x_ship_to_last_name: "Ram"
x_ship_to_state: "New York"
x_ship_to_zip: "11206"
x_state: "New York"
x_tax: "101.31"
x_test_request: "TRUE"
x_type: "AUTH_CAPTURE"
x_version: "3.1"
x_zip: "11206"
success: true

I am also having same issue with Magento 2.2.5, Is there any updates on the issue?

I have faced this issue once. My session data was empty. I corrected it and
then the issue is resolved.
Nanthini Muralidaran
LeanSwift Solutions Inc.

Phone: +91-9524738428 <+919524738428>
Skype: nanthini.muralidaran
Slack: nanthini.muralidaran

We know Infor ERP | eCommerce & Mobile for Infor M3 | Partners Infor M3
Marketplace https://www.inform3marketplace.com/

On Fri, Oct 5, 2018 at 6:35 PM saurabhgwb notifications@github.com wrote:

I am also having same issue with Magento 2.2.5, Is there any updates on
the issue?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/magento/magento2/issues/2904#issuecomment-427359026,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARE4sn9nXBIjz0clujGPukr3KfGYprJKks5uh1kMgaJpZM4G_6M7
.

--
This message originates from LeanSwift, Inc and may contain confidential
information intended solely for the use of the addressee. If you are not
the intended recipient and have received this message in error, please
notify [email protected] admin@leanswift.com and delete this
message from your system. Any unauthorized reading, distribution, copying,
or other use of this message or its attachments is strictly prohibited. All
personal messages express solely the sender's views and not those of
LeanSwift, Inc. This message may not be copied or distributed without this
disclaimer.

@NanthiniMuralidaran cleared the cache many times but no luck.

Below is the message showing under the console in Request URL: https://test.authorize.net/gateway/transact.dll

"The reporting of this transaction to the Merchant has timed out. An e-mail has been sent to the merchant informing them of the error. The following is the result of the attempt to charge your credit card.       
This transaction has been approved.

It is advisable for you to contact the merchant to verify that you will receive the product or service."

Did you check all the post values from your form? Check if anything is
missing.For me customer data session in magento got empty then I fixed it

On Sat, Oct 6, 2018, 12:51 PM saurabhgwb notifications@github.com wrote:

@NanthiniMuralidaran https://github.com/NanthiniMuralidaran cleared the
cache many times but no luck.

Below is the message showing under the console in Request URL: https://test.authorize.net/gateway/transact.dll
https://test.authorize.net/gateway/transact.dll

"The reporting of this transaction to the Merchant has timed out. An
e-mail has been sent to the merchant informing them of the error. The
following is the result of the attempt to charge your credit card.
This transaction has been approved.

It is advisable for you to contact the merchant to verify that you will
receive the product or service."

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/magento/magento2/issues/2904#issuecomment-427552938,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARE4sl_5WzOSWOp_bMfOLw7Lv1RImccWks5uiFoWgaJpZM4G_6M7
.

--
This message originates from LeanSwift, Inc and may contain confidential
information intended solely for the use of the addressee. If you are not
the intended recipient and have received this message in error, please
notify [email protected] admin@leanswift.com and delete this
message from your system. Any unauthorized reading, distribution, copying,
or other use of this message or its attachments is strictly prohibited. All
personal messages express solely the sender's views and not those of
LeanSwift, Inc. This message may not be copied or distributed without this
disclaimer.

I also see this issue about once a day on our website. It looks like direct post has been deprecated. Is there an effort to move to the Accept.js implementation going on?

Authorize.Net itself does have a free extension that supports Accept.js, and I've been trying to get it to actually work on my store: https://marketplace.magento.com/authorizenet-magento-module-authorizenet.html

@lewisje Did the extension worked for you?

It didn't at the time, and we went ahead and purchased the extension by Paradox Labs; the extension by Authorize.Net has not been updated since I tried it out, so I doubt it will actually work now.

I could not get the extension to work. I switched from Authorize.net http://authorize.net/ to Braintree and have not had the problem again.

Mike

On Apr 9, 2019, at 2:43 PM, Vignesh notifications@github.com wrote:

@lewisje https://github.com/lewisje Did the extension worked for you?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/magento/magento2/issues/2904#issuecomment-481380240, or mute the thread https://github.com/notifications/unsubscribe-auth/AdYZAIVzqVp63lQFBDTnYpt99GzdVB8pks5vfN89gaJpZM4G_6M7.

Was this page helpful?
0 / 5 - 0 ratings