优化
-
按评分
horribe app does not work been at it for hours and still not working . losing sales every minute it is down
Hi Nature's Root,
We're bringing up the issues raised with Shopify and they have extended the migration date to September 30th, we're continuing to work with Shopify to resolve known issues but if you're able to revert to the original integration we will advise when a new migration can take place.
Apologies for any inconvenience
We were forced to update Auth.net on our store to process regular payments. We use Recharge which is now not compatible with this new system. Is there an update available? We have subscribers we need to charge.
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
app doesnt transfer transaction id. makes searching which was once easy to do difficult.
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
REFUNDS NOT WORKING ANYMORE!
ERROR: User authentication failed due to invalid authentication values
Broke payment importation between my store and ERP system
Hi Vytanutra,
Please be advised with Shopify's migration to their new Payment Provider Platform, all 3rd party applications integration to payments apps must now reference the paymentID rather than the previous Authorize.net RequestID.
We will be providing more information shortly to support merchants using 3rd parties
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