QuickBooks Merchant Service

[Securfocus]

so, since qbms doesnt get a response from amex whether the cvv is turned on or not, we will never know if the cvv passes?

so if you turn it on at amex, will qbms just figure the charge went through because it doesnt get a response that the cvv failed?

if thats the case i think i would rather just leave it to off for checking the cvv, because if it doesnt get a respone saying yes it worked or no it didnt, it must just default to it passed? which would be bad to figure out the charge really didnt go through because qbms wasnt told the cvv failed.

[mydanilo]

I know it is all a bit confusing. But I do now get the CID response. Here again what it does once CID is activated:

* Now that CID has been activated, AMEX will send the following in the ISO 8583 Authorization Response 1110. If you use a processor or vendor to communicate with American Express, they may translate these responses and provide the same information to you in a different field or value.

Y = CID matched
N= CID did not match
U = CID was not checked

SOOO QBMS can now use these codes like they do with all other cards. No difference anymore once you have
AMEX turn on the CVV verification response.

Conclusion: If you want to only accept cards with a positive verified matching CVV, then you have to have AMEX turn on the CID. If you don't care, don't have it turned on but make sure your QB Merchant security settings do not reject non matching nor not present CVV.

[cptok]

This is worth some thought here... there are two separate checks which happen, Zen and merchant service. You can set Zen to require the CVV code - and it will force inputting the code and send to merchant service. But that does not affect how merchant service handles the transaction.

If I recall correctly, QBMS defaults are to REJECT mis-matched CVV, and ACCEPT matched or "unavailable" CVV. That works pretty well for Visa/MC - but you discovered that AMEX thing - that they report all CVV as "unavailable" or "U". To QBMS, that is acceptable and the charge should go through. BUT that means that a customer can put in a bogus CVV on Amex and it will still run.

So I think the question is - what are the best combination of defaults at QBMS fraud settings and Amex. I think if you have amex verify - that is best. Then you can have Zen require the CVV, and it will come back as match or fail. Easy. But for the default situation - Amex should still clear and run right? As it will come back as "U" which QBMS will accept for CVV (if defaults are still in place). Or am I missing something?

[mydanilo]

cptok: The way I understand it, you are correct with all your statements except one little thing:

"there are two separate checks which happen, Zen and merchant service" Actually three, merchant service sends the cc info to AMEX (or other cards) and they return the result, then QB merchant service will decide what to do according to your security settings.

Other than this detail, you are correct.

[Securfocus]

ok, so now Im clear on this...

1)customer enters CVV code, zen checks to see if its right
2)qbms passes it on to approriate company, amex, visa, mc, etc....
3)cc company sends something back to qbms in there own coding.....
4)qbms then sends a response back to zen which is the same coding you would get from any cc company either

Y = CID matched
N= CID did not match
U = CID was not checked

where i was getting confused is that I thought amex sent something straight to zen, which we didnt have coding for, but zen is just looking for the Y, N, or U which is provided by qbms, which it got from amex.

so if amex CVV check is turned on at amex, amex will send to qbms its response, then qbms will send the Y, N, or U. and if the CVV check is turned off qbms will always send a U.

So i should turn on CVV! alright now im clear!

[mydanilo]

Your conclusion is right but:
"zen is just looking for the Y, N, or U" is wrong. Your QB Merchant account is looking for these and will check with your security settings if this transaction should process.

Zen will only record the completed transaction or give the error message to the customer if the transaction failed.

[cptok]

Well - if we really want to be accurate, Zen parses the "StatusCode" returned in the XML exchange which tells it what happened at QBMS. A "0" is "OK" and then there are a bunch of other 10100 to 10501 codes which are fails with various reasons associated with them. Zen only differentiates between a couple of them and reports. Included in the XML reply will be AVS (zip and street) and CVV results (all Pass, Fail or NotAvailable). We could capture/report those in Zen (in fact I thought about expanding all that error reporting), but why bother. The transaction is already done, and the specific results data available on QBMS website.

[mydanilo]

Thanks cptok. Of course you would be the one that knows exactly what gets sent back and forth. I think we talked this one to death already. Let's leave it at that...

With AMEX now turned on the CID I can do what I want. Just wanted to share this. Read all the fine print in the QB merchant security settings and I think one will get what it is about.

And for the members that got confused by us all talking about the CID, rest assured the module is now working great! Really happy with it. Thank again.

[Securfocus]

Yes, this module works 100%

download cptooks awsome updated module and then if you want you can follow my install path i took on page 12!

thanks again you two for all the help!

cptook, if you come across anything that you needed to update dont forget about us poor non coders!!!

thanks yet again!

[hermes369]

So I walk into my normal Friday visit to SuperNutrient.com (shameless plug), and our office manager is most happy to tell me about QBMS: she's becoming an expert on QB 2009. She asks me if we can use it on the cart; I say, well we'll have to see if there's a module that supports it. Et viola!
Though I'm late to the party, I'm happy to have found you guys and look forward to employing this after I set it up on a test site.
Excellent serendipity!

Thank you!