QuickBooks Merchant Service

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

[cptok]

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.