VP-ASP :: Shopping Cart Software

Shopping Cart Software Solutions for anywhere in the World

US/Canada(Toll Free): +1 888 587 2278
Europe/UK: +44 (020) 7193 9408
Australia/New Zealand: +61 3 9016 4497

VP-Cart StoreFront Customer Forum

Home | Profile | Register | Active Topics | Members | Search | FAQ
Save Password
Forgot your Password?

 All Forums
 VPCart Forum
 Add-ons for VP-ASP
 VP-ASP 5.5 Question
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

Starting Member

2 Posts

Posted - September 04 2008 :  01:14:18  Show Profile  Reply with Quote
We have been using VP-ASP for a few years with success, however we just received word that Authorize.net is changing their Transaction ID number scheme. It is worth noting that we are using Version 5.5 of the product (VP-ASP 5.5)

Will this impact the product at all?

Here is the e-mail 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.

Here is a link to the change info:


Edited by - cland5555 on September 04 2008 01:15:03


4284 Posts

Posted - September 04 2008 :  01:18:43  Show Profile  Visit support's Homepage  Reply with Quote

The changes being made by Authorize.Net will not affect VPASP users.

VPASP stores the transaction id returned from Authorize.Net in a text field which is not subject to the same limits as a field with data type "integer".

You will not need to make any adjustments to your site or database in response to these changes by Authorize.Net

Go to Top of Page

Starting Member

2 Posts

Posted - September 05 2008 :  18:14:41  Show Profile  Reply with Quote
Thank you for the reply on this important subject.
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
Snitz Forums 2000