Spdster - you need to log in to your merchant account center and enable "web". It's off by default. Wait 24 hrs for this to process, then try again.
Spdster - you need to log in to your merchant account center and enable "web". It's off by default. Wait 24 hrs for this to process, then try again.
Thank you!!!!!!!!! I just called them and they will enable it like you said in 24 hours. Thanks again!
I have placed the qbms files on my server, but they do not show up in the payment module screen. I have exactly the same situation as did another poster in messages 341ff in this thread. The help was given offline. Does anyone have any suggestions as to where I should look to correct this issue?
Permissions are not the issue.
Thanks
April
Maybe I don't have the files in the right place. Can someone tell me exactly where they should be please and then we'll go from there?
Thanks so much. This is all brand new and I am so grateful for any help.
Is QB Merchant Service support dead in Zen Cart? I work in Intuit customer service and I get calls from merchants who want to use Zen Cart for their shopping cart and connect it to their e-commerce account. I've been sending them over here to talk to you guys, but someone else in my department said he thought Zen Cart wasn't handling QuickBooks Merchant Service any more. What's the current status of Zen Cart and QBMS?
Joshuagodinez - it is not dead, but remember that these modules are not "official" modules built by Zen Cart Development team. They are 3rd party modules supported by whoever writes them or takes them on. In this particular case, the module is very much alive and kicking. The lack of activity in this thread is more of an indication that the module "just works".
It is also tested and working with the latest release - if that is helpful. I've been maintaining this module for some time now, and pretty much continue to do so. But there just have not been any critical changes needed in recent times.
I am on zen v1.3.9f with no modifications using QBMS 1.9a and I am getting the following error when I try to process a card.
An error has occurred within our system while trying to process your credit card. Please try this transaction again. If the problem persists, ....
From what I have read in the forum this is not a module error but a system error. I am NOT on godaddy and curl is installed. I actually installed OSC 2.2 and tried it with the original module and it worked so I know my QBMS account is set up correctly and I have gotten my app id and connection ticket figured out but I am wondering what else I can do to check to see where the problem is.
I am not using the testing server and I am using a live card (worked in OSC 2.2) I really don't want to use OSC so hopefully I can get this figured out.
Thanks for your help!
propni - First question is, which security model are you using? Desktop or Hosted? This module is really tested with desktop and not so much with "hosted" as few people use it (including me!).
There are a few ways this error can occur. First is if QBMS returns a result code which is not in the recognized results (not likely). A hosted model with bad session connection ticket. Or finally - a curl error. Based on what you've said so far - I'd have to guess a curl error. But the key question right now is whether you are trying to process via hosted model...
Oh - and quick FYI - I would not use OSC module as any kind of measure or benchmark for the QBMS module. Zen version was radically rewritten, much of which included security, input validation etc. which the OSC version never had. There are just so many ways that QBMS would (correctly) fail and OSC would not. Processing customer credit cards includes some accountability on the merchant's part.
I am using the desktop "version" not hosted. How can I check to see if curl is working correctly. Running on CentOS Linux 5.3, PHP 5.1.6, libcurl/7.15.5 OpenSSL/0.9.8b zlib/1.2.3 libidn/0.6.5
Odds of me switching to OSC are very slim, Zen Cart is so much better. I just put that out there to see if by chance I had something set up wrong somewhere, which sounds like it could be irrelevant anyway.
Thanks for the help.
Bookmarks