URL: http://www.uburst.com/cgi-bin/dcforum/dcboard.cgi
Forum: ushp_general_purpose
Thread Number: 385
[ Go back to previous page ]

Original Message
"AVS and CVV2/CVC2 fraud protection"

Posted by dan [dan@subwave.com] on at 01:26 PM
Since MULTICARDS started with collecting the
CVV2/CVC2 numbers - Fraud is not present anymore -why can this 3 digit number not be collected in the UShop ? Or can it ?
Almost all card processing systems include this possibility ..

Table of contents

Messages in this discussion
"RE: AVS and CVV2/CvC2 fraud protection"
Posted by Microburst Support Team on at 01:42 PM
There are various ways that this information can be collected.

The creditcard_template.html file currently allows for 5 credit card fields:
1. cc_type
2. cc_name_on_card
3. cc_number
4. cc_expiration
5. cc_issue

If you are not already utilizing the "cc_issue" number field - then the easiest thing to do would be to just add that "cc_issue" field to your template and give it any label you want.

"RE: AVS and CVV2/CvC2 fraud protection"
Posted by Tom Chapman on at 04:43 PM
I am already using the cc_issue field for Switch Cards - Streamline have just started to ask for the verification number on ALL Customer Not Present transactions (including Switch).

How can I add an additional input field?


Tom Chapman


"RE: AVS and CVV2/CvC2 fraud protection"
Posted by Bill Weiner on at 07:43 AM
The easiest thing to do would be to just choose a label for the "Issue" field so that it requests both the issue number and the CCV number, such as: "Issue Number and CCV Number:". This will store both values in the issue field... but all you are really looking for is a way to collect that information anyway.

Or as a slightly more involved (yet more elegant) option, below are instructions on how to add an extra field to the Credit Card form:

STEP 1: Make a backup of your ushop-lib.pl script... just in case.

STEP 2: Open the ushop-lib.pl file with any text editor such as WordPad.

STEP 3: Do a search on the following line:

$cc_issue = &validate_string($cc_issue);

STEP 4: Immediately AFTER that line, add these three lines:

$cc_code = $form_text{'cc_code'};
$cc_code = &validate_string($cc_code);
$cc_issue .= " / " . $cc_code;

STEP 5: Save the script... as TEXT if your editor asks.. and try it out!

This will allow you to add a new text field to your creditcard_template.html called "cc_code" and will append that value onto the issue number.

Note: Before making this modification, you may want to check the laws in regard to collecting the CCV numbers. I think I read somewhere that CCV numbers cannot be stored in any electronic form. (ie. you have to call and verify the number unless you are using a payment processing system that validates the CCV number in real-time and does not store it.)

"Not writing to .order file"
Posted by Tom Chapman on at 09:03 PM
Many thanks for the quick reply.

I made the following changes to the script:

# From Credit Card Template.
$cc_type = "";
$cc_name_on_card = "";
$cc_number = "";
$cc_expiration = "";
$cc_issue = "";
$cc_code = $form_text{'cc_code'};
$cc_code = &validate_string($cc_code);
$cc_issue .= " / " . $cc_code;

I didn't have the complete cc_issue entry in my original script so I just added the new lines underneath.

The new form field (cc_code) is not writing to the order file - I have checked this both through the order reader and by looking at the text of the .order file as well.

Any suggestions? I have double checked the form to make sure the form field names are correct.



"RE: Not writing to .order file"
Posted by Bill Weiner on at 06:17 AM
It doesn't look like you added the lines to the correct place in the script. Look for the line:

$cc_issue = &validate_string($cc_issue);

... within the "validate_credit_card_parameters" subroutine... and add the additional three lines there.

NOTE: You may have to do the search on just "&validate_string($cc_issue);" to locate that line because there are some additional spaces after the "=" sign... but they are not showing up in this forum.

Posted by Tom Chapman on at 01:04 PM
Thanks Bill - it all working great now!


"cc_issue field"
Posted by Norma Scott [norma@thesteelsource.com] on at 06:45 PM
I need to implement the CVV2/CVC2 support. I do not seem to have the cc_issue field in my credit card template file. It mentions it in the header, but when I look in the body of the file, it's not there. Am I supposed to add it and how so? Thanks.

"getting there"
Posted by Norma Scott [norma@thsteelsource.com] on at 06:59 PM
I think I at least partially answered my own question. I copied the "name" lines and just changed the text and used the cc_issue designation. Will this automatically write correctly to the order so I will be able to retrieve it using the Order Reader? Or do I still need to do something else? Thanks.

"more questions"
Posted by Norma Scott [norma@thesteelsource.com] on at 07:18 PM
Ok, I have a related question for you. I need to be able to collect that CCV code (we recently switched from a PC based process to a card swipe process to speed things in our brick/mortar store, and in order to do internet orders, that security code is required), but I don't want it to print out on the Order Reader form because we print that as a packing slip for the customer's order. I wouldn't want that slip to fall into the wrong hands, who would be able to use the credit card info "legally" because they have the CCV number. Any ideas for a solution?