Last I knew, <@URL> won't post form data. I tried JavaScript to submit on page load, but it wouldn't work -- I surmise because I had other actions with results HTML coming before it.
Chris > Hi, > > I attempted to do this through the <@URL> tag and it wouldn't accept it. > Have you tried it through this route? > > Ben Johansen - http://www.pcforge.com > Authorized Witango Reseller http://www.pcforge.com/WitangoGoodies.htm > Latest downloads & List Archives @ http://www.witango.ws > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On Behalf Of Cornelius Conboy > Sent: Friday, September 27, 2002 10:47 AM > To: Multiple recipients of list witango-talk > Subject: Re: Witango-Talk: Initiating a secure client connection > toapayment gateway > > Hey Chris, > > If you're serving https on your site all you need to do is post the > form > from that to authorize.net's url > > What we do to capture users info into our db easily is have the user > post > the form initially to an action where we create and populate the db > record. > Then we present them with the completed form to approve before making > final > submission. > > From here we post to authorize.net using 100% hidden fields > > <FORM METHOD=POST > ACTION="https://secure.authorize.net/gateway/transact.dll";> > > send them their required parameters > > <INPUT TYPE=HIDDEN NAME="x_Cust_ID" VALUE="your value"> > <INPUT TYPE=HIDDEN NAME="x_Invoice_Num" VALUE="your value"> > <INPUT TYPE=HIDDEN NAME="x_adc_url" VALUE="http://www.your > domain.com/name.taf?arg=whatever"> > <INPUT TYPE=HIDDEN NAME="x_First_Name" VALUE="your value"> > <INPUT TYPE=HIDDEN NAME="x_Last_Name" VALUE="your value"> > > etc. > > Authorize.net processes the transaction and sends you back whatever > args > you pass to them, a response code (1=passed, 2=declined, 3=error) and a > response reason code that elaborates on declines and errors (6= expired > card, 11=duplicate transaction for example). > > We've had some sporadic problems with their general customer service but > the > form posting has been pretty straightforward for us. > > -Cornelius > > on 9/27/02 10:27 AM, Chris Millet at [EMAIL PROTECTED] wrote: > >> Actually, what I need to know is what to do before the transaction > takes >> place, not after. I would like to capture all the information on one > page >> and pass it to authorize.net for processing. According to their >> documentation, I need to be able to initialize a client side secure >> connection before this entire process can happen securely. >> >> I think it has to do with the fact that a client must establish a > secure >> connection with both my site and the authorize.net site in order for > this to >> take place. I can serve a secure form for the client to fill out with > an >> action pointing to authorize.net, but since the form originated from > my >> site, the connection to authorize.net would not be secure until after > the >> client had transmitted the information. If the client initiated the > secure >> connection before transmitting the data, then it would be secure all > around. >> Authorize.net documentation claims there are ways to initiate a > client-side >> secure connection, but I am not aware of one. >> >> At least that is my understanding of it. This is my first time to use >> authorize.net. I have done this using Verisign, but I have found their > tools >> to be rather limiting as well as pricey. >> >> Chris >> >>> One of the parameters that you pass to authorize.net is called > "x_adc_url". >>> it indicates where authorize.net sends the user after his transaction > is >>> processed. >>> >>> I put an if statement at that point to check if the transaction was >>> approved, declined, or if there was an error. >>> >>> I know this topic has been covered on the list a lot so if you have > any >>> other questions I'll be glad to help you off list. >>> >>> -Cornelius >>> >>> on 9/27/02 6:25 AM, Chris Millet at [EMAIL PROTECTED] wrote: >>> >>>> Does anyone know how to do this? My goal is to seamlessly integrate > a >>>> shopping cart with the authorize.net payment gateway without looking > like I >>>> left the site. >>>> >>>> Chris >>>> >>>> > ________________________________________________________________________ >>>> TO UNSUBSCRIBE: send a plain text/US ASCII email to > [EMAIL PROTECTED] >>>> with unsubscribe witango-talk in the message body >>>> >> >> > ________________________________________________________________________ >> TO UNSUBSCRIBE: send a plain text/US ASCII email to > [EMAIL PROTECTED] >> with unsubscribe witango-talk in the message body >> ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
