Transaction ID FAQs

• What is the Authorize.Net Transaction ID?
• What is going on with the Transaction ID field?
• Will my ability to process transactions be affected?
• How can I know if my systems will be affected by this?
• What steps do I need to take to assure that I do not encounter any interruptions to my transaction processing?
• What should I tell my developer?

The Authorize.Net Transaction ID is a unique, sequential, numeric value that the payment gateway assigns to every transaction. The Transaction ID can be found in the transaction response. It can also be found using 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 the near future 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 Authorize.Net 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, as the Transaction ID is a value that is returned by the payment gateway along with the response code after you have submitted a transaction. 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 example, if you are using the field for reporting purposes, once the value exceeds 2,147,483,647, your system will no longer accept the Transaction ID field as a valid value. Similarly, if you are using the Transaction ID to submit follow-on transactions, then you may be affected when the Transaction ID exceeds 2,147,483,647.

If you are currently using or storing the Transaction ID field, or x_trans_id, in any of your own databases or systems and if the data type you are using is not compatible with larger values you may be affected. Please coordinate with your developer or technical team to ensure that the Transaction ID data type will support these larger values.

If you are not sure what we mean by either of the scenarios above, it is critical that you contact the developer, shopping cart or other solutions provider that integrated your Web site or application to the payment gateway, to verify your specific situation. Unfortunately, Authorize.Net does not have access to the technical specifications that will determine whether or not your integration will be impacted by the expansion of the maximum Transaction ID values. As such, our customer support department will be unable to make this determination for you.

Authorize.Net has contacted as many developers, solutions providers and partners as possible regarding preparation for the expanded Transaction ID values, so your provider should be well aware of the situation when you contact them.

You must make sure that your systems or databases use a data type that will handle a 10-digit Transaction ID greater than 2,147,483,647.

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 the Transaction ID has been specified 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.