Jump to content
Sign in to follow this  
woodpress

Auth.net Gateway changes as of October 2008

Recommended Posts

Authorize.net sent notice today that come October 2008 they going to start issuing transaction IDs that are greater than 10 digits. Do the Authorize.net module of osCommerce already accomodate IDs greater than 10 or is there an urgent update needed?

 

Thanks. (A copy of Auth.net's letter follows)

 

Important System Notice

 

Dear Authorize.Net Merchant:

 

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.

 

If you have any questions, please contact Customer Support at support@authorize.net.

 

Sincerely,

Authorize.Net

Share this post


Link to post
Share on other sites
Authorize.net sent notice today that come October 2008 they going to start issuing transaction IDs that are greater than 10 digits. Do the Authorize.net module of osCommerce already accomodate IDs greater than 10 or is there an urgent update needed?

 

Thanks. (A copy of Auth.net's letter follows)

 

No, they did *not* say values larger than 10 digits. They said they will be expanding to a 10 digit number larger than 2,147,483,647 ( sizeof(int) ) or 32 bits or 4 bytes.

 

I haven't looked at the code yet, but I don't believe that osCommerce even uses the x_trans_id nor does it get saved to the database. So, long story short - don't worry about it.

 

Here is the specific text from the email that applies:

 

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.

Share this post


Link to post
Share on other sites
I got the same email. So are we not affected, regardless of whose Auth.Net contribution we're using? I'm using Vger's module.

Then you should go ask that question in the Vger module support topic...

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×