Authorize.net

DO NOT UPDATE - DO NOT UPDATE - DO NOT UPDATE

Presently manual draft orders are not working. All subscription services do not see Authorize.net anymore, so all your subscriptions will fail. We verified this using two different Subscription services on Shopify today. This isn't an update, it is a downgrade. You will be looking for a new credit card system to allow subscriptions. All your current subscribers will need to resubscribe which is a nightmare, since many subscribers had unique prices and plans. So this will need to be done manually by calling each individual subscriber and somehow providing some coupon that matches the exact amounts they had previously. When I say, this is a nightmare... I am not kidding. If you have a large subscription base, your sales will be destroyed until you get people back up on another system in a manual fashion. I have been dealing with Authorize.net, Shopify and this insanity for a couple of days and nobody provides a solution after your subscriptions start failing. What a massive failure. Both Bold Subscriptions and Seal Subscriptions do not work after this update. Others report ReCharge does not work either. We suspect many others do not work as well.

App does not report transaction data properly since the new migration including 0 access to any of the fraud filters that were always made available. Also, none of our settings in the fraud detection suite are working anymore and shopify/authorize.net are processing all orders, even if the settings we have set up are to automatically decline. As another reviewer pointed out, shopify says its authorize.net, and authorize.net says its shopify so we cannot get the issue fixed as neither is willing to take any responsibility. Would recommend switching to another gateway if you want to avoid this whole headache.

Since migrating to the new connector, you can not process a credit card against a manual order in the backend. It will fail every time with "Enter a valid credit card". There are no issues on the customer facing side.

Also, none of the CVV or AVS checks are being passed back to the Shopify order. You have to look in the Authorize_net gateway for all fraud screening now on every order. Also, without any AVS or CVV information in the order, any Shopify Flows you have setup to screen orders are useless.

Even the logged event in the order timeline under "Information from the gateway" now only shows a payment id with nothing else.

This needs to be fixed ASAP.

We upgraded to the newest Authorize.net app since previous one will be discontinued this month. Manual orders doesn't work. You need to fix this asap! We have manual orders! This is a must feature. When we try to process the card it shows as "Enter a valid card number"

This is nonsense! Please fix it.
I tried with several cards but for manual orders this doesn't work!!

Upgrading from the old Authorize.NET gateway to this app seems to have negatively affected the transaction level data available via the Shopify API. When using the last version of the Authorize.NET payment gateway, we were able to obtain the 10-digit transaction ID generated by Authorize.NET. Once the new plugin was installed, the field now contains the value of NULL, and we cannot cross reference transactions between the 2 systems (Shopify & Authorize.NET) in an automated way.

Also, we cannot revert back to the old gateway, so we now have to reconcile transactions between the 2 systems using a completely manual, time consuming process.

The Shopify API call we rely on is: https://{{our store id}}.myshopify.com/admin/api/2024-04/orders/{{our order id}}/transactions.json, which provides a JSON response with the following 2 key fields in it (shown for requests both before and after the upgrade).

Here is a snippet from JSON response before the upgrade:

"gateway": "authorize_net",
"authorization: "{{10-digit transaction ID from Authorize.NET}}"

Here is a snippet from JSON response after the upgrade:

"gateway": "authorize.net",
"authorization: null,

If you rely on this field like we do, I would not recommend installing this plugin until it populates this field with the 10-digit transaction ID generated by Authorize.NET for the transaction.