QuickBooks Merchant Service

Did you decide if your going to post the new files to copy over the old ones on here, or just start a new addon, that we could copy over the old? That of course is when your modified stuff is stable.

Again thank you for working on it!

cptok:

I think if you put in a number less than 10 - the popup will work as expected.

Yes, you are correct. Less than 10 will result in a pop up. I think most often customers might just miss one digit. So I will set it to 15 at least as I accept AMEX as well. Discover and VISA/ MC have 16 digits. This should take care of it right now.

Wait, I just re-read and you say some Visa are only 13 digits? Would that be non US cards I assume? I found a link explaining here
http://www.beachnet.com/~hstiles/cardtype.html

I guess the better we check on our sites before sending it to processing, the less fees we accumulate as we get charged for every transaction and authorization too. Never mind if they decline, still a authorization attempt. Anyway, not sure now what number I will set it on but I do not recall 13 digit visa cards coming across too often.

I think you're probably OK setting to 13 min. Remember, there are many other checks to the number including valid leading bank codes, and numeric hash checks. If they forget a digit, it will fail (prior to going to merchant service) and get the red box. Just getting the red box does not mean it was submitted. The basic flow is - js validates obvious items, the cc_validation (a class) validates numerous other items, THEN it goes to gateway.

Securefocus - it's all pretty stable now. Just deciding how to handle. Post a link to download, or create a forked addon. This new file now has the following fixes/updates:

• Fix to js for initial form validation
• Fix to incorrect CVV2 check
• Fix to input form to limit input fields to sane lengths
• Fix to code to properly set hosted vs desktop gateway URL's
• Some typo and layout fixes

cool, just keep us posted!

OK - submitted to the addons as an update to v1.6. Will need review by Zen moderators prior to activation, but keep an eye out there for the update. All items discussed above are included. Changelog and install files also updated.

Hey guys I am going bananas. On my test site I managed to update the js and pop up worked with QB payment module. Now I installed Fast and Easy Checkout and it is not working. Somehow these two do not work together. Do any of you use the Fast and Easy Checkout?

I don't think it would be a question of them not "working together". The js code would be independent. It's possible, although I have not seen it, that the Fast and Easy script is somehow not working. Does it work by itself (without qbms installed)?

Fast and Easy is working and eliminates one step at check out. Actually it can eliminate 2 steps. Anyway, with Fast and Easy mod installed, I noticed that the pop up warnings are not working at all and the stacked message on top of the page is used to notify that something is wrong with the card. CVV gets not checked at all...

cptok: I checked and even the standard cc offline mod will not give the pop up error for CVV. Must be something with the Fast and Easy. I posted on Numinix website. Will see....

Question for all you QBMS users. The current module will allow multiple (duplicate) charges to occur. Intuit's recommended approach is to craft TransRequestID in such a fashion as to avoid this possibility. The consequence of doing this is that any given customer can only make QBMS charges once every 15 minutes and not more often. As mentioned, this is the recommended implementation by Intuit. Their example is - transaction is "complete" and charged, but network goes down before confirm hits customer. So customer redoes the order. Since it is a duplicate, it will reconfirm the data, but not charge again.

My personal view is to implement a hybrid approach. Craft the transaction id so that the SAME ORDER cannot be charged twice, but a new order number can be done immediately. Thoughts?

cptok:

My personal view is to implement a hybrid approach. Craft the transaction id so that the SAME ORDER cannot be charged twice, but a new order number can be done immediately. Thoughts?

Sounds great if you can do it this way.

Otherwise you could just set that any given customer can only make QBMS charges once every 3 minutes instead of the 15 minutes. I think it is very unlikely that a customer waits in front of the screen for almost 15 minutes and then presses the button again. Most will do it withing 20-30 seconds if they get impatient by a slow transaction.

Thank you for working on this.

Good points, but that is not how it works. The 15 min issue is determined by the processing rules at QBMS gateway, not a setting on our end. Either you set unique ID's and can submit over and over, or... you go with 15 min as determined by the gateway. And I agree with you, it's not clear that I could use an order number as it has not been generated yet. In fact, there is nothing particularly unique about that "order" until it successfully processes and is actually an order.

What I'm currently trying is to use the total charge amount. If it is the same charge amount in less than 15 min - it is considered a duplicate of the same order.

I was going to suggest the last part, the only thing "unique" is the customer and most of the time the dollar amount the customer is trying to buy will be different. So if you could implement that dollar amount into it, i think thats as "unique" as it gets.

I must say im so glad you are working on this as all of this is way over my php skills!

When you say quick and easy check out are talking about the paypal one? i use the paypal standard, that way my customers only have 2 choices. one they use paypal and if they have paypal they will know to use it, and other then that the customer well use the "traditional" put in your cc and press enter. I havent noticed anything not working on my side, but I will update if I do run into a problem.

OK - that update/enhancement is done. Any QBMS submission for exact same $ amount within 15 min will be considered by QBMS gateway to be a duplicate charge. Any differing amount will be allowed and processed. Don't know if I can get this into the release to be put on the addon site - but I'll try. This is a nice fix and a good way to handle it.

The history is - OSCommerce made ANY transaction within 15 min a "duplicate". Zen version allowed any and all transactions and would process them. This is, in my opinion, the best approach.

Great, that was fast implementation.

Fast and Easy Checkout is a mod by Numinix, eliminating some of the checkout steps. Combining the shipping selection screen with the payment screen. Awesome for not loosing customers along the way. The problem is, that the cvv validation does not work as it does on the normal 4 step checkout process. Posted with Numinx on his support site. We'll see if he can fix it or tell me what is up.

If "Fast and Easy" is changing the flow of checkout, something other mods and addons rely on as a predictable architecture, then it really is their issue to resolve. And probably not a topic for this thread. After all, we have been able to find so many things to resolve with the qbms addon as it is!!

Back on topic - I'm quite happy with this round of updates and fixes, and hope the mods activate the v1.6 on the addon site soon. Having said that - if either mydanilo or securfocus are impatient and would like a direct link to the zip file for 1.6 - just PM me.

Now available in Add Ons. Much appreciation for input and advice on this thread to get this update completed.

cptok: Would it be possible to get a transaction number back into Zen Cart? Or is this something that is beyond what the desktop model can do? Something like the paypal IPN transaction info. It would be great if one could see that a payment has been made and have a reverence # posted in the order.

1.6 works great with initial tests. Thank you.

1.6 works with no problems, even with the Fast and Easy Checkout. Numinix fixed the problem with v1.28. I will not mention this mod anymore. I agree the problem was not related, but for others that will read our posts should know that there is no more problem with the two mods together.

thanks for the updates!

good work!