Using authorize.net for payments??

[Greg Evans <raisplin@rcn.com>]

******    message to minivend-users from Greg Evans <raisplin@rcn.com>     ******

My lovely boss today told me that we would be using authorize.net for our 
credit card processing...The HTML part of it is easy enough, I am 
wondering where I put this info though, I would guess checkout.html in 
the /path_to_my_catalogs/simple/pages/ord directory.  However I am unsure 
hwo to impement this without breaking the current form as I as of yet 
don't understand the tags completely or to be honest, exactly how this 
page works.


The part I am unclear on is when looking at the form on the checkout.html 
page I am not sure what "[process-target]" means nor what it will break 
if I just change the 

<FORM ACTION="[process-target secure=1]" METHOD=POST>
 to
<form method="POST" 
action="https://www.authorize.net/scripts/authnet25/WebLink.asp">


Any help much appreciated,

Greg

====Begin authorize.net information====


Here is the information from authroize.net on how to do it: (unneccesarry 
crap deleted)

Link directly to the Authorize.Net secure transaction gateway - (only for 
merchants who have a secure server AND are capable of 
creating/programming their own payment form) The flow of the links is as 
follows:

Your web site, then to.. 
Authorize.Net Secure transaction gateway, then to..
Authorize.Net WebLink transaction receipt page, then ..
Back to your web site

NOTE: For the purposes of this section, a secure server is defined as a 
web server that has installed and is running at least SSL 2.0 (Secure 
Socket Layer) and has a verifiable secure server digital certificate from 
a recognized certificate authority.

Before starting to implement the following requirements, please consider 
that the Authorize.Net payment form and receipt page are provided by the 
Authorize.Net system and
can be customized only in certain ways. The system has been designed to 
appeal to the widest variety of merchants as is possible. A list of what 
you can change about the
Authorize.Net payment form and receipt page is found in the section 
entitled "Edit configuration" later in this guide.

You must have a moderate understanding of HTML in order to fully exploit 
the features of Authorize.Net WebLink. Although it is true that the 
following snippets of HTML code
can be copied and pasted directly into a web site and it would "work", it 
is not likely that all of the specific needs you have with your web site 
will be met simply by copying and
pasting this code. Merchants that are unable to achieve the custom look 
and feel they want on their own should consult with a local Internet web 
designer/programmer for
assistance.

How to link a web site to the Authorize.Net WebLink secure payment form
If you have not read the WebLink overview above, please read it NOW 
before continuing.

Requirements for your web site

At the very minimum, you web site must do the following in order to be 
linked properly with the Authorize.Net WebLink secure payment form:

1. Your web site must produce a total amount that is to be authorized by 
the Authorize.Net system. The Authorize.Net code samples below do NOT 
demonstrate how to calculate totals; calculating a total amount is not 
part of the Authorize.Net system, and usually requires script programming 
in your web site. 

2. Your web site must pass at least the total AMOUNT and the 
Authorize.Net LOGIN ID associated with your Authorize.Net account to 
Authorize.Net. The
code samples below demonstrate this.

3. Any other fields, such as invoice, customer ID, name, address, E-mail, 
etc.. that are defined as "required" on the Authorize.Net system by you 
or your merchant provider must also be passed. The code samples below 
demonstrate this.

Allowed Fields

You can pass any of the following fields to the Authorize.Net system. To 
work properly, the fields must be named exactly as the are named here:

LOGIN (required) 
AMOUNT (required)
(the rest of the fields below may or may not be required, depending on 
the account configuration)

TYPE (type of transaction - either "NA" for Normal Authorization or "AO" 
for Authorization Only. The system will assume "NA" if the value is not 
passed)

<snip list of fields they accept>

Example One - Bare minimum requirements
The following HTML code snippet represents the bare minimum requirements:

<form method="POST" 
action="https://www.authorize.net/scripts/authnet25/WebLink.asp">
<input type="hidden" name="LOGIN" value="your login id here">
<input type="hidden" name="AMOUNT" value="total amount here">
<input type="hidden" name="CUSTID" value="customer id here">
<input type="submit" value="Click Here for Secure Payment Form">
</form>
-
To unsubscribe from the list, DO NOT REPLY to this message.  Instead, send
email with 'UNSUBSCRIBE minivend-users' in the body to Majordomo@minivend.com.
Archive of past messages: http://www.minivend.com/minivend/minivend-list