Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

AVS error - when there shouldn't be


Danny_C

Recommended Posts

Everything on the installation seems to be working, and it seems to be communicating with our payment gateway Wonderpay. But whenever anyone tries to sign up, it gives an AVS error that "billing address1 does not match shipping address1".

 

Wonderpay says everything is functioning correctly on their end, and that it has to be an issue with OSCommerce... but when I researched it, it doesn't seem that this is a problem that people have had in the past.

 

If anyone has any troubleshooting ideas, they would be greatly appreciated.

 

The site, by the way, is www.merchantproducts.com/

Link to comment
Share on other sites

Everything on the installation seems to be working, and it seems to be communicating with our payment gateway Wonderpay.  But whenever anyone tries to sign up, it gives an AVS error that "billing address1 does not match shipping address1".

 

Wonderpay says everything is functioning correctly on their end, and that it has to be an issue with OSCommerce... but when I researched it, it doesn't seem that this is a problem that people have had in the past.

 

If anyone has any troubleshooting ideas, they would be greatly appreciated.

 

The site, by the way, is www.merchantproducts.com/

 

you will need to post the payment gateway contrib you are using :-)

:-)

Monika

 

addicted to writing code ... can't get enough of databases either, LOL!

 

my toolbox: Textpad - Compare and Merge - phpMyAdmin - WS_FTP - Photoshop - How to search the forum

 

Interactive Media Award July 2007 ~ category E-Commerce

my advice on the forum is for free, PMs where you send me work are considered consultation which I charge for ...

Link to comment
Share on other sites

Good idea.  That can be found here: http://www.wonderpay.com/html/oscommerce.html

 

It was mentioned that it may be an issue with that gateway contrib having an issue with my version of osCommerce, which is osCommerce 2.2-MS2.

 

 

I checked the files, they look ok to me ... the message you get is not from osC but wonderpay right? Does it happen even when shipping and billing address are the same in osC?

:-)

Monika

 

addicted to writing code ... can't get enough of databases either, LOL!

 

my toolbox: Textpad - Compare and Merge - phpMyAdmin - WS_FTP - Photoshop - How to search the forum

 

Interactive Media Award July 2007 ~ category E-Commerce

my advice on the forum is for free, PMs where you send me work are considered consultation which I charge for ...

Link to comment
Share on other sites

I checked the files, they look ok to me ... the message you get is not from osC but wonderpay right? Does it happen even when shipping and billing address are the same in osC?

 

Yes. It goes to the confirmation page, shows all of the correct information with the shipping address exactly matching the billing address, and then when you click to confirm and finish the order, it returns the AVS error that the addresses don't match.

 

My first thought was that since it seems to be communicating with Wonderpay and they're returning the error, that it must be something on their end, but when I talk to them they say that everything is looking good on their end and say that it's an issue with my OSCommerce installation. They've suggested entirely reloading OSCommerce, but that's a large undertaking if it turns out not to be the issue... so that's why I'm hoping for some other troubleshooting options first. :)

Link to comment
Share on other sites

in this case I'd do a logging for all parameters (you find them inyour files in the function process button)

 

add this to the shipping module file in that function right before the parameters are added (those hidden values)

$time=date("d M Y H:i:s");
$logfile=fopen(DIR_FS_CATALOG . 'logfile.txt',"a");
fputs($logfile,$time . " - ci_billaddr1: " . $order->customer['street_address']) . "\n");
..... (add an fputs line for all shipping and billing parameters)
fclose($logfile);

 

create a file logfile.txt in catalog, and assign all rights (777) to it

 

then try to use the module, and after the error check the logfile. Let's see what you have in there!

:-)

Monika

 

addicted to writing code ... can't get enough of databases either, LOL!

 

my toolbox: Textpad - Compare and Merge - phpMyAdmin - WS_FTP - Photoshop - How to search the forum

 

Interactive Media Award July 2007 ~ category E-Commerce

my advice on the forum is for free, PMs where you send me work are considered consultation which I charge for ...

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...