We use AbleCommerce 7.0 webshop engine and for the payments we use the Authorize.Net gateway.
Authorize.Net will perform some technical updates and we would like to know that our AbleCommerce 7.0 webshop will work correctly after Authorize.Net releases the technical updates.
The technical updates of Authorize.Net will be the following:
-In the coming months, due to system updates, it will be possible to receive Authorize.Net IDs (Transaction ID, Batch ID, etc.) that are not in sequential order. The limits of any Authorize.Net ID field should be no less than 20 characters.
The exact detail can be found in the following link:
http://app.payment.authorize.net/e/es.a ... f9d8ae4d54
The changes can be cause compatibly issue with AbleCommerce 7.0?
Another question: What would be the cost to update to the latest AbleCommerce engine from our current engine?
The component versions what we use are the followings:
AbleCommerce 7.0
PLATFORM: ASP.NET
VERSION: 7.0
BUILD: 10125
AjaxControlToolkit: 1.0.10301.0
CommerceBuilder: 7.0.10110.0
CommerceBuilder.AuthorizeNet: 7.0.9764.0
CommerceBuilder.CanadaPost: 7.0.0.0
CommerceBuilder.CCH: 7.0.0.0
CommerceBuilder.Configuration: 7.0.10102.0
CommerceBuilder.CyberSource: 7.0.9764.0
CommerceBuilder.DataClient.Api: 1.0.0.21
CommerceBuilder.DataClient.Csv: 1.0.0.0
CommerceBuilder.DHL: 7.0.8825.0
CommerceBuilder.ECB: 7.0.0.0
CommerceBuilder.FedEx: 7.0.9725.0
CommerceBuilder.FRBNY: 7.0.0.0
CommerceBuilder.GoogleCheckout: 7.0.10052.0
CommerceBuilder.InternetSecure: 7.0.9764.0
CommerceBuilder.LinkPoint: 7.0.9764.0
CommerceBuilder.Paradata: 7.0.9764.0
CommerceBuilder.PayFlowPro: 7.0.10061.0
CommerceBuilder.PayJunction: 7.0.9764.0
CommerceBuilder.PayPal: 7.0.10071.0
CommerceBuilder.Services: 7.0.9733.0
CommerceBuilder.SkipJack: 7.0.9764.0
CommerceBuilder.UPS: 7.0.10041.0
CommerceBuilder.USPS: 7.0.9728.0
CommerceBuilder.Web: 7.0.9777.0
ComponentArt.Web.UI: 2007.1.1566.3
CyberSource.Base: 2.0.0.0
CyberSource.Clients: 5.0.2.0
CyberSource.Clients.XmlSerializers: 5.0.2.0
CyberSource.WSSecurity: 2.0.0.0
CybsWSSecurityIOP: 1.0.0.0
edtFTPnet: 1.2.4.0
FredCK.FCKeditorV2: 2.5.2912.21007
ICSharpCode.SharpZipLib: 0.85.1.271
Interop.eLicenseLib: 1.0.0.0
LinkPointTransaction: 1.0.1797.29766
log4net: 1.2.10.0
Microsoft.Practices.EnterpriseLibrary.Common: 2.0.0.0
Microsoft.Practices.EnterpriseLibrary.Data: 2.0.0.0
Microsoft.Practices.ObjectBuilder: 1.0.51205.0
Microsoft.Web.Preview: 1.2.61025.0
NVelocity: 7.0.8530.0
PaygatewayNET: 3.0.0.0
paypal_base: 4.2.1.0
PFProCOMLib: 1.0.0.0
PFProdotNET: 0.0.0.0
SerialProvider: 1.0.0.0
UpgradeSerialProvider: 1.0.0.0
Validators: 1.0.0.0
WebChart: 1.1.1.6
wwHoverPanel: 1.85.0.0
AbleCommerce 7.0 webshop and Authorize.Net update
Re: AbleCommerce 7.0 webshop and Authorize.Net update
I checked with our development team and here is their response:-In the coming months, due to system updates, it will be possible to receive Authorize.Net IDs (Transaction ID, Batch ID, etc.) that are not in sequential order. The limits of any Authorize.Net ID field should be no less than 20 characters.
We should be fine. In ac_Transactions table where we stored provider transaction id we have set it to 50 characters. We already have GUIDs in this field up to 36 characters. So we are good up to 50 characters. Keep in mind that we use the same field for different providers and have never heard any issue with this limit so far.
Nothing in our code requires sequential ID's, so we should be good there too.
If you are interested in upgrading, you should contact us directly because we'll need to look up your account. Please use the contact form on our website - https://www.ablecommerce.com/ecommerce-contacts.aspx or call or use the online chat form.
Thanks,
Katie
Thank you for choosing AbleCommerce!
http://help.ablecommerce.com - product support
http://wiki.ablecommerce.com - developer support
http://help.ablecommerce.com - product support
http://wiki.ablecommerce.com - developer support