Jump to content


Corporate Sponsors


Latest News: (loading..)

- - - - -

Authorize.net


6 replies to this topic

#1 flanec

  • Community Member
  • 7 posts
  • Real Name:Lane Covington
  • Gender:Male

Posted 28 August 2008, 16:24

What versions of oscommerce will this affect if any?

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.

Edited by flanec, 28 August 2008, 16:25.


#2 Bushmaster

  • Community Member
  • 456 posts
  • Real Name:Scott McFadden
  • Gender:Male

Posted 28 August 2008, 17:37

never mind thinking of a diffrent data issue :blink:

Edited by Bushmaster, 28 August 2008, 17:40.


#3 Jack_mcs

  • Community Member
  • 24,448 posts
  • Real Name:Jack
  • Gender:Male

Posted 28 August 2008, 18:08

View Postflanec, on Aug 28 2008, 12:24 PM, said:

What versions of oscommerce will this affect if any?

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.
It's not the version of oscommerce that is affected. The authorize.net module is what determines that. I know the authorize.ent AIM module uses Text for that field so it is OK. If you use a different version, you will need to check the database table for the size being used.

Jack

#4 Jack_mcs

  • Community Member
  • 24,448 posts
  • Real Name:Jack
  • Gender:Male

Posted 29 August 2008, 16:04

I need to correct the above statement. The transaction key is stored in the configuration_value column of the configuration table. If that field is setup as Text, you shouldn't have a problem. If it is setup as something less, then you may. I apologize for the mistake. A case of working on two problems at once with a mind that only has one gear.

Jack

#5 koolie

  • Community Member
  • 5 posts
  • Real Name:Pat
  • Gender:Male
  • Location:Wisconsin, USA

Posted 02 September 2008, 21:35

View PostJack_mcs, on Aug 28 2008, 01:08 PM, said:

It's not the version of oscommerce that is affected. The authorize.net module is what determines that. I know the authorize.ent AIM module uses Text for that field so it is OK. If you use a different version, you will need to check the database table for the size being used.

Jack

I believe I am using the AIM module, but where in the database can I find if I'm using text or int? I cant seem to find it anywhere.

Thanks.

#6 koolie

  • Community Member
  • 5 posts
  • Real Name:Pat
  • Gender:Male
  • Location:Wisconsin, USA

Posted 02 September 2008, 21:40

Nevermind...I think I found it in the configuration und "Transaction Key". If someone could confirm this that would be great!

#7 Vger

  • Community Member
  • 16,978 posts
  • Real Name:R Anthony
  • Gender:Not Telling

Posted 04 September 2008, 11:24

The Authorize Net AIM module for osCommerce uses a field called x_tran_key, which is the 16 digit key provided by Authorize Net to the vendor.

It has nothing to do with x_trans_id, which is not part of the Authorize Net AIM module, and so the change is of no concern to those using the Authorize Net AIM module.

Vger