comment on

Thanks for the ideas.

I already have a self-signed cert I created awhile ago, and it's been working fine for my basic tests. I also bury my IMAP mail behind it using SquirrelMail, so the mod_ssl bits are already there and functioning well (I also use a similar certificate for my irc/ssl irc server). My server signature is currently:

Server:
   Apache/1.3.26 (Unix) 
   PHP/4.3.0RC1 
   mod_gzip/1.3.19.1a 
   mod_perl/1.26 
   mod_ssl/2.8.9 
   OpenSSL/0.9.6a
[download]

The only downside to having a self-signed certificate is that the user will get a warning dialog every single time they hit the secured page, because their browser doesn't recognize the CA.

I suppose I'll have to see how to handle the merchant account issue. I wonder what (if anything) they charge for that service. Is it a percentage of the charges processed through them? Or is it a flat fee on a monthly scale? Merits further investigation. Thanks again.

In reply to (OT) Re: Building in "donation management" support in site design by hacker
in thread (OT) Building in "donation management" support in site design by hacker

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Pathologically Eclectic Rubbish Lister
	PerlMonks