Hi, I have the very same Transaction ID on all my Authorize.net orders, the number is 16777215. I expected this number to change from order to order, the only value that changes is the Authorization Code.
Is there something wrong with the AN plugin?
J! 2.5.9
VM 2.0.10
PHP 5.2.17
Thanks a lot in advise!
Hello
The transaction ID is a number returned by Authorize.net.
Quote from: alatak on April 04, 2013, 09:49:36 AM
Hello
The transaction ID is a number returned by Authorize.net.
Hi alatak, that I know, but is really stran ge that is allways the same, if I enable the sandbox mode, the Tx ID varies!. Will contact AN support to see why that is happening.
Thanks!
OK im getting the same exact thing.
Every transaction ID is 16777215
what gives? it wasn't like that before migrating to joomal 2.5. i had the correct IDS such as 5200854901
SO something isnt right.
The same for my shop, can't this be revised? If any delevoper needs something to be done on our part to debug, be welcome to ask!
OK i did some digging..
a snippet from the authorizeresponse_raw Field in the Table: c6ocg_virtuemart_payment_plg_authorizenet
1|1|1|This transaction has been approved.|602589|Y|5211401120|
BUT IN THE FIELD authorizenet_response_authorization_code it shows 16777215
and thats probably due to the field TYPE not being correct.
authorizenet_response_transaction_id mediumint(1) UNSIGNED
has a max number of 16,777,215 and without error checking it just puts in the max since our number is greater than that.
I have changed the field type to char(128) removed the unsigned attribute (yes that is serious overkill)
then manually use phpmyadmin to copy the transaction ID from authorizeresponse_raw to authorizenet_response_authorization_code
THEN it should work ok until they put the CORRECT field type in.
this needs fixed NOW>
What rayge is saying is to apply this query to fix the issue.
QuoteALTER TABLE jos_virtuemart_payment_plg_authorizenet CHANGE authorizenet_response_transaction_id authorizenet_response_transaction_id CHAR( 128 ) NULL DEFAULT NULL
I have applyed the query and now waiting to a real order to arrive to see if it's working
Hello
QuoteI have changed the field type to char(128) removed the unsigned attribute (yes that is serious overkill)
Txs. I have done the change
I confirm that altering the table, the issue is long gone!