-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Mark Gardner wrote: | OK.... I know this is a little off-topic but you are all so smart! | | I was wondering if anyone has had any experience in getting a merchant | account setup so one of my commercial sites can process credit card | payments. What are the first steps I should take? | | Mark Gardner
I second Jason's mention of iTransact, and will also mention Authorize.net as a Utah based solution. Others I have worked with are ECHO Online and PSIGate. Unfortunately, I can't distribute them (company code), but I've developed a set of perl modules that work with each of these four, so if you have any questions or need any tips I might be able to help.
Anyways, the first step is to choose which provider you're going to go with. IIRC, you purchase the actual merchant account from a bank and iTransact, et al., provide what is called a Gateway. But the gateway company can usually broker the merchant account for you as well.
After that it's just a matter of interfacing with the gateway providers API. In this department, I have to put in a plug for ECHO Online. It's not the best/simplest API of the four I worked with, but they have and promote an open development community around their API[1]. So if you go with them, you can probably find most of the work done for you.
My two cents.
Jacob Fugal
[1] http://www.openecho.com/index.php -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQFAAvaz/PO7QochUiQRAr9RAKCAfwn3NK+Qwgz0a++vIG+Hw5njVgCfb15l 21oeN7wVSOGn7wF0AOV0AZo= =Fq3p -----END PGP SIGNATURE-----
____________________
BYU Unix Users Group http://uug.byu.edu/ ___________________________________________________________________
List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
