QuickBooks Merchant Service

[kwes00]

Hello - I read through this thread twice & followed all of the QBMS advice & tips but I'm still getting "An error has occurred within our system while trying to process your credit card" after submitting the final credit card info in Zen Cart

QBMS rep verified:
- we're able to accept webstore payments
- Visa flags are checked
- the connection ticket (desktop-production) is active on the account

The payment module (v1.3.8) was installed & reinstalled and is configured with the correct AppID, App login, & connection ticket.

I reset the QBMS setting "process with web store" off & then back on & waited a full 24 hours, plus confirmed it was enabled with QBMS.

Our site is hosted through Godaddy & they confirmed a proxy for the cURL is not required, so our proxy status is set to false & the cURL proxy address is null.

Any other ideas or suggestions would be greatly appreciated

Thanks!

Here's the fix for anyone else using Godaddy to host Zen Cart, connecting to QBMS

Within the file includes>modules>payment>qbms.php
1. Remove the line:
curl_setopt($clientURL, CURLOPT_SSL_VERIFYPEER, 1);

2. Add these two lines in its place:
curl_setopt($clientURL, CURLOPT_SSL_VERIFYPEER, false);
curl_setopt($clientURL, CURLOPT_SSL_VERIFYHOST, 0);

[cptok]

kwes00 - In my opinion, that is a big (very big) mistake. Do you understand what changing those settings does? Remember - you are sending customer credit card information. I would be very careful of making changes such as this without VERY clearly understanding what you've changed, and what exposure that might create for you.

This is open-source code, so of course you can change it as you like. So take the above advice... or not. But I can tell you I wouldn't make that code change (both you list) and take customer cc data.

My 2 cents...

PS - It might be alright to turn off "verifypeer" (if GoDaddy really does have broken libcurl). But turning both off... ??

[cptok]

Quick reality check for all credit card module users. PLEASE be very careful "hacking" these modules (QBMS or any other). It's one thing to hack and play with a skin, or display modules etc., and quite another to make code changes to credit card processing modules.

Think about it - at least just for a brief moment. If you have a code error, and a bunch of charges (possibly a great many?) get disputed by the cc holders... who do you think gets hit with the losses? The merchant service company will reverse those amounts from the vendor. If there are additional exposures say for example you send the credit card data to an unverified destination, and there end up being large additional liabilitites... who do you think will get that call? The vendor in this chain of events has a great deal of exposure - especially since these are online transactions (no signature, no swipe, no physical card).

Enough said. Message is - please be responsible when handling financial transactions. This is open source, and "distributed without warranty", so anyone is clearly free to make changes and hack away. But IMHO, Mydanilo has it right, tighten up security on these transactions (such are requiring correct CVV and AVS) rather than loosening it up.

Definitely not trying to offend *anyone*. Just think it's an important awareness to have in working with these transactions.

[mydanilo]

Here is another solution, don't host with Godaddy for Zen Cart. Too many issues.

[cptok]

NEW VERSION QBMS 1.9

(Includes important bug fix. All users encouraged to update to latest version.)

v 1.9 -- 09/05/09

- Optimized duplicate search so that large db's do not get impacted by duplicate handling.

- New feature to provide better error reporting to customers. Denials vs. validation now recognized and handled separately.

- New code to check for and handle duplicate transactions from QBMS. If same customer with same sales amount submits within 5 minutes, QBMS treats as "duplicate" and does not post the charge. BUT Zen was receiving the "OK" status and creating the order. New code checks the returned transaction ID, and if it exists - it creates an error without creating an order.

- Fix legacy bug in XML transaction request ID. This could cause transactions which submit very close together to be treated as duplicates at QBMS.

[styleboy]

Odd problem I have. I can make purchases with 2 of my credit cards and get them to go through. The third one spits back an error " An error has occurred within our system while trying to process your credit card. Please try this transaction again"

If I change the address, this card will work. In my web store security settings I have accept transaction for all of the billing and zip code matches. Why would this work if I only put in a wrong billing address?

It seems a lot of cards are not working if you put in the correct billing address. Why would this be?

[cptok]

First, and most important, what version of QBMS module are you running? The AVS/CVV checking and return code handling has been modified a lot in recent versions.

[jbthomasfl]

Newbie question alert! Sorry if I'm hijacking the thread.

NEW VERSION QBMS 1.9

(Includes important bug fix. All users encouraged to update to latest version.)

v 1.9 -- 09/05/09

I'm trying to take over for our webmaster, but am not a coder, just broke. We've had several emails asking if we took CC's other than by PayPal. We got QBMS for card present retail transactions. We can also key in xactions. Is it possible to use both payment methods in ZC 1.3.8a? If so, do I need to create an intermediate page for the buyer to choose or do we want to drop PP altogether, since the rate is higher?

[steve30000]

I have just downloaded version 1.9a to install in a new zen cart and have gone through the process to register the application and now would like to try it in the test environment. However, when I follow the link provided in the PDF to sign up for a PTC Merch Account, I get a "Page Not Found" error message.

If##you##selected##the##Test##environment##you##need##to##sign##up##for##a##PTC# #Merch##account##in##order##to##test##the##module,####do##so##going##to##the##fo llowing##web##page##
https://merchantaccount.ptc.quickboo...erchant=true##

Any suggestions?

Thanks,
Steve