Authorize.Net Consolidated 1.7 with Curl Fix bug?

[Guest]

Hey guys I am using this payment module:

 

Authorize.Net Consolidated 1.7 with Curl Fix

http://www.oscommerce.com/community/contri...earch,authorize

 

It works like a champ, but I have noticed one bug.

 

When someone processes a credit card, and Authorize.net declines the card. OsCommerce still adds the order to the orders.table. Then when you are in ADMIN view, I see that the order is shown as "PENDING". It's shown as PENDING even though it was declined. It will also add an entry for each time they try and process the card and it's declined. So if they try three times, I get three PENDING orders.

 

When I click on PENDING in the admin screen, it shows me nothing...I can't even delete it because it did not set some flag correctly or created another table entry correctly.

 

I always have to go into MyPHPAdmin and delete the table entry in the orders.table to get rid of the PENDING status that was created for a declined card.

 

Has anyone else had this problem? :blink:

[superman123]

Hey guys I am using this payment module:

 

Authorize.Net Consolidated 1.7 with Curl Fix

http://www.oscommerce.com/community/contri...earch,authorize

 

It works like a champ, but I have noticed one bug.

 

When someone processes a credit card, and Authorize.net declines the card. OsCommerce still adds the order to the orders.table. Then when you are in  ADMIN view, I see that the order is shown as "PENDING". It's shown as PENDING even though it was declined. It will also add an entry for each time they try and process the card and it's declined. So if they try three times, I get three PENDING orders.

 

When I click on PENDING in the admin screen, it shows me nothing...I can't even delete it because it did not set some flag correctly or created another table entry correctly.

 

I always have to go into MyPHPAdmin and delete the table entry in the orders.table to get rid of the PENDING status that was created for a declined card.

 

Has anyone else had this problem?  :blink:

<{POST_SNAPBACK}>

 

 

yea i get the same error. I guess they will have a fix for it in the naer future but for now. i delete them manually in mysql