QuickBooks Merchant Service

[Securfocus]

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!

[mydanilo]

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.

[cptok]

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

[Securfocus]

cool, just keep us posted!

[cptok]

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.

[mydanilo]

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?

[cptok]

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)?

[mydanilo]

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....

[cptok]

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?

[mydanilo]

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.