Omtaler (20)
Raffiner
-
Etter vurdering
***Update (07/17/24) PLEASE RESPOND: I just got an e-mail stating that I have to upgrade yet again? I literally just updated this plugin 2 months ago? I have no way of knowing whether or not I am good or I have to update yet again...***
***Update: Had an issue with JCB. Was fixed promptly. Great customer service. Thank you so much!!!
Here we go... got an e-mail that Authorize.net is updating their app. Followed the instructions to install the new app. The purchase testing went fine but I've now lost the ability to accept JCB.
Here are the cards I accepted with the original app.
Visa, Mastercard, American Express, JCB, Discover, Diners Club
Here are the only cards listed in the new app.
Visa, Mastercard, American Express, Discover, Diners Club
I lost JCB even though it clearly states that my merchant provider lists JCB is enabled in the Authorize.net configuration page on the Authorize.net website (not Shopify). It doesn't seem to show up on the new Shopify app. If I revert back to the old Shopify app JCB comes back.
***Update***
Hi RingDivas,
The JCB update has now been approved and released, I have run some test transactions to validate. Apologies for any inconvenience I hope the remainder of your testing goes well.
Regards
A.Net support
———————————————
Hi RingDivas,
We've submitted the additional card type version for approval, as soon as it's been approved JCB should be available for you.
Apologies for any inconvenience caused, hopefully this should be resolved by the end of the day. As soon as I receive word that it's been approved I will add a note here
Regards
A.Net Support
REFUNDS NOT WORKING ANYMORE!
ERROR: User authentication failed due to invalid authentication values
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.
Apologies for the issues you have been facing. As mentioned with the new migration to Shopify's Payment Processing Platform which all Payment providers are required to migrate to we no longer have the ability to return our RequestID. For all future transactions you will need to utilise the PaymentID supplied by Shopify to interact with payments. We have begun to pass the AuthorisationID across in the comment field as this is the only available field at present to help merchants cross reference
Once again apologies for the inconvenience, however this is a core element of the new Shopify architecture
The transaction ID from authorize.net is no longer passed through. if your keys change you need to un-install and re-install the app.
needs improvement
it led to a problem on our Shopify Store’s functionality has stopped capturing payments for all new orders ever since this App was installed as per recommendation by our 3rd Party provider, eBizCharge. Tech support of eBizCharge says it's Shopify, but Shopify support says it's them. Going circles. Still waiting this issue be resolved.
Hi Security Pro,
Apologies for the issues you have been facing. As mentioned with the new migration to Shopify's Payment Processing Platform which all Payment providers are required to migrate to we no longer have the ability to return our RequestID. For all future transactions you will need to utilise the PaymentID supplied by Shopify to interact with payments.
Once again apologies for the inconvenience, however this is a core element of the new Shopify architecture
app doesnt transfer transaction id. makes searching which was once easy to do difficult.
Does not transfer the auth code back to Shopify, which means we can't process it in our ERP. Missing basic functionality.
Apologies for the issues you have been facing. As mentioned with the new migration to Shopify's Payment Processing Platform which all Payment providers are required to migrate to we no longer have the ability to return our RequestID. For all future transactions you will need to utilise the PaymentID supplied by Shopify to interact with payments.
Once again apologies for the inconvenience, however this is a core element of the new Shopify architecture
The new Authorize.net processor gateway for Shopify does not support Recharge subscriptions! Everyone is required to upgrade to this new version by June 28th, 2024. Hopefully it is fixed by then.
Hi Gorilla Mind,
The initial communication was intended to only go to merchants who were not using subscription options.
Apologies for any inconvenience caused if you received this in error. Our development team are planning to have the subscription functionality available by the 14th May. We’ll make sure to update you when the release is ready for testing.
Regards
A.Net Support