Author Topic: Authorize.net Transaction ID Changes in October  (Read 4323 times)

davetanguay

  • Beginner
  • *
  • Posts: 9
    • Interactive Online
Authorize.net Transaction ID Changes in October
« on: September 02, 2008, 03:15:12 am »
Will VirtueMart still work with the Authorize.net changes which are occurring in October? Here is the notice we received...


In early October, Authorize.Net will be expanding the range of Transaction IDs issued by the payment gateway. Please read this e-mail thoroughly as it contains important information on how to ensure that your account is not affected.

The Authorize.Net Transaction ID is the payment gateway-generated number used to uniquely identify each transaction you submit for processing. The Transaction ID can be found in the transaction response and in the Search and Reports features of the Merchant Interface.

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.

In most cases your transaction processing will not be affected. However, if you have an internal business application or solution that relies upon the Transaction ID field, your system may fail if it cannot handle a Transaction ID larger than 2,147,483,647. For more information, please review the Transaction ID FAQs located at http://www.authorize.net/transid.

It is critical that you contact your developer to verify whether your integration will be impacted. Specifically, please provide your developer with the following information:

The Transaction ID, or x_trans_id, is specified as a 10-digit integer and will only be affected if that value is represented as an INT data type, which has a max value of 2,147,483,647. If you have specified the Transaction ID as a string value, then your system will not be affected. Failure to accommodate 10-digit values larger than 2,147,483,647 will result in your system's inability to accept Authorize.Net transactions.

Note: If you need to make updates to your Transaction ID architecture, you should do so prior to October 1, 2008, to ensure that you will not be affected.

andydouth

  • Beginner
  • *
  • Posts: 5
Re: Authorize.net Transaction ID Changes in October
« Reply #1 on: September 08, 2008, 10:24:36 am »
Does anybody know how this will affect VirtueMart?  Is VirtueMart already using a string or int 64?

Ian

  • Beginner
  • *
  • Posts: 8
    • Daily Cartoons, Comic Strips, Online Games & Funnies to start your day
Re: Authorize.net Transaction ID Changes in October
« Reply #2 on: September 10, 2008, 01:19:56 am »
Do any developers know the question to this? It seems only the 3 of us are concerned about whether virtuemart can handle the new authorize.net Transaction ID changes?
I have reread the email from authorize.net, but as I'm not a programmer I have not idea know this will effect the website and how to prepare for it.
Please can someone who knows the answer please respond. Does Virtuemart relie upon the Transaction ID field and if so, can it handle bigger values of 2,147,483,647?
http://www.thefunnycartoon.com - Daily Cartoons, Comic Strips, Online Games & Funnies to start your day
http://www.pixelfreeway.com - My Graphic Design Portfolio Website

TheWebGuy

  • Jr. Member
  • **
  • Posts: 57
Re: Authorize.net Transaction ID Changes in October
« Reply #3 on: September 10, 2008, 01:31:55 am »
There is quite a few more than just us 3 who are concerned as there are a number of posts (as far back as August 1st) which ask this question and I haven't seen a reply to any of them.

http://forum.virtuemart.net/index.php?topic=43894.0

I guess you get what you pay for  :-\