Authorize .Net October Upgrade

[heinscott]

Hello, just wondering about an email we just got from Authorize .Net. They say that "The Transaction ID field was originally developed with a maximum numeric value of 2,147,483,647. As the number of merchants using the Authorize.Net Payment Gateway has grown, we have identified a time in which the Transaction ID count will surpass 2,147,483,647. For this reason, we are in the process of expanding the range of Transaction IDs that the payment gateway can issue. Accordingly, we are communicating to all merchants to verify that your systems can accommodate a 10-digit Transaction ID greater than 2,147,483,647." I just looked at the db, and noticed that the ProviderTransactionId is a nvarchar(50) data type, which I assume means that this upgrade will not affect Able Commerce.
My boss just wanted me to write this message in the forums to verify that the Authorize .Net upgrade will not "break" our store.
Thanks for the help,

Scott

[Shopping Cart Admin]

Hello Scott,

I asked this of development a few months back and was told it's a text field so it won't be a problem.

[heinscott]

That was my impression, too. Thanks a lot!

-Scott

[AbleMods]

Hey Mike, just wondering about an email we just got from Authorize .Net. They say that "The Transaction ID field was originally developed with a maximum numeric value of 2,147,483,647. As the number of merchants ...........


LOL!!!!!!!!!!!

p.s. inside joke, apparently Mike's been hit up on this quite a bit today so I couldn't resist

[Logan Rhodehamel]

Our transaction system has handles several different gateways - some of them do not use numbers but alphanumeric strings. So we have always built on the premise that it is a string, as far back as AC3 and maybe farther.