Credit Card Validating

Hi,

I'm interested in using this product to create payment forms for a limited number of products on a website. I'll take care of the SSL certificate, but I'm curious to know if this can handle credit card validation, by making sure the format is correct? Not actually validating live cards.

Plus, I'll be using this for client websites, is there a way to give permission to view the data collected, but not necessarily the access to edit/break forms that have been created?

Plus just one quick piece of feedback, it's a shame the forums and documentation are limited to paying customers only, it makes it difficult to understand what the product is capable of without asking for help here :)

Thanks!

Wow.
This would be HUGE right now. At least any applicable CC validation rules to begin with. Then Authorize.net Direct Post Method (DPM) integration support would be amazing.

Any possibility of these in the future?

visa card accepted?

I have enabled the hidden credit card field and placed it on my test form.

At present I do not have a 3rd party cc processor and presumed my form would just process but not store cc data as described above (while I test it further).

For some reason the form when you complete the form it rejects any credit card number during validation with the message "Invalid credit card number". I have tried a number of test card numbers and real ones also.

Is this because I haven't setup integration to the 3rd party yet (ie submit uses gravity forms) or do I need to do something else. I have set all credit card types on using the form field checkboxes during the setup of the form.

I am getting the same problem on my ssl server as well as locally.

Thanks

To see the credit card not passing vaildation please try [redacted]

Did some experimenting at this end and it seems the problem occurs once you using paging for your form. If all fields are on a single page - card numbers seem to validate. Once the cc field is on page 2 (like example) I keep getting invalid card number.

Correction to above post. Force ssl alters ampersands in the query string on chrome, safari and FIREFOX (only ie not affected) so that prepopulation via url no longer works.

I think the the url string using ampersand amp semicolon is still valid (as is a single ampersand) but prepopulation is not working unless the url is constructed using single ampersands.

Can the force ssl be modified to not change the ampersand or can gravity forms be changed to still prepopulate if the query string contains this alternatte variant (ampersand amp semicolon). ? Is there another way to build the query string (maybe no ampersands ?).

Hi, A few questions on this CC topic...

1. Where is this form_detail.php located, to paste the CC code snippet?

http://www.gravityhelp.com/documentation/page/Gform_enable_credit_card_field

2. And, are you saying there will be a "force ssl" check box at the level of the CC field in the form itself?

3. Also, what is the scope of this field? Once user submits form, the info is NOT saved? Is it at least "captured" (sent to my email) for admin to view - or is it lost in thin air once the form is submitted? Its purpose is simply to make sure there are no errors? Which credit cards does it validate?

4. Is this the only way to validate or "take" a credit card without a developer license?

thanks :)

@tmort - Yes the cc field looks nice. I can get the cc details encoded (encrypted would be better) and sent via email. Hopefully you or someone can work out how to save it with the form. I was trying to save the details into a hidden or new field and keep and leave the rest alone

//Turn on our credit card field for admin and front end
add_action("gform_enable_credit_card_field", "enable_creditcard");
function enable_creditcard($is_enabled){
    return true;
}
//Email encoded card details when the form is submitted.
add_action('gform_after_submission', 'email_encoded_cc', 10, 2);
function email_encoded_cc($entry, $form) {
function get_creditcard_field($form){
        $fields = GFCommon::get_fields_by_type($form, array("creditcard"));
        return empty($fields) ? false : $fields[0];
    }
        $card_field = get_creditcard_field($form);
        $card_number = rgpost("input_{$card_field["id"]}_1");
        $expiration_date = rgpost("input_{$card_field["id"]}_2");
        $expire_month = $expiration_date[0];
        $expire_year = $expiration_date[1];
        $security_code = rgpost("input_{$card_field["id"]}_3");
        $card_name = rgpost("input_{$card_field["id"]}_5");
$cc_detail_string =  "CCName $card_name CCNum $card_number CCexp $expire_month-$expire_year CCV $security_code  " ;
//remember base 64 is not encryption - just encoding!
$encoded_cc_detail_string = base64_encode($cc_detail_string);
//send encoded cc details via email
$to = "whoever@wherever.com"; /*your email here*/
$subject = "For your eyes only";
$body = $cc_detail_string; /*or encoded string*/
$message = "Here are some cc details $body";
$from = "someonelse@example.com";
$headers = "From:" . $from;
mail($to,$subject,$message,$headers);
}