speed777

Do a search in Community->Contributions, there may be a module that you can install for PBS.

You may also try to troubleshoot it by inserting a test product with a cost of $1.00 into your catalog. Then run an actual credit card transaction, you'll see an error code. Look up the error (response code) at: http://www.authorize.net/support/AIM_guide.pdf

That's in your merchant service providers interface, that's not in OsCommerce.

That's where you have to have your shipping modules installed and working.

ogg2k, Have you enabled PWA in your OsCommerce admin panel? It's under Configuration>Customer Details>Purchase without acount.

dposborne, It's the / includes / languages / english / login.php file that you modify.

You need to get a Merchant Service Provider and use their internet payment gateway to process your credit card transactions. You will then be able to install and use a module like Authorizenet, Plug 'N' Pay, Payflow or something else. They are an intermediate but necessary step in the credit card process. Fees will vary with the different companies so shop around.

Try installing the module again. The address for the check/money order is taken from the store address. Configuration>My Store>Store Address and Phone

http://www.oscommerce.com/community/contributions,4091

Click on the top bar, where it says "Community" then "Contributions" and do a search.

I would then look at the checkout_payment and checkout_process files. Install a new Authorizenet file for each. It sounds like it's going through the checkout_payment -> checkout_process -> checkout_confirmation files. Since you're not getting an Authorizenet error with this problem, it's probably not selecting the Authorizenet module.

I had the same problem and I fixed it by reinstalling the original Authorize.net checkout_payment and checkout_process files. It worked then so I just had to figure which one was causing the problem. I substituted the modified MVS checkout_payment and it worked. I then made a new checkout_process file with Winmerge copying only the text that began with //MVS start. It works now.

Make sure that your Relay Response is correct (i.e. https://www.yourstore.com/.../checkout_process.php).

In includes/languages/english.php, look for: define('TEXT_CCVAL_ERROR_INVALID_DATE', 'The expiry date entered for the credit card is invalid.<br>Please check the date and try again.'); define('TEXT_CCVAL_ERROR_INVALID_NUMBER', 'The credit card number entered is invalid.<br>Please check the number and try again.'); define('TEXT_CCVAL_ERROR_UNKNOWN_CARD', 'The first four digits of the number entered are: %s<br>If that number is correct, we do not accept that type of credit card.<br>If it is wrong, please try again.');

See this topic: http://www.oscommerce.com/forums/index.php?showtopic=200146 It is my understanding that the information is submitted once and a decision (response code) to accept or decline is made unless there is an error or it is held for further review. http://www.authorize.net/support/AIM_guide.pdf

Make sure your cURL path is correct, ask your host provider if you're not sure. Then check the 'Accepted Credit Cards' field of your Authorizenet module to insure that the credit cards are going to be accepted. Third, check to see if your Merchant Service Provider has your merchant account set up to accept credit cards.

In your osCommerce Admin panel, click 'Modules' then edit your Authorizenet module by selecting 'Processing Mode' with "Authorize and Capture". Then click "Update".

https://developer.authorize.net/response_co...sp?page_id=7199

I mentioned disabling AVS because it was recommended during the holiday season by a credit card processor. Here is the mesage they sent: 1 December 2005 Processing Gift Credit Card Transactions In the past few years, the use of pre-paid or gift credit cards (stored-value cards with a Visa, MasterCard, Discover or American Express logo) has grown significantly in popularity. According to the third annual National Retail Federation (NRF) Gift Card Survey, conducted by BIGresearch, card sales will total $18.48 billion this holiday season, a 6.6 percent increase over 2004. The average consumer will spend $88.03 on gift cards or 15.6 percent of their holiday gift budget (http://www.nrf.com/content/default.asp?folder=press/release2005&file=giftcards1105.htm&bhcp=1). With this kind of growth, there is no doubt that your business can greatly benefit from processing gift credit card transactions. However, since a gift credit card is not associated with the recipient?s billing address at an issuing bank, gift credit card transactions may experience Address Verification Service (AVS) rejections. AVS is a valuable fraud-prevention tool that allows you to validate customer billing address information before accepting credit card transactions. However, to allow for the smooth processing of gift credit cards during increased holiday shopping, please take the following steps to verify, and if necessary, turn off the appropriate default AVS setting for their payment gateway account: Log into your Merchant Interface account Click Settings and Profile in the main menu Click Address Verification System (AVS) in the Security section Click to deselect the checkbox labeled Address information for cardholder is unavailable (U) Click Submit Your AVS settings are now updated to allow the processing of gift credit card purchases with unavailable address information. It is recommended that you reinstate this setting shortly after the holiday season. Your success is our priority, especially at this busy time. Good luck and happy holidays!

Return address (receipt page) should be 'https://ssl.yoursite.com/catalog/checkout_confirmation.php'

This is an open forum and I'll say what I want to say. If you don't like the answer...fine. If I misunderstood the problem that is my fault.

As I understand it, in order to accept gift cards, you must first disable the AVS settings in your payment processor interface. Otherwise the transaction will be rejected.

Turn off 'Force Cookie Use' in your settings, if it runs ok then it's a problem with your includes/configure file.

I use WinMerge to integrate php files. Go to WinMerge and download the free program. It has a feature that lets you open 2 files and see them on the screen side-by-side. Open your credit card module file (example: if you're using the Authorize.Net Consolidated 1.7 with Curl Fix contribution, it has a file called checkout_process.php) and the new file (look in the Purchase Without Acount contribution for checkout_process.php) that you want integrated. The differences in the 2 files will be highlighted in red. Transfer the new file over and save. You may have to experiment a few times to get it to work right. Remember to work off of a copy of the file (rename the original file) so you can restore it to the original state if you need to.

PWA contains 2 files, checkout_process.php and checkout_payment.php, which are also used by your credit card module. So, if you don't integrate them, you'll have problems. It sounds like that's what happened.