I just went ahead and grabbed it while I had a second.
This includes several form values that I gather (obviously) before I
come to this .cfm There may be extra # in the code as I coded this when
I was first learning CF.
<cfparam name="FORM.ssl_amount" default=0>
<cfparam name="FORM.ssl_company" default="">
<cfparam name="FORM.ssl_customer_code" default="1">
<cfparam name="FORM.ssl_first_name" default="">
<cfparam name="FORM.ssl_last_name" default="">
<cfparam name="FORM.ssl_avs_address" default="">
<cfparam name="FORM.ssl_address2" default="">
<cfparam name="FORM.ssl_avs_zip" default="">
<cfparam name="FORM.ssl_email" default="">
<cfparam name="FORM.ssl_city" default="">
<cfparam name="FORM.ssl_state" default="">
<cfparam name="FORM.ssl_country" default="">
<cfparam name="FORM.ssl_phone" default="">
<cfparam name="FORM.ssl_description" default="">
<cfif #len(FORM.ssl_description)# GT 255><!--- this is a viaKlix
limitation --->
<cfset xDescrip = #left(FORM.ssl_description,254)#>
<cfelse>
<cfset xDescrip = #FORM.ssl_description#>
</cfif>
<cfoutput>
<form action="https://www.viaKLIX.com/process.asp";
method="post" name="SendCC">
<input type="hidden" name="ssl_merchant_id"
value="999999"><!--- this is a value you get when you set up with
viaKlix --->
<input type="hidden" name="ssl_user_id"
value="xxxxxx"><!--- this is a value you get when you set up with
viaKlix --->
<input type="hidden" name="ssl_pin"
value="XXX99X"><!--- this is a value you get when you set up with
viaKlix --->
<input type="hidden" name="ssl_salestax"
value="0.00"><!--- in our case there is never any sales tax but you
could have a value here --->
<input type="hidden" name="ssl_show_form"
value="True"><!--- see below --->
<input type="hidden" name="ssl_description"
value="#xDescrip#">
<input type="hidden" name="ssl_transaction_type"
value="SALE"><!--- this could vary - see viaKlix docs; e.g., might be
(as I recall) "CREDIT" --->
<input type="hidden" name="ssl_amount"
value="#FORM.ssl_amount#">
<!--- see below --->
<!---<input type="hidden" name="ssl_card_number"
value="#FORM.ssl_card_number#">
<input type="hidden" name="ssl_exp_date"
value="#FORM.ssl_exp_date#">
<input type="hidden" name="ssl_cvv2"
value="#FORM.ssl_cvv2#">
<input type="hidden" name="ssl_cvv2cvc2"
value="#FORM.ssl_cvv2cvc2#">--->
<input type="hidden" name="ssl_company"
value="#FORM.ssl_company#">
<input type="hidden" name="ssl_customer_code"
value="#FORM.ssl_customer_code#">
<input type="hidden" name="ssl_first_name"
value="#FORM.ssl_first_name#">
<input type="hidden" name="ssl_last_name"
value="#FORM.ssl_last_name#">
<input type="hidden" name="ssl_avs_address"
value="#FORM.ssl_avs_address#">
<input type="hidden" name="ssl_address2"
value="#FORM.ssl_address2#">
<input type="hidden" name="ssl_avs_zip"
value="#FORM.ssl_avs_zip#">
<input type="hidden" name="ssl_email"
value="#FORM.ssl_email#">
<input type="hidden" name="ssl_city"
value="#FORM.ssl_city#">
<input type="hidden" name="ssl_state"
value="#FORM.ssl_state#"><!--- I leave out some things you see on the
viaKlix site because they are not needed for verification --->
<input type="hidden" name="ssl_country"
value="#FORM.ssl_country#">
<input type="hidden" name="ssl_phone"
value="#FORM.ssl_phone#">
<!--- change as needed
<input type="hidden" name="ssl_test_mode"
value="TRUE"> ---><!--- see viaKlix docs; uncomment if you need to test
--->
<input type="submit" value="STANDBY"><!--- see
below --->
</form>
</cfoutput>
<!---
Even though I had a secure site (https) and didn't store the credit card
info my employer balked at even gathering it on our site.
So, I set ssl_show_form to TRUE. Before that I transmitted the credit
card info and set ssl_show_form to FALSE so the user never saw
the viaKlix entry form. This now takes them to the viaKlix form but
prefills the information transmitted above. You can control your viaKlix
Form in their administrator so that some fields can be seen - filled
with this info - but not edited on their site. They now go to the
viaKlix form, enter the credit card data, and submit.
The weakness of this approach if someone should quickly pop up the
page's code before it submits - and I have found no way to overcome it -
is your info (e.g. merchant ID) is exposed for just a few seconds
Until the javascript code below automatically submits the page to
viaKlix. I have my sites set so I have to approve all transactions and
I've
never had a problem.
My wife uses pcCharge software and we like that. I use a different
approach there, using Windows ability to have two windows working at the
same time
to send keystrokes to the keyboard buffer which fills in her web based
form and we then submit that.
--->
<SCRIPT LANGUAGE="JavaScript"><!--
setTimeout('document.SendCC.submit()',1);
//--></SCRIPT>
-----Original Message-----
From: Jesse Kuhn [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 27, 2006 4:54 PM
To: CF-Talk
Subject: Re: Viaklix
Larry,
If you don't mind could you post or email your viaklix code so I could
compare with the other post? It would be greatly appreciated... this is
the only place I've been able to find anything that involves viaklix and
ColdFusion (viaklix and Nova support have been no help at all). Thank
you very much in advance.
Jesse Kuhn
[EMAIL PROTECTED]
>
>If the other postings don't work let me know. I've used it successfully
>in two applications.
>
>
>Larry V. Stephens
>Indiana University
>Office of Risk Management
>[EMAIL PROTECTED]
>812-855-9758
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting,
up-to-date ColdFusion information by your peers, delivered to your door four
times a year.
http://www.fusionauthority.com/quarterly
Archive:
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:254546
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
